My experience of Arch is that it's fun as a home computer tinkering exercise but I don't trust it for my work computer since I can't resist a version number bump and the amount of time spent faffing around would be a nightmare.
In my experience microservices have been prescribed as a sales bullet point instead of a software architecture decision.
Every time it's resulted in insane low traffic bottlenecks all over the place as services chatter away or separately need to look at he same file data so all request a copy etc.
Any architecture has tradeoffs and it's poor form to pick one before you've even described what the software is for.
Very useful, I find that discovering domain knowledge can be a painful process when trying to build a relationship with a new client. Hopefully this will help
Thanks, I was just wondering since I don't really see the point in rewriting between dynamic languages. Aside from a few things being easier in each (async being an example) they're basically the same to me.
We did this for a project a few years ago and it was alright. In the end we decided against doing it again purely because the DOM became so extreme with one-rule classes that it became a nightmare to read the templates. So much noise.
For building things out and prototyping it was amazing though.
Vacation / Sick time is a bit different than needing to run errands till 10am, either shifting the working day round a bit or spreading the time out over the next days or week etc.
Doesn't hurt to check in when you're available again as a courtesy but the benefit is NOT having to get permission to do something like this up front.
If you're remote as an employee then presumably the company has process around holidays and stuff that would be followed. If you're a freelancer then part of what stops you, and your client, from being fined by HMRC (in Britain) is setting your own working hours and days.
I have been keeping one day a week for the manager's schedule- style calls and appointments.
The rest of the week is divided in to half-day blocks which from my own experience is the minimum useful time to switch context and complete or work on some task.
I'd never read this before but it sums up problems I've had in teams previously with scheduling and especially short-notice "quick" meetings that wreck an afternoon.
It also means there's sacred time in my calendar for unbillable stuff, which gives peace of mind rather than thinking "but I could be doing..."
I think about it often, but I assume it's some kind of burnout. None of my hobbies would translate into even my current pay level.
There's that nagging idea of the 'real programmer' who is getting paid big money to solve interesting problems. Almost certainly a myth but still a frustrating idea.
It was a relief when I didn't have to use a mac for work anymore.