11–20 of 339 posts
I'm confident enough to tout this number as effectively true, though I should mention that no company I work with has so far been willing to delete a whole day's work to prove or disprove this experiment yet. Long ago when I was much more tolerant, I had a boss that would review all code changes every night and delete anything he didn't like. This same boss also believed that version control was overcomplicated and d…
re·con·nais·sance noun military observation of a region to locate an enemy or ascertain strategic features.
Did you want to grace us with any particular relevance of this knowledge or do you just wanna keep it to yourself? Sadly, after all these years programming, I have yet to discern any real vulnerability in the US government.
Compare the sorts of teams that do prototyping and the sorts of teams that work to a Gantt chart.
* the ideal light cav trooper was jockey-sized, highly observant, and was already a good horseman before enlisting; the ideal heavy cav trooper was imposing, obedient, and was taught just enough horsemanship to carry out orders but not so much that he could go AWOL.
Developers need to learn how to think algorithmically. I still spend most of my time writing pseudocode and making diagrams (before with pen and paper, now with my iPad). It's the programmers' version of the Abraham Lincoln's quote "Give me six hours to chop down a tree and I will spend the first four sharpening the axe."
re·con·nais·sance noun military observation of a region to locate an enemy or ascertain strategic features.
Did you want to grace us with any particular relevance of this knowledge or do you just wanna keep it to yourself? Sadly, after all these years programming, I have yet to discern any real vulnerability in the US government.
You could see the recon as the thinking from the article. The enemy and terrain are the code and various risks and effects associated with changing it.
Developers need to learn how to think algorithmically. I still spend most of my time writing pseudocode and making diagrams (before with pen and paper, now with my iPad). It's the programmers' version of the Abraham Lincoln's quote "Give me six hours to chop down a tree and I will spend the first four sharpening the axe."
Developers need to learn how to think algorithmically. I still spend most of my time writing pseudocode and making diagrams (before with pen and paper, now with my iPad). It's the programmers' version of the Abraham Lincoln's quote "Give me six hours to chop down a tree and I will spend the first four sharpening the axe."
Wait… you have the diffs… why are you retyping the lost code by hand? What am I missing?
Developers need to learn how to think algorithmically. I still spend most of my time writing pseudocode and making diagrams (before with pen and paper, now with my iPad). It's the programmers' version of the Abraham Lincoln's quote "Give me six hours to chop down a tree and I will spend the first four sharpening the axe."
Does it really take four hours to sharpen an axe? I've never done it.
Takes about 20 minutes to sharpen a chainsaw chain these days though...
Developers need to learn how to think algorithmically. I still spend most of my time writing pseudocode and making diagrams (before with pen and paper, now with my iPad). It's the programmers' version of the Abraham Lincoln's quote "Give me six hours to chop down a tree and I will spend the first four sharpening the axe."