That being said i understand how it works at a high level.
60 karma · joined July 29, 2017
That being said i understand how it works at a high level.
Proemion is providing an all-included remote telemetry service for industrial machinery. We develop hardware, firmware and software to collect remote machine telemetry, analyze it and provide in a way that empowers manufacturers and their customers to use the machine better.
The position is for the web services driving the analysis, reporting and our web portal.
Our tech-stack is mostly in java.
https://career.proemion.com/en/jobs/it-software-development/...
So I wouldn't cross out "staring at a wall" as inarguably invaluable. It's what's going on in your head when you do it. Same as when reading that book.
But in an of itself doesn't create anything. Mindless content consumption doesn't even leave memories sometimes, what to say of ideas.
At the same time, my current role has a neat balance of technical and softer aspects. So why chase the "career" if I'm already in a good place. Focusing on my family and out of work priorities just makes so much more sense.
It's probably the first time, I've rejected a path to a promotion.
Simple avg, etc were better, but always clickhouse was an order of magnitude faster than timescale. We didn't invest a whole bunch into optimization other than trying some indexing strategies in timescaledb.
So for our use case the choice is clear.
GS is a big company. There's lots of people there. Some 8k people are in the tech division. And the employer competition there is not just with other financial firms. But also with the rest of the tech sector.
So as other commenters say, if other places offer similar conditions, but also remote work. It may be a differentiator. In practise though - working from home for tech some days a week has been totally normal for years. So I expect little actual impact on the company.
Switched the missus as well. Since it easier to have a homogenous set of machines.
She's as non-technical as they come. But browsers work the same. So she hardly noticed. Most modern casual usage is on the web anyways.
And for advanced things I haven't yet found a thing I couldn't easily do.
But if you're just the average developer, like most of us really are - the higher competition will surely make it harder to negotiate higher pay.
So you wouldn't get a random version even considered.
Version shadowing and overriding is a totally different concern of course.
Fixed versions for as many things as you can (including OS images, apt packages, Docker images, etc) lead to changes in your CI under your control.
Sure, you have to upgrade manually or by a script. But isn't plain build stability worth it? Not even talking about security.
- define what productive means for you. The narrow definition of "doing work" won't work for the missus, kids. And your general well being for most of us. The author doesn't dive into that. I guess because the article is already too long. My take is - doing the things that matter. - Being meticulous and ruthless about removing garbage getting in the way. And for that all the data and tracking help.
But a legal entity in Pakistan have to obide by those rules. And if it's profitable - they will.
Replace Pakistan with any other country name, the argument doesn't change. It's the law in that jurisdiction.
You can't really mix and match the legislation you like and don't like.
No idea if the particular law is just, but that's not the question. The question is - is it profitable to abide by it?
I've gone from IC to team lead, to group lead. I think this is my limit at the moment. Not because I'm remote, but that's how much I can handle at the moment.
I don't get some of the hallway chats from the mothership, but the feedback routinely is that we're one of the strongest groups in the company. So I would take that as a sign that the remote aspect isn't a deal breaker.
Personally I wouldn't go back to the office routine unless I was out of options.
And yes, I do spend 80% of my time in various calls. This is not different from being in an office and working with a distributed team (also in offices in their regions).
As someone who's been through internships and many years of in office work this is worrying me too.
Our junior colleagues coming in without the little things they would get from sitting in a room with everyone else.
Without team lunches and social events. Because it's not direct impact this is hard to reason about and create artificially.
I chose to work remotely full time 4 years ago and I have to rely on my past years of experience quite a lot.
What I do see is that excellent mentors and senior colleagues still find a way to mentor less experienced colleagues. It just takes conscious effort from both sides and we need to support both sides more in this.
I'm very keen to study this in my teams and use the learnt experience to raise the base level.
Especially because those 3 are unlikely to come back.
My personal expectation is that there is a lot of developers out there and at least at non-junior levels the differentiating factor is skill, experience and timezone, as you say.