Luciana Vitale
vitale-lu.bsky.social
Luciana Vitale
@vitale-lu.bsky.social
Reposted by Luciana Vitale
I retired in March, but today's React vuln should remind everyone that @charity.wtf has always been right: if you have a holiday code freeze, your build-test-deploy-rollback process is completely broken and you should not work on anything else until that's fixed.
December 3, 2025 at 5:35 PM
Reposted by Luciana Vitale
Impact-driven promotions almost always (eventually) lead to promotion-driven development. Little wonder it's so widespread throughout Big Tech and larger companies.

Full: newsletter.pragmaticengineer.com/p/preparing-...
December 9, 2025 at 8:32 AM
Reposted by Luciana Vitale
I tell this story periodically, but it seems like it's time again:

General Motors ran an automobile manufacturing plant in Fremont, California, that was one of the worst in the country. Accident rates and defects were astronomical. Absenteeism was through the roof.
1/12
December 4, 2025 at 5:53 PM
Reposted by Luciana Vitale
The meaning of pragmatism as a term has been hijacked to mean subjectively justified hacking and piling up a mountain of cruft.
A "just dump it under the rug while no one is looking" development.
November 27, 2025 at 6:35 PM
Reposted by Luciana Vitale
Wild to me that a CEO sets goals about outcomes that have nothing to do with the business (are customers more satisfied? Is the product more reliable? Etc.)

Setting the goal of what % of code should be AI-generated is as useful as setting the goal of how many lines of code devs should write per day
September 4, 2025 at 6:40 AM
Reposted by Luciana Vitale
Working in high-quality code improves development speed by as much as 7x. Mob/Ensemble programming can give you a 3x improvement. Getting rid of bottlenecks also yields major improvement. You get the idea.

None of the above impacts outcomes.
4/5
June 8, 2025 at 4:23 PM
Workarounds are easy to see in a code base. When you're looking at one, you instantly know. It's a big code smell.
January 19, 2025 at 12:39 PM
Reposted by Luciana Vitale
Have you ever sat down with a couple of workmates to track down a bug or solve a tricky problem? Congratulations—you've done Ensemble Programming. Worked pretty well, didn't it? So why not work that way all the time?
January 17, 2025 at 7:46 PM
Reposted by Luciana Vitale
Messy code and fancy code are two sides of the same coin. Code can become confusing and deceitful by either neglect or ornamentation.

*Clean*/*good*/*expert*/*professional* code--call it what you may--isn't opulent, decorated, fancy, high-concept stuff.

It's profoundly ordinary.
December 20, 2024 at 12:11 PM
Reposted by Luciana Vitale
Amen, brother. 🫡

🤍❤️💚❤️💚🤍
December 2, 2024 at 5:55 AM
From deadline to *deadlock* in 3 simple steps:

1. We do not use deadlines.
2. For this particular super critical thing we can try introducing a deadline.
3. Wow! that was a success. Probably the deadline is the reason. Let's introduce deadlines for every single meaningless task.
October 5, 2024 at 5:51 PM