TechWorkRamblings

by Mike Kalvas

202407181026 Architecture as a form of procrastination

Don't let architecting your application, library, or system prevent you from doing the actual work that needs to be done. It's better to have something working and shipped than to have it be perfect the first time.

Avoid architecture as a form of procrastination. [...] There's a lot of disguised procrastination in dev in general. Lots of working around the work, planning how to work, talking about the work, instead of actually working. And I know there's a balance to that because you want to think about what you're doing beforehand, before you do it, and have a good plan.1

202106221150 Procrastination is a complex subject with a range of causes and effects. Architectural 202109090909 Decision paralysis could mean that we need to just get something going in order to make progress and get a better feel for the problem space (throw one away #thread).

Knowing when to architect and plan ahead vs just get moving is something that comes with experience, and can be a good indicator of people who can operate at the 202206112236 Senior engineer or 202206112233 Staff-plus engineer level.


  1. Otwell, T., & Stauffer, M. (2024, June 24). The Laravel Podcast | Listener Q&A: ChatGPT, Laravel Hangups & Best Practices, API Docs, Inertia Next Steps (S6:E13) [Broadcast]. https://laravelpodcast.com/episodes/listener-q-a-chatgpt-laravel-hangups-best-practices-api-docs-inertia-next-steps