News for hackers. Stuff that matters.
Re:Best practices for remote software engineering by TeeMassive on Monday April 26, 2021 @11:59PM (#26951855)
I'm in the same boat right now. Since my company insists on using an "air-gapped" development network (it basically means no internet connection, but that didn't stop the Chinese from copying our code and designs but I digress) we have to go through two different VPNs, which means remote desktop lag. Usually I don't mind for a few days, but after more than one year I just can't stand it, especially when we're we're forced to used an early 2019 version of Visual Studio, so it's reallyyy slow. I just can't stand it anymore. Sometimes I'm allowed to come back at work and it's day and night in terms of productivity.

I'm getting contacted by headhunters left and right every months but I'm still reticent to leave because we're short on staff and the project I'm working on is really important for the company and I've was kinda hired to bring those things into reality as the other devs are mostly technical experts in their fields than actual developers and in addition the code is ugly.

So yeah. Sucks.

Re:Best practices for remote software engineering by flafla2 on Tuesday April 27, 2021 @05:38AM (#26953823)
> I'm getting contacted by headhunters left and right every months but I'm still reticent to leave because we're short on staff and the project I'm working on is really important for the company and I've was kinda hired to bring those things into reality as the other devs are mostly technical experts in their fields than actual developers and in addition the code is ugly.

Red alert. You basically just wrote “I should quit tomorrow”.

Re:Best practices for remote software engineering by PoignardAzur on Tuesday April 27, 2021 @05:48AM (#26953890)
Wait, is there an ethical reason you think the project should be completed? Like, it's really going to help starving orphans or something?

Because otherwise you should quit yesterday, like the others say. You don't owe them nuthin'.

Re:Best practices for remote software engineering by TeeMassive on Tuesday April 27, 2021 @10:15PM (#26964670)
> Wait, is there an ethical reason you think the project should be completed?

I had a higher salary than demanded because they needed me to complete the task. Sure I could quit, it's just I'd feel bad about myself.

>ike, it's really going to help starving orphans or something? Because otherwise you should quit yesterday, like the others say. You don't owe them nuthin'.

Can't deny the logic of that.

Re:Best practices for remote software engineering by arvinsim on Tuesday April 27, 2021 @12:09AM (#26951915)
Company loyalty is an outdated concept. You are the CEO of yourself so that should be your first priority.
Re:Best practices for remote software engineering by lostcolony on Tuesday April 27, 2021 @12:15AM (#26951949)
Get out.

All your reasons for staying have to do with the company; not you. Unless -you- want to see it to completion, that is not a good reason. You do not owe the company anything.

Re:Best practices for remote software engineering by titanomachy on Wednesday April 28, 2021 @02:18PM (#26972377)
Everyone is saying you should quit, which might be a reasonable suggestion, but it sounds like your issue is with working remotely. It sounds like you are able to be very productive and get satisfaction from your work when you can come into the office. If you don't want to quit, you could alternatively demand that they let you work from the office or relax development security. If they realize that saying "no" means jeopardizing the project, you might have some leverage.