Programming Answer of the Day!
-
I spent a couple of years doing it for entertainment. 0) Head to some shareware repository 1) Select and download target 2) Run & alter in debugger 3) save patch to disk or write keygen There's a field of programming challenges known as crackme and another known as keygenme. The latter are infinitely more fun. ;P
-
Judging by QA, most developers can't use a debugger either ... :sigh:
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Documentation is for lovers or those with special needs.
The less you need, the more you have. JaxCoder.com
Let's keep this KSS, please!
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
Debuggers are elephanting useless. They cant tell me why my code wont compile!
"If we don't change direction, we'll end up where we're going"
-
Whenever I write anything I run it through the debugger - I remember when debuggers were either non existent or not very sophisticated, you had to add lots of print statements to see what was going on. The VS debugger is superb.
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
-
Six hours of debugging can save you five minutes of reading documentation."If we don't change direction, we'll end up where we're going"
Six hours of debugging can explain why that documentation you took five minutes to read is completely wrong. FIFY.
-
Six hours of debugging can save you five minutes of reading documentation."If we don't change direction, we'll end up where we're going"
-
Six hours of debugging can save you five minutes of reading documentation."If we don't change direction, we'll end up where we're going"
What documentation? Haven't seen that in years!
-
Six hours of debugging can save you five minutes of reading documentation."If we don't change direction, we'll end up where we're going"
-
Speaking as one that wears all 3 hats, (not at the same time mind you, I would look rather silly), as a developer, the primary focus is to not create bugs when adding new features and certainly now when fixing features. Yes that can be easier said than done, especially as spaghetti code is often at the root cause of many bugs, and debuggers are critical tools needed to help find and fix things. But that is only part of the story, QA and users do unexpected things which developers should for tell and protect against. As a QA lead it is a challenge to break code other developers create, and sometimes its the role of the customer to find the really obscure issues. As a documenter the clarity of what gets written is as important as the accuracy of what is written. I say this after inheriting documentation from two predecessors who claimed to write good English and keep the changes made up to date, (yes that was a laugh). So to summarise, the whole lifecycle can be a real pain, we simply have to do the best we can with the resources to hand, unless anyone has a time machine or working crystal ball. Bobby Dazzler
