bethcodes.bsky.social
Sr Staff Engineer supporting agile cultures that let developers build software well & help them learn how to.
Mediating a new scientific revolution associated with the night dream of post-industrial society
any/all
1,298 posts
1,449 followers
620 following
Regular Contributor
Active Commenter
comment in response to
post
As a Unitarian-Universalist, I couldn’t disagree more. We don’t need to sacrifice our religious freedoms to build towards justice.
comment in response to
post
Absolutely. I appreciate that they called out the architectural debt in the component, but they didn’t get into the whys of that.
I would be looking into our code review culture, deadline management, goal setting, pairing or lack thereof, aesthetic critique, testability of the code, size of PRs…
comment in response to
post
That is one of the reasons I think it is important to be transparent about whether AI played a role.
Tasks, and languages, may be more or less conductive to AI-assisted coding. Using tools where they are not appropriate can cause significant damage.
comment in response to
post
Why triple instead of double? In disfunctional organizations they are going to come back & say whatever you said is too long.
At that point, do another week of implementation & come back with “we’ve figured out options that let us cut a third of the time!”
Unless the project has launched by then 🤷
comment in response to
post
It stopped austerity in the US, while austerity went ahead in Europe & crushed their recovery.
The long term impact was mostly just putting Warren in Congress, but the immediate effect was stopping Larry Summers from cutting off unemployment.
comment in response to
post
When we get a video of ICE and the Proud Boys fighting outside a uniqlo we will all know what happened
comment in response to
post
When we get a video of ICE and the Proud Boys fighting outside a uniqlo we will all know what happened
comment in response to
post
It is possible to have reactions without posting them on the internet.
It is fine to feel the feelings, but as soon as we are participating in the backlash against a Black woman standing up for trans people we are just participating in the backlash to a Black woman standing up for trans people.
comment in response to
post
By “more than just what they deliver”, I mean things like “communicating to executives & translating back”, “building process”, “coaching folks across roles”, “crafting engineering cultures”, and other things besides writing software
For writing software, Sr/Lead is the terminal role.
comment in response to
post
Those are also different jobs, taking responsibility for more than just the software one personally delivers.
I find that misunderstanding often frustrates senior engineers who don’t understand that “Staff” isn’t just a promotion: it is a different job they would start doing to get the title.
comment in response to
post
Now I understand what the disconnect is. I agree that we don’t see people over 50 systematically paid more than a younger person for doing the same job.
I disagree that that is unfair, but I agree that we don’t see that.
comment in response to
post
I would bet it is worth making them actually do that work, and then throwing a fit about how they are disrespecting the traditions of the Republic.
comment in response to
post
What role is there “beyond” Lead that isn’t something architect-y, at any age?
Maybe this is my time in other professions coming through, but I’m confused by the idea that a trade would have an endless career ladder. If we want to keep doing the same job, why wouldn’t it be the same job?
comment in response to
post
If you have a reference, I’d be interested in reading more.
comment in response to
post
Leverage Research was ahead of its time
comment in response to
post
I can believe people looking to make more money move into other roles, but I am less convinced that it is the norm. The median age of a computer programmer in America is 43, compared to 42.2 for all workers.
comment in response to
post
Is it? The last time I looked men didn’t leave software engineering at higher rates as they aged than other professions.
Which isn’t to discount the alienation of moving from “most folks are older” to “most folks are younger”. But the meme that older developers are invisible is odd to me.
comment in response to
post
Like a bug-a-thon: we choose some priority and the entire team focuses on that, without worrying about planning, pointing, relative prioritization or other process overhead.
comment in response to
post
Huh.
The profession grew fast during the cell phone revolution, which brought younger people in, but I’ve worked with my grandfather’s coworkers. At my first tech job I was less than half the average age.
comment in response to
post
IMO a huge part of the problem is that open-office floor plans are *so* sub-optimal for everything except real estate costs.
There are offices I would go back to (if I wasn’t bringing extra skills to remote teams), but it isn’t most of the offices currently available.
comment in response to
post
Part of why I have stuck with remote work is *because* it is a different challenge and requires different skills.
Having built some of those skills (largely by accident), I can be of greater use in a remote workplace.
comment in response to
post
I have seen the best results when there are at least three ways people connect with coworkers on a weekly basis:
* With people working on the same goal
* With people doing the same kind of work
* Something random enough to enable happy coincidences
comment in response to
post
I found that my experience building World of Warcraft guilds, online communities and distributed event teams translated, but also without that (unpaid) experience I would have had no support at all.
comment in response to
post
I find it makes Staff+ roles particularly impactful. Those folks can have the energy, focus & autonomy to be proactive about building relationships, reading what is written & actively facilitating cross-team culture.
comment in response to
post
I don’t think we need to rely on model-based claims the empirical evidence doesn’t support.
We could directly value medical residents & their well-being. They are also people whose health matters.
comment in response to
post
Which research were you looking at? My statement was informed by metastudies like www.acpjournals.org/doi/full/10.... and meridian.allenpress.com/jgme/article...
comment in response to
post
Part of the challenge is that while it is bad for doctors, it isn’t bad for patients. And the profession, admirably, cares more about the second than the first.
comment in response to
post
I don’t think that is necessarily a bad thing.
We are asking people to ignore their personal interests in favor of the patient’s interests. Ordeal rituals are one of the few effective tools we have for build a shared professional identity capable of resisting individualistic pressures.
comment in response to
post
Interestingly, EHRs weren’t found to have a systematic positive impact on patient health, though they reduce medication errors & time spent documenting. Reading is still reading.
On the other hand, increasing the overlap between shifts is effective but expensive: medicine.tums.ac.ir/uploads/296/...
comment in response to
post
There is an interesting question of what the best EHR would be. It likely varies by hospital/specialty (while still being perfectly interoperable).
Building software well is expensive. Trying for “best” would raise healthcare costs further, so mostly we aspire to “good enough”.
comment in response to
post
It’s telling how none of their “controversial” opinions are ones that challenge systems of power, like “prohibition dramatically reduced alcohol consumption & domestic violence” or “lead exposure impairs self-control” or “therapy is useful”
It’s all just “what if Republicans’ desires were correct?”
comment in response to
post
That just sounds like an estimation problem 😉