rc_hackernews
Joined 6 years ago
Joined 6 years ago
Love Rails, but found it very difficult to learn Ruby. It's very hard for me to read, but that may be because I come from a C# background.
If you're looking for something like Rails, I'd recommend trying out Laravel.
It's on par with Rails as far as features, ease of use, etc. And PHP was a lot easier to learn for me versus Ruby.
C# is still king, but it’s been getting a few features from F# the past few years.
I haven’t played the first one, but the second one is excellent and is my favorite game of the year so far, and probably last year too. And as already mentioned, it plays great on the Steam Deck.
I highly recommend it.
It's either what you mentioned or they have very outdated development practices.
I'll keep in mind how comments like that come off in the future.
Friends in late 20's to early 30's have had a lot of trouble conceiving, i.e. they needed to do IVF.
Not sure what's going on with that, and this is purely anecdotal, but I've been hearing people having troubles having kids a lot it seems.
I think it’s easy to say we as engineers should make things simpler. I have no idea how to do that in practice on a team though.
Once the complexity started to creep in, seems like a wave just kept sweeping everyone towards more and more complexity.
Was talking to a recruiter who specializes in recruiting for tech and product companies. The C# positions he had topped out at what other languages started at for senior developers.
I like C# it’s just it feels like it’s all enterprise jobs with bad development practices.
Should’ve said “Heroku-like” instead of “Heroku for AWS”.
My main complaint as an application developer these last few years is the amount of time I’ve had to spend wrangling infrastructure.
I’ve been noticing what you’ve posted for awhile in regards to interesting opportunities and .NET, or lack there of.
Not sure how to make the switch to something else though.
And like you said the organizations that pay very well...don't tend to use .NET. Which is what I've been seeing "in the wild".
At this point, it's just becoming increasingly hard to justify sticking with it. Especially considering I could make more money and not have to deal with so much legacy or poor development practices all the time.
In defense of those organizations though, in my experience, the interview processes have been very reasonable, i.e. no LeetCode. As long as you haven't been sleep walking through your career, it should be pretty easy to get a new position.
I'm about to start a new position that uses C#/.NET and seems like a technically mature/sophisticated organization. Finding this position was hard though.
If that fell through, I was thinking of ways I could try to switch tech stacks. As you stated, the types of companies that gravitate towards .NET are not the types of companies I want to work for anymore.
Not to mention, after talking to several recruiters, it seems like salary for .NET devs are much lower than counterparts in other languages. I'm probably at the top of what I can expect to make as a senior engineer in .NET. I spoke to a few recruiters who recruit for other stacks and my salary is what senior devs typically start at for those organizations.
Outside of a few areas related to DDD, event sourcing, and some distributed-system frameworks (NServiceBus and MassTransit) there's really no killer app for .NET, in my opinion.
The big selling point for .NET now is that it runs on Linux...which is not really a selling point in the grand scheme of things.
It was really bad, but I was fresh out of college and had no experience.
Took me about 10 months to find a job in that market.
The market is definitely rough, but I wouldn’t say it’s that bad yet.