Well hello, friend. I'm going on six years sober thanks to /r/SD and it just occurred to me that maybe this place exists and needs some more friendly faces, so I'm going to crack open a bottle of rose lemonade and not drink with you all today
I will gladly take one for the team and sell him a Lemmy for a few billion.
I don't. I often work a few hours at weekends, but the pattern is different. I'll tinker for 10 minutes then go do some laundry or play with my son or go for a walk, then tinker again when I'm next passing by. I'm actually pretty productive most weekends despite not spending much time at a computer which makes me wonder if I'm doing it wrong during the week.
If you're genuinely enjoying the work, there's no harm in doing it. Just be sure that you're not using work as a way to avoid other commitments, or letting down your loved ones because you're not present.
It's really good! It does all the things I'd build for myself if I had a few months spare. Only quibble I have is that it can take a while for instances to scale up. I've done a bunch of optimisation on builds so now I get run times under 2 minutes, but wait times around 5 minutes.
I've set up idle runners so we keep a couple of instances warm during work hours, but it's still annoying.
Write down on a bit of paper "I want to spend more time with my son, I can always find another job", then flip it over and write "I'm going to spend my time on work, I can always have another kid" and see how you feel.
Discovered at age 12 that I was actually fast as fuck over short distances and won a 200 metre race, leaving the sporty popular kids in my nerdy dust.
My teacher said "you'd have been a lot faster if you hadn't kept looking behind you"
The Practical Architecture Process is probably the best distillation I've read.
Alongside that there's the classics, Enterprise Integration Patterns, a DDD book of your choosing, Newman's Microservices.
I'm a big fan of ReST In Practice, though nobody cares about ReST any more, and Simon Brownwork is great, particularly the C4 model.
Mostly, unfortunately, you have to learn by doing. Design a thing, document your assumptions and constraints, and see if the design still makes sense 5 years later.
Welcome aboard!
The time I spent on platform teams absolutely made me a better architect. "Operational concerns" take on a whole new meaningat 2am when you're trying to restore service on a component with no docs and bad logs.
Sup, Joe!
Can you briefly define quantitative software architecture? I have an inkling of what you mean but it's a new term to me
My ZenFone 8 died this morning and I'm heartbroken.
It's just a website, but for computers. Instead of returning HTML, that your browser can render, it returns structured data that's easier to read with a computer program, like a 3rd party app or a bot.
You could just fetch the website and pull information from that, but HTML is awkward to read, and has a lot of data for display purposes that you don't need for other use cases .
People will find it if they need to. I hope that r/SD continues to function tbh, it's a great community. If it doesn't, we'll be here waiting for the 5th of July regretters.