Hello Lovelies,
If you talked to an aircraft designer and they showed you their design drawings but they apologised that they were a bit of a mess and that the design wasn't very good, how keen would you be to go for a fly?
More often than not the first word I hear when looking at someones block diagram is "sorry"
Whereas we love showing off our code, we kind of buy into the software craftsman view of it. We feel our code is well-crafted and have pride in it.
Quite often this contriteness is misplaced, if the code is working and adding value then it is good software in my opinion. It might not be good for all use cases though and this is when we get the call. Most commonly it might be functionally good, but difficult to maintain or extend.
The difference here is interesting and I actually think there are things to apologise for and things that you don't need to apologise.
Say sorry for these!
Note: all of the above are wilful decisions or omissions.
Don't say sorry for these
One reason we never feel the urge to say sorry is that we write code slow to debug fast and that involves effort and attention to detail. Debugging fast means we can make changes fast too, they are related.
I've tried to float the index to articles at the top of the blog, been told by NI that it won't work and this article is the tester.
Let's see<--Didn't Work
Lots of Love
Steve
Steve
Opportunity to learn from experienced developers / entrepeneurs (Fab,Joerg and Brian amongst them):
DSH Pragmatic Software Development Workshop
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.