oxff

This is quite obviously about substantial influence on election news cycle; and of course pointing the finger at the other side is already contained in the friend-enemy distinction.

> It is not a big deal.

You would be literally fuming about how Fascists Are Hanging Democracy From The Rope if Biden and Trump was switched in this case. So would most "it is not a big deal it happened, but it would have been big deal if it didn't".

Friend-Enemy is all it is.

Obviously corruption.

To obviously debunk any and all FP autism coming at your way.

To give credit where credit is due, most of the time some application functionality being described through FP jargon gives a better spec of its behavior than the same through OOP jargon.

Enforce the Jeff Bezos AWS rules. Hire people based on how well they can read code Clear thinking, clear reading and clear writing are roughly the same thing / caused by same things eventually. You cannot have clear writing if you don't have clear thinking about the subject etc.

The compiler doesn't make assumptions that are incorrect (it is what it is, basically, if it assumes no integer overflows there better not be).

Your application, and the application programmer, instead fail to fulfill those compiler assumptions.

This is a good positive model of UB, fulfilling the compiler assumptions.

> On the other hand, there seem to be so many cases like this one where the “undefined behavior code deleter goes brrrrrr” really overextends its usefulness.

I would simply not depend on invoking UB as part of my program's behavior (?).

Borrow checking (lifetimes and references) are fairly easy for a beginner to Rust to grasp, I think it is basically a meme at this point that this stuff is hard. Entirely different thing if you are making some kind of async library though, that is when you will run into advanced gotchas.

Rather than a nice steep curve, its more like a threshold function.

The first two are the same problem so this is almost correct.

Unit Tests are a colossal waste of time 80% of the time, and at least 80% of that time should be spends in thinking how to make your system debuggable.

As a software engineer, docs are quite low in priority. You should be using a language that can do documentation, like Rust, Haskell or even TS if you must use JS.

If you are stuck with JavaScript you have to be careful since you might just make an API that is way more permissive than what you intended to do, or similarly if you are writing Java and need to consider what happens when concurrency happens etc.

I have an atomic note like ``Paxos`` and when I re-read or add to it, I usually refactor it to resemble my improved understanding.

This is a colossal waste of time if you do it by hand, but it is something that really helps me, and is enabled by taking notes on a keyboard + Obsidian.

What about the low doc, low meeting culture

The entire Windows 11 UX and UI feels like using someone's react bootcamp product, complete and utter ..

AWS, Rust std.

> Anything about Nix > fast

Massive doubt.jpeg, as all my previous attempts at understanding and using Nix have all been "trust me bro, THIS random github repo source code has the Current Best Practice (already outdated)" and various other random two article blogs on how great nix is.

damn guess i have my next few weekends nuked

I find it funny they got it added to Kernel when there is really no good documentation or experience with how the two different memory models will mix together? Maybe I'm missing something obvious.

Genuinely did not expect this to happen, a feature of not only software engineering, but management and organization too to make it happen.

lol at people saying no and writing a virtue signaling blog

Both Spacex and Tesla consistently rank as most desired workplaces for real engineers (as opposed to combucha drinking twitter employees w/e), fact is most of the readers here wouldn't even make it (me included)

This one should just be a type-check & compile time error with red squiggles all over the editor.

Go to a medium to small-sized company that's 5+ years old with PHP codebase.

Youtube wants to be much like Tiktok, barely any search capability, just a stream of ML generated OR recommended videos, anything else outside of a constant, continuous video stream generated based on your metadata and other PII is considered "overhead" by these cyborgs, search for relevant videos? overhead, sorting videos? overhead, let the algo do.

These changes also render the site nearly unusable if you have a triple digit iq.

p.s. Youtube's search, much like Gooogle's, is pure dog shit by the way. Neither of them fill the function of a search at this point, you'd have to remove SEO and ML optimizations from them to get them working again. I search for "X" in youtube, I get 2-3 videos vaguely related to it, and then like 50 "videos you watched", "videos others searching for X watched". It's so fucking bad its unreal, makes me think what kind of a brain dead adderall crack addict they have QA testing this there.

> I can't work on it for long amounts of time - every 15 minutes, I will either visit HN, Reddit, some game, or have to get up and physically leave the desk. I can't bring myself to work on things for extended periods of time.

This is not bad in itself. Do you actually PROGRESS in your work when you do this? If so, keep going on.

Mocking almost certainly is always the wrong thing to do. The maintenance burden alone from making sure the mock accuracy wrt. real implementation is high enough to guarantee high enough assurance should disqualify using them.

They also make the tests nearly unreadable and very hard to reason about IME.

And now only libgen and archive.org remain, sad

Where / how do you save a HN shitpost that is definitely not worthy to be part of the atomic note of `Kubernetes.md`, but is still relevant / insightful and related to it?

I would add it to either quotes.md or the daily note with #kubernetes tag.

The structure is there, it's just not in the file / folder layout, but in the wikilinks and whatever else Obsidian can uncover (ie. unlinked mentions, orphaned file output).

I guess I learned how my own learning and memorizing works, and managed to match it better with how Obsidian works, and now I don't have to think about silly file / folder structure anymore. Your experience maybe different.

I like what the error handling achieves, it is actually readable way to understand the divergent control flow paths (and probably majority of code is read more than written), but I do not enjoy writing the initial boilerplate, so that's good to hear.