Resources to become a better Software Engineer besides coding?
3 comments
Look for essays on context. (use cases & post-mortem analysis) The business world much better at this than non-business world largely because need to know can one still make $$$ at it. Note: NASA vs. SpaceX approaches / trade offs to this!
Is knowing how to make better code going to be helpful if using legacy colbal program in a VM in order to use modern web interface? aka How many different contexts are in aforemention situation.
Why did apple succeed commerically where Xerox with same idea, did not.
When/why did Kodac employee concept of digital camera (circa 1970's) not get picked up by Kodac?
Datarace / Intel and the history of the 4044.
Does anyone associate Motorolla with washingmachines & driers anymore?
*****
Systems Analyst vs. Research Software Engineer.
Colbol vs. Lisp
Dec VMS vs. Unix
Space shuttle redundency software (sync vs. async) vs. Voyager probe.
Is knowing how to make better code going to be helpful if using legacy colbal program in a VM in order to use modern web interface? aka How many different contexts are in aforemention situation.
Why did apple succeed commerically where Xerox with same idea, did not.
When/why did Kodac employee concept of digital camera (circa 1970's) not get picked up by Kodac?
Datarace / Intel and the history of the 4044.
Does anyone associate Motorolla with washingmachines & driers anymore?
*****
Systems Analyst vs. Research Software Engineer.
Colbol vs. Lisp
Dec VMS vs. Unix
Space shuttle redundency software (sync vs. async) vs. Voyager probe.
Getting better at being a programmer/developer is a mix of technical skills and people skills and you will do good in being better at both.
My I recommend checking out https://www.programmingbooks.dev.
My I recommend checking out https://www.programmingbooks.dev.
learn to say no, how to negotiate and how to sell.
I already know plenty of resources on how to make better code. But besides programming, I'm looking to become a better professional by itself. That is, being more reliable, to come up with better and more structured procedures, and to provide good services despite less than ideal contexts (which is, almost every company software project)
For starters, I got the book "How to Work Effectively With Legacy Code" for the technical part. My guess is to read about scrum and agile. Then about git flow and collaborative software projects. Then a bit about devops so I know what platforms support the product I'm trying to make.
Am I missing something?
Thanks in advance