Whether it is a specific enough technical expertise, or just part of the craft you do well?
For further actions, you may consider blocking this person and/or reporting abuse
Whether it is a specific enough technical expertise, or just part of the craft you do well?
For further actions, you may consider blocking this person and/or reporting abuse
Latest comments (98)
Over the last couple of years it's become clear to me that most problems in dev come not from bugs in code, but from flawed/missing conceptualisation of business/problem.
As such, I've focused hard on studying software architecture and understanding business. My go-to tools these days are Domain-Driven Design (DDD) - Event Storming being a powertool for mapping out the Domain, and Clean Architecture to tame the popular abuses of frameworks such as Rails.
Improvisation
Asking the right questions.
Problem solving is the biggest one.
I don't have one yet. I even started out way back 2015 and it seems like I always lost myself all the time. It's also way harder to keep being updated with the latest techs especially living in a remote place where internet connection is a pain in the ass.
Reading Articles
Finding information really fast, but carefully filtered.
Thank you for sharing. I can relate because I've seen people in your situation and also found myself in similar situations. Now looking at the silver lining you quickly landed another job so its all great.
Problem solving. I really like to work on complex/challenging problems.
I would say my visualization skills. Solving problems is always a visual process and I can quickly find analogies in the real world and extract patterns for a solution there. It may be a naive or inefficient one, but I read a lot and I have a lot of schemas to rely on so I can optimize it.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.