Engineering Director @thoughtworks. Breaking production code since '04. “Short cuts make long delays.” Opinions are my own; more on my blog 👇
Toronto, Canada
Joined March 2008
- Tweets882
- Following1.6K
- Followers680
- Likes635
Skills should be less about constraining the model and more about preventing the caller from unintentionally constraining the model.
context pulling > context pushing
Paul Sobocinski retweeted
We’re all set for #coderetreat today. Are you?
#gdcr2024
PS: don’t forget your laptop!
🌐 Global Day of Coderetreat Toronto is back! 🌐
Join us at Thoughtworks Canada’s shiny new office in downtown Toronto for a day of deliberate practice in Software Development.
💪 Coderetreat is a day to exercise your software development muscles.
🚢 Away from the everyday pressures of, “just get it done”, Coderetreat invites us to challenge ourselves in ways we don't get to at work.
✨ That means focusing on what our best work could look like – be it the simplest design, the most expressive tests, or the most readable code.
🤝 We also get to meet and catch up with other professionals in the software industry by actually writing software together!
💻 Fair warning – you’ll be spending almost the whole day coding so come prepared with a laptop and power supply.
All in all, Global Day of Coderetreat is a unique opportunity to learn through deliberate practice while creating meaningful and memorable connections with other software developers.
We hope you’ll join us!
👩💻👩💻 👩💻🧑💻 🧑💻👨💻
📆DATE: Saturday, November 9th, 2024
#gdcr2024 #coderetreat
Register here: na.thoughtworks.com/global-d…
#LeadDevNewYork is a wrap!
To all the organizers, speakers, and attendees — thank you for an unforgettable experience! 🙌
Product roadmaps really being, “Something with X” for decades. Ain’t that the truth. #LeadDev
I never ask for permission to refactor. But I often ask for help.
Don’t confuse asking for help with asking for permission.
Silos happen when the person...
- Good at the thing
- Responsible for the thing
- Doing the thing
... is the same person. Collaboration means that these can be different people.
It requires that people can be trusted to do things right and ask for help when they need it.
A programming language optimized for LLMs to write and maintain would be very terse, to maximize the lines of code that can fit inside of an LLM's context window. It could look like minified JS or something else entirely.
Source code would become indecipherable to humans.
6/9
Consequently, we’ll still need humans who can exist outside the system while simultaneously being deeply involved inside the system.
Only in this way can software developers effectively reflect on and adjust both the problem being solved and how it’s being solved.
8/9
And we've had these programming languages for over 60 years. Java's 29 years old and has had 22 major versions.
With every update to its syntax, Java's authors have tried to make Java and the codebases written in it more understandable to humans (with rare exceptions).
4/9