Lead Software Engineer building happier, more collaborative teams, and developing genuinely simple enterprise code
Android | Gamedev | Beardsman | Barista
đMarietta, GA
| GitLab | https://gitlab.com/timothyolt |
The slides from my @voxxedzurich talk "Reversible Decisions for Better Software Design" are now online:
https://speakerdeck.com/dtanzer/reversible-decisions-for-better-software-design-voxxeddays-zurich
Ursula Leguin, who I think might have been the first female sf/f author I ever read whose name made it clear she was female, is, of course, *legendary*.
Arkady Martine has done some truly impressive work, esp. _A Desolation Called Peace_.
There are also writers who don't specialize in sf/f, but who have written there:
Margaret Atwood's _Oryx and Crake_ stands out.
As does Mary Doria Russell's *stunning* _Sparrow_ duology. (Be prepared to feel sad.)
"I hate planning meetings!"
Maybe. Maybe it would help if you saw people actually _planning_:
- changing the plan to reflect changing reality
- taking our anxiety seriously about missing deadlines
- figuring out what to say "No" to, then actually saying it
What do you think?
As well, 5 iOS and 6 Android people from my team were let go as well â they're all _amazing_, really truly.
Best team I've ever had the pleasure of working with.
So, if anyone is recruiting senior or staff mobile engineers, and _especially_ for design systems, let me know and I can intro you to them.
If you value my work and decades of teaching (including setting the example of a different way to âteachâ that doesnât âelevateâ an âauthorityâ but rather fosters co-creation of the experience, where we all step into leadership moments as we flow through the experience)
please at least like if youâre on LI (reshare would be better obv)
Also (but not only) boost here, of course.
RE: https://mstdn.ca/@drikanis/116107120926277506
I'd like to comment on the common "AI is just a tool" thing: I'm a woodworker by training & that means a lot of machines - but almost every craftsperson knows how to do their job with hand tools, or "lesser" machines.
Similarly, a writer can write without a text editor - just as well, only slower.
If loss of a tool = loss of your skill & knowledge, then that tool isn't an asset, it's a liability. You're signing over your ability to do business to whoever sells & maintains that tool.
Coding is like taking a lump of clay and slowly working it into the thing you want it to become. It is this process, and your intimacy with the medium and the materials youâre shaping, that teaches you about what youâre making â its qualities, tolerances, and limits â even as you make it. You know the least about what youâre making the moment before you actually start making it. Thatâs when you think you know what you want to make. The process, which is an iterative one, is what leads you towards understanding what you actually want to make, whether you were aware of it or not at the beginning. Design is not merely about solving problems; itâs about discovering what the right problem to solve is and then solving it. Too often we fail not because we didnât solve a problem well but because we solved the wrong problem.
When you skip the process of creation you trade the thing you could have learned to make for the simulacrum of the thing you thought you wanted to make. Being handed a baked and glazed artefact that approximates what you thought you wanted to make removes the very human element of discovery and learning thatâs at the heart of any authentic practice of creation. Where you know everything about the thing you shaped into being from when it was just a lump of clay, you know nothing about the image of the thing you received for your penny from the vending machine.
#AI #VibeCoding #design #development #making #creation #artiface #craft #coding #programming #technology #humanity
dtanzer
Al Sweigart
sam henri gold
GeePawHill
J. B. Rainsberger (he)
Col
Kyle đłď¸âđ
Ruth â of systems & design
JWcph, Radicalized By Decency
Aral Balkan