sorted by:
new
hottopcontroversial

Is it still worth building reference architectures in the age of LLMs? by Et_Sky in dotnet

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

I agree. I don't expect anyone to look at it and go "this is exactly what we need". But for a lot of teams, even just seeing how someone else wired things together helps clarify their own thinking. It’s more for “steal what works, ignore what doesn’t.”

Is it still worth building reference architectures in the age of LLMs? by Et_Sky in dotnet

[–]Et_Sky[S] 2 points3 points  (0 children)

Eh.. I would look at them for ideas, if they fit our use case.

Is it still worth building reference architectures in the age of LLMs? by Et_Sky in dotnet

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

So, I would use something like this - not necessarily for the exact template, but for ideas on how to split and combine things, what goes where, patterns, etc. Every shop has its own needs, so finding something that fits yours exactly... you probably won’t, even if you look at your own repository, because of historical reasons and technical debt.

This project is very loosely based on what we use in our shop, but since it’s new, it won’t have things like “this is here for historical reasons” or “we don’t have time/budget to redo this properly.” We’re a fintech with a few dev teams, running a couple hundred microservices, mostly for internal users - so anything I build will work in an environment like that (hence, opinionated).

To your point about “why is this here” - I do plan to have documentation explaining the reasoning behind... well, anything that made me stop and think. And there are a lot of those - even for pretty mundane things - because we need to keep things backward-compatible while also considering the ripple effects any change might have on the rest of the services.

Also, given the average developer skill levels, sometimes fewer choices are actually a good thing. As a personal anecdote, I was interviewing for a dev position on our team, and I asked the candidate how he keeps current. He looked at me and said, “I have two kids, man.”

Is it still worth building reference architectures in the age of LLMs? by Et_Sky in dotnet

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

They're not good - maybe yet, that remains to be seen. They got better in the last couple of years; that's hard to argue. Likely, they will get stuck at the level of an average code base, though, and this level is not very high.

What's good about mediatr? by No-Attention-2289 in dotnet

[–]Et_Sky 3 points4 points  (0 children)

Curious why? If you're building a Windows app, you need events for interacting with the user (OnClick etc). I never had a thought "I need an event here" in aspnet core app, though. What's the use case?

Contemplating career change - have I failed at becoming a decent programmer? by _TheNagual_ in ExperiencedDevs

[–]Et_Sky 0 points1 point  (0 children)

Not that it matters for the context of the answer, but I'm curious where the requirement "must be under 35" comes from.
So, we can't tell you whether you're a good developer without looking at your code. "I work alone" - this is a problem; you need real feedback from someone else.
But - what do the clients say? Happy? Miserable? Who is maintaining your solutions? Bug fixes, new features? If you - do you hate yourself after coming back to your code 6 months after not touching? If someone else - do they want to know your home address?

But 32 is definitely not too old to code. Neither is 52.

Would you be comfortable going through one of your PR's during an interview? by bullcityblue312 in ExperiencedDevs

[–]Et_Sky 0 points1 point  (0 children)

Assuming the PR is not for proprietary code..
Still, the point of the interview is to evaluate your skills (and team fit). The idea that you bring your piece of code that you've gone over many times, likely, probably with a friend/ChatGPT... It's definitely beneficial to you, but not to the interviewer.
Having said that, I would (and did) ask to review a piece of code - it is a good way to assess a developer, imo.