That’s why we need to negotiate in block, likely through unions.

Damn, those copyleft extremists!

Why not contribute to the upstream?

I’m speaking in abstract because it never happened to me.

But stuff like this, I suppose: https://www.businessinsider.com/how-bosses-use-employee-tracking-software-for-remote-workers-2023-8?op=1

And then actively using/reviewing these to create competition between people, and/or change how people choose to work.

I kind of get the passive use, and the extreme cases, where people are not delivering and then you find they are not actually working, in retrospect.

Active remote surveillance, no one?

I think failed estimated dates just highlight how much we don’t know about ourselves, our systems and our own knowledge.

It is the abyss of the unknown talking back to us. We have the privilege of having the stuff we don’t know thrown back at us to prove us wrong. And we often fail to be humbled by it.

Most technology, programming languages and frameworks feel just the same, in a professional environment. Majority of web and apps is so simple that literally anything will do. Simple api consumption, simple database crud stuff. The tech stack doesn’t matter that much.

Don’t worry too much about what your team members would think about you. Your team members might not like you for this, but they would respect you. And most importantly, your project manager will know you are a good, confident developer and better than others.”

What kind of crap advice is that? To just learn communication and claim the credits for yourself?

Yeah, you can get a bigger share of the small pie of budget recognition the company will set for your manager to split between you and your team. So instead of a sub-inflation salary review you get a slightly sub-inflation and everyone else gets their slightly lower?

Remember friends. Alone we beg, together we bargain. It’s not unlikely to see collective negotiations get 15% across the board! Stop settling for just being “above others”. Raise the bar for everyone!

It’s past time for us to negotiate as teams of engineering instead of individual devs that think each can just move jobs and get a higher contract. Some people can, but the best of us can’t, because of just how stressful job hunting is.

We only get the fairness we fight for. And as software engineers we have fought for nothing, so far. We surf a bull market and think we got paid for our skills and merit. Surprise: we didn’t. How many people have made way more money than the best of us, just dancing the money dance?

Let’s please strengthen our unions, so that we can negotiate when they try to push these shitty layoff seasons.

Sorry for the rant. :)

Not evil, but not the most common or expected way to modularise thing in js/ts, so your colleagues may have to think for a moment before they get used to your code. It’s valid solution, though.

I think you should do what’s comfortable to you, but also try to adapt to the common language in each of the code ases you will be working on, so that everyone is on the same page.

Typescript is useful, jsdoc type casting is useful, modules are useful.

Good luck in your journey!

That screams inexperience in their end, to me. 20 years in the field, I learned to respect legacy. Can’t move away from it without getting it under control first and then weeding out the smelly parts.