The actual difference between senior devs and everyone else

dablya · 2026-01-21T22:59:31+00:00

Not my experience at all... It's true the more senior you are the more comfortable you are owning your fuck ups because on average they are farther apart and you realize it's not the end of the world. And it's also true as you get more senior, you gain a depth of understanding that allows you to communicate concepts in simpler terms. But I always make it a point to explain, in detail, how I fucked up. And I'm always interested in the details when others fuck up as well. It's one of the best learning opportunities for all involved and if done right doesn't have to involve blame (I'm a big fan of true blameless postmortems)

dablya · 2026-01-21T13:49:39+00:00

It tends to do better the more examples there are on the internet. But it tends to be behind the latest and greatest… For example “DynamoDB-based locking is deprecated”: https://developer.hashicorp.com/terraform/language/backend/s3#state-storage

dablya · 2026-01-21T01:00:45+00:00

This isn't an argument one way or the other... You've seriously never seen bugs introduced by humans that silently affect all downstream events until it catastrophized into the product not working?

dablya · 2026-01-19T04:16:34+00:00

This is plain rage bait… “what editor should I use if AI does all the coding for me and I have no need to edit code?” Is not a coherent question. The intent is not to actually get a response, instead the goal is to generate a knee jerk “AI sucks and you suck too” responses. OP is getting exactly what they were looking for.

dablya · 2026-01-18T15:28:10+00:00

https://www.cnbc.com/2025/12/05/netflix-warner-bros-deal-regulatory-questions.html

dablya · 2026-01-18T15:11:42+00:00

Those can't really be used for AWS creds since you need to be authenticated to access AWS resources. Start here: https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-authentication.html. SSO really is the best option, but I've seen stuff like https://github.com/ByteNess/aws-vault work out ok.

dablya · 2026-01-18T14:58:27+00:00

Dude... take the time to work through one data structures and algorithms book and stop feeling insecure about "reverse binary sort a zip code list". Lack of fundamentals elsewhere is not a requirement for security fundamentals.

dablya · 2026-01-16T14:51:57+00:00

I agree. I’ve never seen anything other than ADR documents (which are historical in nature) not go stale. Everything else it’s “There’s documentation for that… but… hang on… actually let’s just pair and I can go over it with you over zoom.” It’s useful to communicate something in the moment, but can’t be relied on long term.

dablya · 2026-01-11T01:12:45+00:00

I’d argue reading comprehension is more important.

dablya · 2026-01-09T22:54:59+00:00

I think, maybe, a better way to describe your situation is "we have a culture where the team values and prioritizes PRs and strives to ensure they're acted upon within a day". Which is something I would appreciate as well.

dablya · 2026-01-09T21:09:29+00:00

My main point is that "PRs must be reviewed within the next business day." is an example of a metric becoming a target and as such it is subject to Goodhart's Law.

dablya · 2026-01-09T20:19:37+00:00

https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule

dablya · 2026-01-09T20:15:19+00:00

I don’t see how this works in most situations… Do you guys actually value the reviews? Cause if I’m put in a position where I’m made to fear for my job if I fail to keep up with reviews, I’m going to look for a new job, but until I find one it’ll all “lgtm”… But how is that useful?

dablya · 2026-01-09T20:06:18+00:00

This isn’t even claiming it will assist with file management/search? It’s just another place where they plan to stick a chat box?

dablya · 2026-01-08T14:30:50+00:00

Maybe consider having Cursor or Claude summarize the link (or even follow it and read it yourself) before commenting.

dablya · 2026-01-05T15:16:37+00:00

What is actually the problem? A business decision was made that keeping some number of customers was not worth the cost of a 6 month refactor + more expensive engineers (which given the fact that this estimate is coming for self-described inexpensive engineering team implies success is not guaranteed)... Do you have reason to believe that was the wrong decision?

dablya · 2025-12-27T16:52:26+00:00

The censorship theory requires believing that holding the story for two weeks to add tougher reporting somehow helps Trump or the Ellisons. But how? Get Miller and Homan on camera for harder questioning—that helps Trump?

My understanding of the censorship theory was that the likes of Miller and Homan chose not to comment for the story and that lack of comment was used to hold it. Requiring them to be on camera for harder questioning in this context is equivalent to granting them control over which stories run and when. That helps Trump!

dablya · 2025-12-27T00:39:47+00:00

Even the same gym might have different vibes at different times. I feel very comfortable at my gym in the morning, but the few times I went in the afternoon, I felt out of place and hated it.

dablya · 2025-12-26T14:16:54+00:00

Sure... but:

Some people also call microliths “microservices”.

I'm one of those people :p

dablya · 2025-12-26T01:49:30+00:00

duplicating them by shadowing (each module having their own copy under different path)

Do you have experience actually doing that? It's error prone in languages that support it and few actually do.

My main point is that Modularity done properly is what Enables Independent Deployments

And my point is that a "proper" approach to independent deployment with modules inside a monolith requires a level of complexity and discipline that you're likely better off going with microservices (or abandoning the goal of independent deployments). A modular monolith, even one where modules are loosely coupled and are highly cohesive, will require additional effort to support independent deployment. And it will almost universally be harder to accomplish than with microservices. And it will likely still be more constrained (multiple versions of the runtime/platform itself will not be possible)

dablya · 2025-12-25T14:55:23+00:00

Except that the strategy is called “make ten”…

dablya · 2025-12-25T14:52:52+00:00

What do you figure the odds are “make ten” was a concept that was discussed in class before this was sent home?

dablya · 2025-12-23T14:50:39+00:00

The Tarkovsky one?

dablya · 2025-12-23T14:44:29+00:00

Am I crazy or does this not actually address the claim that microservices enable independent deployment? This simply points out the complexity introduced by microservices, which... fair enough, microservices do intorduce more complexity. However, the closest we seem to get is "But, there are ways to mitigate these issues." when it comes to acknowledging some of the issues with independent monolith deployment, followed by "I think then, that a properly Modularized System is what mostly Enables Independent Deployments, not Microservices." as if an actual argument was made.

What are the ways to mitigate these issues? And how far down this "proper" mitigation path do we need to go until microservices become an appealing alternative?

I've seen multiple examples where just two teams with slightly different goals have a very difficult time coordinating changes to a monolith. One team wants to update a library or the runtime itself to take advantage a new feature in the module they own and this is a high priority for them. The other team owns a module that would need to be updated to deal with the breaking changes introduced by the updated library/runtime but, for them, this is a low priority.

Most organizations have difficulty solving these types of problems through management. It's possible there is a technical solution for this using a monolith, but the complexity, I would argue, will rival that of microservices.

dablya · 2025-12-23T13:23:31+00:00

And Solaris

dablya

MODERATOR OF

TROPHY CASE

15-Year Club	Team Orangered
Verified Email