I feel like posting this documentary for every A10 thread because it's awesome.
https://www.youtube.com/watch?v=_L_TjXXx7eQ&list=PLBRwtd-BBErti3HPCo-YKtqhrZGgdwJDX&index=1&t=703s
"Several months ago, I came to possess film footage depicting the exploits of an A-10 Fighter Squadron in Afghanistan during the fighting season of 2014. The story it renders, through interviews and first-person experiences on the battlefield, vividly illustrates the essential role of the A-10 Warthog, its community of pilots, and Joint Terminal Attack Controllers working together expertly to save the lives of ground troops engaged in close combat in the most dangerous place in the world."
-
10 tags
-
10 tagsJon Stewart and Chris Smith on Charlie Rose
https://youtu.be/ARIR3y49tXA
I missed it when it aired, but now it is on the tubespace. -
10 tags
-
10 tagsChaps, Chapettes. What were your favourite books of 2016?
I'm doing my yearly thing where I list a bunch of books to receive as a Christmas present from family. You guys have been pretty good in the past. Can't be arsed to wait for Goodreads. -
10 tagsClear cache, problem solved:
power off your Nexus, then:
Press and hold Volume Down and Power simultaneously until you see the boot screen
Use Volume Down to navigate to Recovery Mode
Press Power to confirm
Wait until you see the Android robot then hold down Power. Press and release Volume Up.
Navigate with Volume Down to the Wipe Cache Partition option.
Press Power to select.
Use Volume Down to highlight the Yes option.
Press Power to select.
Press Power to reboot your Nexus. -
10 tags
-
10 tags
-
10 tagsKeep in mind, these are principles for the process of making good software, not what good software is. This is the content of the slides and I will talk through the so, unfortunately, there's some content that is part the overall presentation but has not been committed to text. So if you have questions about what I mean by a particular thing, please ask.
1. Understand the business domain
- Engineers are hired to create business value, not to program things *
- We each must know the goals of the business, not just he goals of the program
- Why a feature should exist will inform you on how make it instead of just being focused on what to build
* http://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-programmer/
2. Quality is not a feature, it’s fundamental
- We should strive to write programs that are SOLID
- Unit tests are how we know our programs aren’t misbehaving
- Security is not a “layer” in a program, it’s a concern with every line written *
- Readable code is not just nice to have, it’s how we ensure maintainability
- Integrate often so failures are small **
* https://youtu.be/eL5o4PFuxTY
** https://blog.codinghorror.com/check-in-early-check-in-often/
3. Leverage the wisdom of the team
- Lone wolf programming is not appropriate behavior *
- Be humble and honest about what you don’t know
- Be generous and patient when mentoring on what you do know
- Code reviews are not just for oversight, they’re a great way to learn
- Disagreements can be one of the best ways to find a solution to a problem
- Look to the community as an extension of the team
* https://www.youtube.com/watch?v=t9YLtDJZtPY -
10 tagsSystem Shock Reboot gameplay!
https://www.youtube.com/watch?v=v_uJ47oKHY0
Looks great!
http://www.polygon.com/2016/6/24/12007602/system-shock-kickstarter-campaign-rewards-screens-demo -
10 tags