7

I think one of my biggest mistakes as a dev in the becoming is to have tried to produce code rather than think code.

The patience to try and understand a problem rather than just solve it.

After spending 2 hours on what seemed like a ridiculously small issue,i know what the problem was before solving it.

Which meant i did take longer to solve it but i DID NOT take the wrong direction. Which would ultimately have come back to my face some time soon.

Coding takes a fuck load of time -_-.

Comments
  • 2
    My vision right now is to get to the point where I’m just thinking code and can help my employees in a more coaching type of leadership and help them to think and then produce.
    One of my leading catchword is “THINK” - as IBM always have had :)
  • 1
    I agree it should be important to think things through but that's becoming less and less of a reality, and I'll try to explain why.

    Sure the frameworks we use today are based on these algos and data structures and we should know them but for many devs they're not relevant day-to-day. All of a sudden the day to day for many involves setting up and building with a framework that does all the heavy lifting.

    As a result bugs have started to change from issues with malloc and DS/algos to immutability, versioning, and uncategorizable errors. When this happens it often doesn't help to think about it because sometimes the framework doesn't support the fix, and other times it's not something you can figure out without being familiar with the framework's codebase and recent changes. Nowadays some bugs can't be fixed without a workaround commandline flag with a specific version of leptonica (@tesseract).

    It _should_ be important to think, but recently errors are getting more and more obscure.
  • 2
    Perhaps if the design of these frameworks was done more with engineering in mind and less with speed/ease of use/extensibility then things would make a lot more sense and do what they're supposed to :/
  • 0
    Funny thing is that i always jump to solving without really Thinking. Learning to really THINK before solving.
Add Comment