I've set up my regular subscription. ๐ This was an important step towards the future sustainability of the platform, so I'm glad to see it happen. Thanks very much, @[email protected] and @[email protected] for your continued dedication.
I can imagine them carrying on making consoles this generation but long-term Microsoft is a services company and over successive generations they have failed to recapture the lead from Sony since the 360. Ultimately, they just want to make more money and struggling in the hardware business is not an exciting place for them to be in.
I say this as a Series S owner: the writing is on the wall. I will likely not be purchasing another Microsoft console after this, though I'm not sure they'd be interested in releasing one. I want to buy and own games I can play locally on a piece of hardware, which probably means I have to return to Sony or go back to the humble PC. For anyone currently on the fence seeing this news, I don't know why they'd consider buying into the Xbox platform and tying in all their gaming purchases.
A lot of it has reinforced my understanding around distributed databases and transactions. In my day-to-day, I've not really had need to use this knowledge as pretty much all our data stores are hosted in cloud platforms and we're operating on low datasets and traffic.
I hate the Tory party. I want Labour to get in.
Apart from this 28 billion pound investment, I cannot name one thing they actually stand for going into the election. This is a problem.
I've been reading Designing Data-Intensive Applications and it really is a great book, specifically for backend engineers.
Ah, I see, cut income tax just before a general election despite having literally years to do so prior, just so Labour will be forced to find extra income elsewhere or revert the tax cut in some form when they get in power. Cynical as usual.
I know it's vastly underpowered compared to even the Xbox Series S but I still think there's something magical about the way you can have these fully fledged gaming experiences in front of your TV or in your hands while on holiday using the same hardware. Of all the consoles I've owned, it's probably my favourite.
As a bit of low-hanging fruit, you may be able to reduce the length of the diffs in an MR by marking generated files with -diff
in a .gitattributes
file. This is at least supported by GitLab (not sure about others): https://git-scm.com/docs/gitattributes#_marking_files_as_binary
To be honest, it doesn't seem that bad. With clean architecture, you are going to end up with extra types and mappers. I would argue that what you have isn't coupled, because a change in one place doesn't have unexpected side effects elsewhere.
I haven't used Goa or Gorm. Writing SQL by hand gets old quick so I get why you'd use Gorm - just less code to write in the end. I've used sqlc as it's more a library than a framework, and it's fine, but it can't fulfill every use case. Goa looks too opinionated for me, on the face of it.
I've used wire. It takes some understanding but it's definitely a lot to understand just to add a dependency. At work we've got our own template for doing dependency injection and although I was skeptical at first it strikes a really good balance between being understandable and abstracting away DI. If this is your pain point, I'd consider going back to basics and get rid of the framework.
If you decide to go with a framework like Laravel, Rails or Next.js and build everything around the framework, you will deliver quickly at first, but you won't have type safety and it particular point it will stop scaling because these frameworks have no consideration for clean architecture. You won't necessarily be better off.
I feel Lucy's stories must end up mostly on the cutting room floor
If the outtakes are anything to go by, they do.
Forgive my crudeness, but she can go and get fucked, was my first thought.
Ngl, I honestly thought this was a bit of satire.