Post

@codevsdev debugging your own code without blaming the framework first
English

@codevsdev reading source code when you are stuck. anyone can google an error, but the people who just open the actual library and read what it does are unstoppable. least glamorous skill, most compounding one over a career.
English

@codevsdev Troubleshooting. Coding is a big part of it but knowing how to quickly fix things in your stack when they aren't working right is also important.
English

@codevsdev When given a body of work to do with any substance, NOT opening up your IDE and starting to code. Requirements first, coding second.
English

@codevsdev Debugging & ability to have deeper understanding.
Now a days, whenever a error comes up 60% just give it to AI and leave it, no one cares how it is getting fixed.
English

@codevsdev Understanding networking and OS. Those skills compound and make you much stronger.
English

@codevsdev weighing pros/cons instead of assuming one solution has zero tradeoffs.
English

@codevsdev Reading documentation.
You spend more time understanding and researching what you are doing than actually building.
With AI, this even becomes more important.
English

@codevsdev Being able to connect the dots quickly.
A lot of tech work is not about knowing the tool. It's about understanding what is actually happening.
English

@codevsdev The ability to take hate and respond with love.
English

@codevsdev Reading the output of an agent. There is way too much of lgtm around here
English










