Gonzalo🇦🇷🇳🇱 (@GonchuB) header
Gonzalo🇦🇷🇳🇱 (@GonchuB) profile picture

🎓 Software engineer • I bet on humans writing TypeScript • Opinions are my own

Amsterdam, The Netherlands
Joined June 2009
Photo by Gonzalo🇦🇷🇳🇱 (@GonchuB)Photo by Gonzalo🇦🇷🇳🇱 (@GonchuB)Photo by Gonzalo🇦🇷🇳🇱 (@GonchuB)Photo by Gonzalo🇦🇷🇳🇱 (@GonchuB)Photo by Gonzalo🇦🇷🇳🇱 (@GonchuB)Photo by Gonzalo🇦🇷🇳🇱 (@GonchuB)Photo by Gonzalo🇦🇷🇳🇱 (@GonchuB)Photo by Gonzalo🇦🇷🇳🇱 (@GonchuB)Photo by Gonzalo🇦🇷🇳🇱 (@GonchuB)Photo by Gonzalo🇦🇷🇳🇱 (@GonchuB)
Testing won’t cover for the lack of observability
Quote tweet this with your spiciest web dev take
490
Slack's most powerful feature.
3
1
7
A single cockroach will completely wreck the appeal of a bowl of cherries, but a cherry will do nothing at all for a bowl of cockroaches 🍒 🪳
3
A typology of organizational cultures and their response to anomaly (2 per type). Westrum
2
4
Not Wordle just my GitHub contributions in 2022 ⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️ ⬜️⬜️⬜️⬜️⬜️
1
2
1
16
🔥 🥵 🌶
Hot take: what is holding back most companies in becoming better at tech is that their leaders - CEOs, CTOs, VP Engs - have never worked on high-performing software teams as an engineer. Their understanding of "best in class software teams" will always lag behind reality.
1
monorepo or multirepo with private registry?
1
5
Somebody, somewhere, thought that a slider was a good idea for numeric inputs 🥴
5
🙏 It is not a sprint, it is not a marathon, it is a small plane flown by experienced pilots; the destination is on the other side – at Amsterdam, The Netherlands
Replying to @aboodman
I hear you asking, dear reader, how this miracle came to pass. How did chrome-team manage to deliver high quality software without death marches? Funny you ask... Turns out that software projects actually benefit strongly from having senior technical leadership deeply involved.
2
💯% and I would add L4: Knowing how to transition it iteratively into a system that works how *most* expect it to work – at Amsterdam, The Netherlands
This! 👇 I recently described it 3 levels of (complex system) knowledge: L1: Knowing how a system works L2: Knowing why this system works this way L3: Knowing why this system doesn't work in some other way L1 is in code, L2 is in docs, L3 often only in people's heads.
1
1
Iterate, learn, drive trust 🧠 – at Amsterdam, The Netherlands
Replying to @johncutlefish
Read the thread. Many good points. Some predictable ones. Story points are not inherently evil. Like many things, tools came become weapons in the wrong hands. If you want to see more of my thinking, see my experience report agilealliance.org/resources/…
Tell me you use JIRA at work without telling me you use JIRA at work. I'll go first:
Timebox it and then 🍷 Timeless advice – at Amsterdam, The Netherlands
Replying to @MiaFallon17
🙌 My best advice is to timebox it. So if you want to do extracurricular dev, do it the hour before you start work. Then when work is done, say 5-6pm, literally leave. Go out somewhere for dinner or a walk, or I just murder a bottle of red wine.
2
10 steps towards a software feature: Analyze > Ideate > Refine > Prioritize > Plan > CODE > Demo > Iterate > Document > Release – at Amsterdam, The Netherlands
CSS in JS is cool, but have you seen CS in CSS? – at Amsterdam, The Netherlands
1