Microservice from the start may be a lot of overhead, but it should at least be made with that scalability in mind. In practice to me, that just means simple things like make sure you can configure it via environment vars, run it out of docker compose or something because you need to be able install it on all your dev systems and your prod server. That basic setup will let you scale if/when you need to, and doesn’t add anything extra when planned from the start.
Allocating infrastructure on a cloud service with auto scaling is the hard part imo. But making the app support the environment from the start isn’t as hard.
Skilled in asking a chatbot how to job.
as soon as you pay for 12 consecutive months, you will receive this perpetual fallback license providing you with access to the exact product version for when your 12 consecutive months subscription started.
So at most your software will be 1 year old.
AWS has so much documentation, and yet it never has what I’m looking for ☠️
You’re right, I’m not representing the merge correctly. I was thinking of having multiple merges because for a long running patch branch you might merge main into the patch branch several times before merging the patch branch into main.
I’m so used to rebasing I forgot there’s tools that correctly show all the branching and merges and things.
Idk, I just like rebase’s behavior over merge.
I like flutter’s design where you do your markup and styling as code, and then it gets rendered via opengl. So you get that native performance without having to deal with the whole browser stack.
I don’t like how almost all software these days is just web apps masquerading as native apps, but they’re just so damn easy to write compared to anything else.
It probably won’t get rid of js’s dominance, but it’ll give people options. I already see some front end python and rust frameworks thanks to wasm. But for some reason I really don’t like the idea of writing html / css in my rust. But I don’t like the idea of html / css in my rust.
I feel the opposite, but for similar logic? Merge is the one that is cluttered up with other merges.
With rebase you get A->B->C for the main branch, and D->E->F for the patch branch, and when submitting to main you get a nice A->B->C->D->E->F and you can find your faulty commit in the D->E->F section.
For merge you end up with this nonsense of mixed commits and merge commits like A->D->B->B’->E->F->C->C’ where the ones with the apostrophe are merge commits. And worse, in a git lot there is no clear “D E F” so you don’t actually know if A, D or B came from the feature branch, you just know a branch was merged at commit B’. You’d have to try to demangle it by looking at authors and dates.
The final code ought to look the same, but now if you’re debugging you can’t separate the feature patch from the main path code to see which part was at fault. I always rebase because it’s equivalent to checking out the latest changes and re-branching so I’m never behind and the patch is always a unique set of commits.
I think the only thing that should be in the dependency array of the useEffect is jsonParams.
I’ve only ever used hooks with no dependencies to effectively “run once” so I don’t know how to make them fire conditionally, but you definitely don’t want the state variables in there.
This is what I thought at first too. But after thinking about it more, it kind of falls into cybercrime. I can imagine hearing something like this on darknet diaries.
This is just the plot of office space
Dang good catch on the second user, I wouldn’t have noticed since I usually don’t look at people’s profiles.
It’s kind of funny that reddit will become this chamber of advertisers making posts and fake users “engaging” while the real people all migrate to lemmy.
Does the bill also include at least a 1.25x minimum wage increase to enforce this as well?
That sounds nice, I’ll try that out
Dang, the shared grocery list and meal planning was the best part of it.
Epitome was one of mine too. Also inventory, i thought emphasis was on the vent syllable not the in syllable
I also quit whisk when it became samsung food. Does CopyMeThat let you have shared lists with other people?
Here I’ll add some context
It is pretty easy not to think about this game, it does not live rent free in my brain. I bought the promise of a space ship over a decade ago when there really was no game. The “game” then was here is your spaceship in a garage, stare at it and marvel. That was the whole game.
Over time i’ve seen bits and pieces of it in my feed, I remember when they added being able to fly the spaceship, idk when that was, but again that was the whole game. You could see pretty space but still no substance.
That was really my last experience with it because I think somewhere around this point is probably where I started working full time and stopped really following game news.
Flash forward to today I see this post to see the game is still a work in progress, I shared my opinion.
So if there is a decent game by now with a plot that would be great, I would give it a shot. But if it’s still just a fancy tech demo where you can run around for a bit but there’s really nothing to “do” then I’ll wait another decade.
The point of the supreme court is to make a ruling on cases that already went through the lower courts. So it seems weird to make an official opinion saying it’s for the lower courts to decide instead of just letting the lower court decide by not making an opinion at all.