You May Also Like
How would you manage “road tax” going forward?
- June 18, 2023
- 20 comments
I think I’d implement a system whereby you pay tax in a category based on how much impact…
I’ve been out of the scene for some time. Are leather trousers still a thing?
- August 19, 2022
- 18 comments
And if they aren’t, what would you advise as an alternative for an aging lothario?
What instance of bullying at school sticks out vividly in your mind?
- March 30, 2022
- 30 comments
Not something that happened to you, but towards other people you went to School with? I remember when…
4 comments
That’s gonna drastically vary depending on the culture of the company you work for.
Most software engineering roles might have occasional moments of crunch / final push towards a release / “fuck! Something broke and we need to fix it”, but it should definitely not be the norm.
At most, larger, business / web style software businesses in the UK now, people finish generally around 5:30-6:00. Emergencies happen, you might be expected to pitch in. Somebody might even call you at 2AM. This kind of thing happens, but by-and-large a lot of tech companies have really gone big on the whole “reasonable hours” thing.
Games companies are a bit notorious for major “death marches”, where people do roud-the-clock work to meet some kind of deadline.
I work remotely (not exclusively with Python), but this is all still a bit of a spread. Some companies have stayed fully remote, or “encourage but don’t mandate” going into the office, others have an X days a week policy, and some are going back to full-time office work. More opportunity if you are flexible but work for all preferences there.
I work with .net but everyone I know starts early at 8am if possible so finishes at 4pm
We have fairly flexible working hours, so I choose to start and finish early. I’m logged off by 4:30 most days.