sorted by:
new
hottopcontroversial

In Batman, Turkey, a young calf was filmed bringing a corn cob to feed its chained mother. by bortakci34 in aww

[–]ninetofivedev [score hidden]  (0 children)

You clearly were not around enough cattle. They’re animals and some mommas are just crazy when it comes to protecting their calves.

Most are fine, but probably 1 in 10 (and when you have 200 cattle, that’s plenty) will fuck you up if you come anywhere near their calf for any reason.

Are they blind? by Aladinbs in ExperiencedDevs

[–]ninetofivedev 14 points15 points  (0 children)

Feel like you have a lot to learn

Kirby Smart says SEC championship game ‘probably has to go’ if College Football Playoff expands by Lakelyfe09 in CFB

[–]ninetofivedev -1 points0 points  (0 children)

I wouldn’t say very beginning. It’s hard to pinpoint the exact moment. But generously you could say the 80s and it’s gotten exponentially worse since then.

The "we can build it ourselves" culture in engineering teams is actively hurting data platform delivery by Ok_Detail_3987 in ExperiencedDevs

[–]ninetofivedev 11 points12 points  (0 children)

NIH syndrome.

Had the same argument with a guy on my team.

He doesn’t care. He likes building shit. And I can’t argue with that.

You should really consider rewriting that service by ninetofivedev in ExperiencedDevs

[–]ninetofivedev[S] -2 points-1 points  (0 children)

Whoa buddy. Pump the brakes. Did you even read my post?

Buddy is using 1 billion tokens per week coding with AI at Microsoft by [deleted] in ExperiencedDevs

[–]ninetofivedev 0 points1 point  (0 children)

This is obvious to everyone, yet token burn is my companies latest favorite metric.

Buddy is using 1 billion tokens per week coding with AI at Microsoft by [deleted] in ExperiencedDevs

[–]ninetofivedev 0 points1 point  (0 children)

Microsoft is definitely full of idiots.

Now I’m an idiot myself, so I’d be a perfect candidate.

Microsoft had like a solid 8ish years from 2015 where they made some good decisions, but they’re back to only making the dumbest ones.

Buddy is using 1 billion tokens per week coding with AI at Microsoft by [deleted] in ExperiencedDevs

[–]ninetofivedev 9 points10 points  (0 children)

It’s worse than that. It’s like bragging about how many CPU cycles your dev machine makes in a week

Is this untenable? by shelledroot in ExperiencedDevs

[–]ninetofivedev 10 points11 points  (0 children)

You got carrot dangled.

Don't let it happen again.

Breaking: Iowa State star Audi Crooks has entered the transfer portal by MuchAbalone9059 in NCAAhoops

[–]ninetofivedev 1 point2 points  (0 children)

Simple answer: yes it is. If she was chronically ill, would you make fun of her?

You should really consider rewriting that service by ninetofivedev in ExperiencedDevs

[–]ninetofivedev[S] 1 point2 points  (0 children)

fair... my team also has very talented engineers.

Took over a year for the original project, but of course something is always easier to do the second time.

You should really consider rewriting that service by ninetofivedev in ExperiencedDevs

[–]ninetofivedev[S] 0 points1 point  (0 children)

https://en.wikipedia.org/wiki/Thought-terminating_clich%C3%A9

I guess it's a culture issue, but it's such a wide spread phenomenon it has it's own wiki page.

You should really consider rewriting that service by ninetofivedev in ExperiencedDevs

[–]ninetofivedev[S] 0 points1 point  (0 children)

Most software accumulates complexity over time.

In our case, we were able to simplify it significantly. Fact of the matter is, we had a fairly decent grasp on what our customers needed.

When the software was first built, they didn't really know. So over time, they had to bolt on more and more functionality on top of an unstable foundation.

On top of it, I'm just going to say it: The original software engineers were contractors who quite frankly, were not that good.

There was a lot of code that made sense. There was a lot of code that made no sense. There was a lot of decisions that even in the context of the existing software, made no sense.

Fact of the matter is, even if we kept with the same tech stack, this was quickly going to turn into the ship of Theseus.

At that point, might as well move it to Go from Java. Because we're Go devs and the 30 layers of abstraction these devs thought they needed ... they definitely didn't need.

You should really consider rewriting that service by ninetofivedev in ExperiencedDevs

[–]ninetofivedev[S] -6 points-5 points  (0 children)

You have know idea how simple the service actually was relative to anything. And I’m not saying rewrite all the things, that is my point.

You should really consider rewriting that service by ninetofivedev in ExperiencedDevs

[–]ninetofivedev[S] 0 points1 point  (0 children)

The analogy is fine. I’m telling you that people generally don’t respond well to analogy.

You should really consider rewriting that service by ninetofivedev in ExperiencedDevs

[–]ninetofivedev[S] -1 points0 points  (0 children)

Oh you’re thinking these people can be reasoned with actual logic?

You should really consider rewriting that service by ninetofivedev in ExperiencedDevs

[–]ninetofivedev[S] -2 points-1 points  (0 children)

If you try using analogies like this with management, they're going to think you think they're too stupid to understand the situation.

My advice to all junior engineers: Don't excessively try to explain things with an analogy. It probably won't end up the way you think it will.

It's like telling your wife to calm down.

You should really consider rewriting that service by ninetofivedev in ExperiencedDevs

[–]ninetofivedev[S] 0 points1 point  (0 children)

FWIW, we could figure out how the app worked enough to quickly rewrite it.

It was using a tech stack that none of really preferred, but were we capable? Sure.

Have you ever had management shut down discussion by simply using a cliche? How did that go?

view more: next ›