Why you should AVOID being a tactical programmer
Would you consider yourself to be a tactical or a strategic programmer?
Do you just want to get the job done or are you a bit of a perfectionist?
There's many terms for the same behavior: cutting corners, rushing, being lazy – it's all describing something called "Tactical Programming". Whatever you call it, it will bite you in the long run in software development!
What both of these terms precisely mean, which way of working is preferred and why (hint: it's strategic programming), what psychology has to do with today’s video and most importantly how you can make yourself a lot more valuable for your company and the job market in general, you will find out in today's video – especially if you are a junior developer!
This video is for software engineers as well as managers. In this video, you'll get tips how to approach your daily job.
Timestamps:
00:00:00 Introduction
00:00:31 How a tactical programmer works
00:02:19 Reason 1: Why a strategic approach is preferable
00:03:25 How a strategic programmer works
00:04:37 Reason 2: Why a strategic approach is preferable
00:06:24 Psychological effects of all of this
00:08:24 Reason 3: Why a strategic approach is preferable
00:09:30 Summary
Please note that this video is based on personal experiences as well as publicly available books, most prominently "A Philosophy of Software Design" by John Ousterhout.
You can support my channel by buying said book via these links, in case you are interested:
Amazon.com:
"A Philosophy of Software Design": https://amzn.to/2WqKzby
Amazon.de:
"A Philosophy of Software Design": https://amzn.to/3icxudh
Amazon.co.uk:
"A Philosophy of Software Design": https://amzn.to/3ASBLKf
If you have any suggestions for content or feedback please leave them in the comments.
In case you enjoyed this video, make sure to leave like, subscribe and share it with anyone you could consider interested!