ScampiLover

@ScampiLover@lemmy.world
0 Post – 7 Comments
Joined 12 months ago

I like to shoot for the middle ground: skim for key functions and check those, run code locally to see if it does roughly what I think it should do and if it does merge it into dev and see what breaks.

Small PRs get nitpicked to death since they're almost certainly around more important code

We had a zoom call with a very well reviewed, recommended broker local to us. Next day I get a spam call pretending to be the bank we talked about the most as a lender, but that we currently have no business with. My paranoia has been at 100% ever since

It's not stateless end-to-end, it just means the client needs to keep track and pass the state rather than drivers or hardware

I'm not 100% on the motivation but from an architectural standpoint it does make sense - your software can now do many new and weird things without a hardware change

One example I saw was allowing an arbitrary number of streams to be processed simultaneously, just passing the different context state for each stream

I may be dumb about this stuff but what is an SPF? How does vit c boost it?

People look down on Javascript (and therefore Typescript) but as someone who learned by doing I think its a really good option

Once you get past the hello world phase you can take it any direction you want: websites/apps, command-line stuff, desktop apps you name it. Just avoid the trap of getting sucked into specific frameworks or loads of tooling early on and learn the language

W3schools is a great resource and you can do the examples and exercises right there in your browser

I love burgers, I hate mayo. This has caused me more pain than most would understand

Only game I've ever come back to this much. Unlocked everything, still fire it up every so often to have a run or two and it still somehow feels fresh each time