Re: who should do redactors. My $0.02 is that the person who did the work should refactor. I have found this to be a good tool for developing that second skill of anticipating future needs. The advice I give my team is to build in a self-aware way for future refactors: focus on spotting issues as you develop and rigorously enforce modularity, declarative thinking, and commenting your thoughts in code to leave breadcrumbs for future re-work. Disclosure: I'm not a coder but I have built an entire company using no/low code tools
Using low code is software engineering too. Not a huge fan of the gatekeeping present in the tech circles.
Great point about future developments. This is definitely important for building long term skill. Curious how you trade that off against immediate results especially now that the tenure in the job market is reducing so much .
Great piece. Thank you so much
Glad you liked it
Re: who should do redactors. My $0.02 is that the person who did the work should refactor. I have found this to be a good tool for developing that second skill of anticipating future needs. The advice I give my team is to build in a self-aware way for future refactors: focus on spotting issues as you develop and rigorously enforce modularity, declarative thinking, and commenting your thoughts in code to leave breadcrumbs for future re-work. Disclosure: I'm not a coder but I have built an entire company using no/low code tools
*redactors == refactors
Using low code is software engineering too. Not a huge fan of the gatekeeping present in the tech circles.
Great point about future developments. This is definitely important for building long term skill. Curious how you trade that off against immediate results especially now that the tenure in the job market is reducing so much .
Hi Devansh
Great to know about your approach to understanding & learning AI in a systemic way.
Would like to connect with you on WhatsApp. - Dipak from India
My email ID: dkkapoor47@gmail.com
Looking forward to hearing from you.