Some find fulfillment from work, and others don’t. The stereotype in tech, especially at startups, is the uber-driven people out to make a name for themselves. But we don’t have to live like that if we prefer not to. Plenty of people do solid work and go home and enjoy their lives outside work, and there is no shame in that. It’s ok to feel disinterests at work.
Software Engineering ⚙️
Relay folks have pushed for this issue quite a few times, but I never understood the pain points. This GraphQL Spec RFC helped me know why by juxtaposing component-driven development with fragment-driven data fetching.
This article is outdated, but I enjoyed reading it, learning how games are developed. I found two points interesting: first, they use LFS to version control binary assets that Git cannot handle, and second, they also employ modern development methodology like feature branch deployments.
This article has some cool stats on how Apple adopted its language and framework, Swift and SwiftUI. Even though Swift is growing rapidly, Apple developers added more modules in Objective-C than in Swift (528 vs. 316), demonstrating the power of inertia and status quo.
I was surprised that the survey found salary transparency as the second most important factor for employers. I suspect that that’s another way for the developers to say they feel underpaid. I am curious how many decide on that factor.
Communities of Practice are similar to guilds that I shared a few issues ago. I found this article insightful as it defined the lifecycle of the communities, complete with shutting down. All good things have an end.
The author says
people choose to work for companies for many reasons, reasons that an outside observer may not be aware of (nor is it any of their damned business anyway).
While it is simple to argue this way, this position reminds me of Adolf Eichmann. I am not equating working at a tech company with war crimes. But there are shades of gray.