Stardew Valley

Yes. You corrected a dyslexic. Well done.

That is more down to poor marketing. Here on Lemmy or reddit there are big open source communities where you can extol the values of it.

I never went with a software project from random scrolling. It has no value to me if it doesn’t meet a need I have right now.

No contributor is going to be good that doesn’t use it.

Why would it be? Software is good based on it’s use and recommendations from real folk, not *s. Many project not on github

That is quite a mixed bag response. Leaves me between they won’t do nothing, and they might do something.

Anyway, that’s enough about yourself…

Feels like you never truly where on Reddit if you felt it was a beacon of warmth and friendliness. Did you ever share an opinion contrary to the prevailing opinion on there?

I wouldn’t recommend staying with a company for 17 years. That’s for sure. Best way to get stuck in a company specific niche skill that is not transferable. For the reasons stated you got to keep yourself positioned well skills wise and relevant so you can jump into any role you need at any time.

Integrity is not for the company. It’s doing things the way you think they should be done and earn your own respect.

I would say all companies don’t replace with cheaper. Many do. Especially the shitty ones. It’s quite easy to avoid those like the plague. Many did, and learnt the hard way, many have staff that have seen failed outsourcing and are in a position to influence that.

Soloing knowledge doesn’t keep you safe though as the penny pinching companies will remove anyway and clean up later regardless. It does not keep you safe. It’s a false sense of security. Complacency is a death sentence in software development.

Professional integrity. Have you ever worked for a company that got screwed by a consultancy? Vendor lock in and charging scandalous amounts for little offer.

You are paid for your skills and your time. If you’re confident in your ability and impact, you shouldn’t have to be worried.

I’m not saying sacrifice for yourself for your company, and if they are a shitty company that would replace you with cheaper, get out, but also, giving nothing for the pay you get is a bit dishonest, and then you are no better than them.

Plus, you make the case that hiring people is bad and paying a consultancy is less risky.

Of course Jared didn’t document anything and made themselves a bus factor. Real success is when Jared makes themself replaceable because hiding detail and making yourself critical is the best way to take a site down when you’re on holiday and prevent other team members stepping in and taking ownership.

Not perfectly optimised is fine, but non-functional isn’t acceptable. I’ve never seen a quirk personally, and quirks aren’t a good reason to help maintain Google’s monopoly on web standards.

You may say less than 5% is fine, but it could be the margins in a low margin industry. 2% could be 40% of the profit.

I haven’t seen a team operate where a senior isn’t checking it.

Usually the bleeding edge stuff is used by small companies trying to establish themselves because they have nothing to lose and no reputation to protect.

Plus, when you got Browser Stack, you catch a lot of problems like this.

Because in web development there are compatibility tables of what features work with which browser. If a developer has used a feature poorly supported, they either haven’t done their homework, or intentionally made that call.

In web development, most reputable Front End Devs would not choose bleeding edge, barely supported features even if the temptation was there because the user comes first. Generally, you wait until it has been adopted by the main browsers (chrome, safari, ff).

Isn’t this just the tech version of cuckooing?

https://en.m.wikipedia.org/wiki/Cuckooing

Illegally using someone’s property to make profit from dodgy business.

I didn’t drink or have sex for a big proportion of my life (until 16). Was quite happy to ditch old habits.

The thing is, chrome was probably built for spying.

Never noticed an issue and if websites using only chrome supported features, it’s an issue with the website, not the browser.

Blender or GIMP? Idk.

Unit tests, yes, but you don’t only do unit tests. Integration and e2e tests still exist.

Was there even tests?

I’m not sure what’s with your first sentence. Everything else you said agreed with the point I was making…

The issue is your mindset.

You write bugs because you have something to learn. You’re so focussed on what you’re making, that when a learning opportunity arises, you are not open to it. You’re just looking to speedrun/hack it.

You need to drop the delivery pressure and enjoy the journey. When a bug comes up, celebrate it “ah, you got me here. Interesting. What am I missing?”. Then you slow down, focus not on solving it, but understanding it. If you understand it, the solving is easy.

If you consider learning “not progressing”, then you need to reflect on what benefit the pressure and delivery focus is.