Swizec Teller

@swizec.com

Best selling author of Scaling Fast: Software Engineering Through The Hockeystick book ⏵ https://scalingfastbook.com prev book ⏵ https://swizec.com/senior-mindset blog ⏵ https://swizec.com

Skills make pretty good documentation for repetitive tasks. Something about writing for models tricks people into being concise and to the point. No fluff

Bild

I had Fable revamp the information architecture of my blog (1969 posts across 20 years) and it found ~8 core categories then Fable decided to write an intro blurb for each (good idea, I didn't ask) this is shockingly good writing

Bild

In the 80’s and 90’s it was obvious that programming was solved. Compilers, OOP, and later MVC frameworks + Java meant that “if you think hard enough and make a plan, you can just delegate implementation to cheap non-engineers” sound familiar?

Been thinking about leading software teams when everyone’s also using agents Architects have two failure modes: - ivory tower -> useless and annoying - code janitor -> burnout To be effective you need to build systems of humans and computers swizec.com/blog/how-to-...

How to be useful as a software architect

Software architects have a weird role: Think about the code _tomorrow_. Today's code is what it is, how do we make it good tomorrow? Without slowing down, losing business, or falling off a cliff.

swizec.com

The best team you can have right now is a high agency product engineer with a token budget and freedom to cook give them tools, say yes, and get out of the way

The computer scientist says “The halting problem cannot be solved, I have proven it” and the software engineer goes “30 second timeout, if the answer’s not ready by then we don’t need it”