I keep forgetting to design for the failure path, so my product is an accurate depiction of society, where everybody has a convenient excuse to not handle issues and the slightest problem ends up collapsing everything.

My two main grudges against Typescript:
1) Union types can't be passed as arguments if there is a variant for every element of the union
2) No tuple polymorphism, i.e. [T, U] isn't assignable to [T]. This is not a mistake because the length of the arrays differs and therefore they may be interpreted in a different way, but IMO there should be a tuple type which is actually an array but length is unavailable and it supports polymorphism. This sounds stupid, but since function parameter lists work well with tuples it would actually enable a lot of functional tricks that are currently inaccessible.

Any non-tech hobby usually helps my coding, because relaxing breaks are far more efficient if I'm not just laying in a bean bag trying not to think about work but rather engaged in something unrelated. During the summer I was storing a really good electric guitar because the owner emigrated, so when I felt stuck I played some music. I used to play the cello in middle school but I was never really good at it nor did I care to practice properly because it felt a lot like yet another class to attend. Apparently music practice works whether you do it in one long or several short rounds as long as the total time is enough.

What's with people displaying their pronouns in SM but failing to put their family name in all caps? I'm glad you're so progressive, but as a person with an Indian name in London, have you considered enabling English people in talking to you first?

Anyone know why calling the "memo" function on a React component or using the "useMemo" hook is widely accepted to be called "memoization", when the name itself derives from an existing English verb which actually means what the function does? Why are we artificially creating jargon?

Does it make sense to buy a Nintendo Switch second hand? What should I look for, besides that the console is clean and the screen has no burn-ins or dead spots?

[!dev]

Sometimes I feel an overwhelming lack of willpower that prevents me from moving except for my eyes. It passes within a minute and leaves a temporary tiredness. I didn't really think about it until now and I have no idea why, but yesterday it happened while a friend was talking about something they're passionate about and I realised that this is very far from normal. Have you experienced something like this?

Whenever I see an ORM that supports creating and transforming objects in bulk, I can't help but think about the poor misdirected users who forced it to do that. It's an Object-Relational Mapper. It maps objects. The whole concept isn't designed for bulk operations, the point is that you add logic to each and every record and convert your operations to SQL so that you never have to keep a lot of them in memory.

So you know how a polite request may be phrased as a question, eg. "May I have seconds?". And how an appropriate answer for such a question may be a simple request, indicating the answerer's desire for the inquirer to be at ease, eg. "please do."?

So today my non-native ass had the following exchange:
her: "I'd love to keep you company but I have to call a friend who asked me dearly to call him back when I get home."
me: "please leave"

This was originally a reply to a rant about the excessive complexity of webdev.

The complexity in webdev is mostly necessary to deal with Javascript and the browser APIs, coupled with the general difficulty of the task at hand, namely to let the user interact with amounts of data far beyond network capacity. The solution isn't to reject progress but to pick your libraries wisely and manage your complexity with tools like type safe languages, unit tests and good architecture.

When webdev was simple, it was normal to have the user redownload the whole page everytime you wanted to change something. It was also normal to have the server query the database everytime a new user requested the same page even though nothing could have changed. It was an inefficient sloppy mess that only passed because we had nothing better and because most webpages were built by amateurs.

Today webpages are built like actual programs, with executables downloaded from a static file server and variable data obtained through an API that's preferably stateless by design and has a clever stateful cache. Client side caches are programmable and invalidations can be delivered through any of three widely supported server-client message protocols. It's not to look smart, it's engineering. Although 5G gets a lot of media coverage, most mobile traffic still flows through slow and expensive connections to devices with tiny batteries, and the only reason our ever increasing traffic doesn't break everything is the insanely sophisticated infrastructure we designed to make things as efficient as humanly possible.

I do not have the capacity to look for a job. I hate trial-and-error, I can't lie and I suck at talking to people in all but a cooperative context. I'm a decent webdev and I'm willing to learn, but to be able to do it I need skills that I don't have and I wouldn't need.

Why the fuck does Arch ship with NTP installed but disabled by default? I know it's a DIY OS, but this is just plain inconvenient with no perceivable gain.

You ever realize how small a newborn is? It's amazing how tiny humans can be. They're not even a full breakfast.

I got my very first PR to a repo of mine. Naturally, I got out of bed at 4am to test and publish it.

Anyone can become a designer, some just face a longer journey than others.
Like people who set a monospace font and then specify section margins that aren't an integer number of characters.

So today I learned how tree shaking works and I was just about to publish patches to my NPM modules when the registry gave up.

I just wrote 80+ lines of tests for a 30 line module and I was really mad at myself for wasting my time like that, until I remembered that while writing those tests I did actually catch several really tricky bugs and it didn't even take that long.

I wanna go back to the age where a C program was considered secure and isolated based on its system interface rathe than its speed. I want a future where safety does not imply inefficiency. I hate spectre and I hate that an abstraction as simple and robust as assembly is so leaky that just by exposing it you've pretty much forfeited all your secrets.
And I especially hate that we chose to solve this by locking down everything rather than inventing an abstraction that's a similarly good compile target but better represents CPUs and therefore does not leak.

I was passed someone else's homework which included describing what certain Bash commands do. I've a fair bit of experience and I can't imagine why this one would be useful, can you think of any use for it?

(find -type d) | grep public | tr './p' ' '

I finally figured out how to get myself to take regular breaks

To the bright engineer who considered it a good idea to open Zoom's toast popups in their own windows without tagging them appropriately as frameless short-lived managed popups:

Ride a hedgehog to work, you lazy fuck.

Viruses are quine programs written for cells.

A word of advice:
If you integrate email verification very tightly in the registration flow, it will be a world of pain to implement changing the email address.
It's alright, I didn't want to do anything this afternoon anyway.

What's the minimal feature set that can make a language as ornamented as JS into a comfortable REPL?
Should I write a full parser or should I try to patch my way around with regex?
It will have to interface a lot with JS so it has to be able to manage JS datastructures in some fashion, which means that I can't just make a whole new command line with its own programs.

My current plan:
Some delimiter (probably a semicolon) will take the output of a command and inject it in the next in case you decide halfway through a line to do some more processing, It also awaits promises and does some other nice stuff to make controlling such pipelines easy. I have an elaborate system in mind to decide where a value must be injected to make the line valid so in most cases you don't even have to indicate it. JS has beautifully simple syntax rules so I have a lot of technical balance to burn before I start building technical debt.

I have some ideas for automatic parentheses and commas in function calls. I realize while using a command line you do not want to tap shift often. My main idea here is that two names or values in js are always joined by an operator so the first missing operator is a call and following missing operators are commas until the end of line. This has lots of nasty edge cases though, like that no argument expression can begin with a unary operator or a bracket of any shape. You can always prepend a comma but it's cognitive load.

Anyway, do you have any suggestion or warning besides "js bad" which I know but it's the most popular sandboxable language and has a massive existing set of libraries which I kinda need.

Can we take a moment to recognize how absolutely retarded JS' event system is?
Events aren't objects. No, they're managed by an object, and identified by a string.
To subscribe to an event, you call object.addEventListener(name, callback). Because for some reason we can't just have an event object. Events MUST have an owner.
But to unsubscribe you don't call the function addEventListener returned, you don't use the token it returned either. No, you pass the same function to removeEventListener.
Because we don't use serializable tokens like in PP, and we don't return functions like in FP, no, we use functions as tokens, realising idiomatic DFP.

Redux is weird, and I don't like it because it violates the most basic principles of responsibility. The concept of expressing state changes as reducers is nice because it can be duplicated, saved and restored and compared for equality. So is creating isolated accessors and selectors. However, I really don't think a reducer should be aware of its own position in the hierarchy. When specifying an action you aren't addressing a reducer, you're addressing the tree. That the tree doesn't manage this addressing and expects reducers to identify themselves is a bit strange, especially considering that the whole point of having a tree is that reducers shouldn't be affected by their position in that tree because they're pure. Same goes for selectors, they should belong to the tree, not to any particular sub-reducer. Separating the slices is reasonable structure, but if you specify parts of the addressing in the slice and parts of it in the root you might as well just use separate reducers for each of your slices. It's functionally equivalent.

The primary concept of reactive programming is great. The idea that things just naturally re-run when anything they rely on is changed is amazing. Really, I think it's the next step in programming language development and within a decade or two at least one of the top 5 programming languages will be built entirely on this principle.
BUT
Expecting every dependency to be used unconditionally is stupid. Code that checks everything it might need all the time even if a decision can be made from much less information is simply bad, inefficient code. If you want to build a list of dependencies automatically, you have to parse the source.
And I really hate that there are TONS of languages that either make the AST readable at runtime or ship with a very powerful preprocessor that could be used to analyse expressions and build dependency lists, but by its sheer popularity the language we're trying to knead into something it was never and still isn't meant to be is JavaScript.

So, I turned on my old phone to transfer all my p̶o̶r̶n̶ photos, and it crashed from the notifications.

And I understand that it's an underpowered device and notifications aren't expected to come by the hundreds, but how terribly misdesigned must a pubsub system like Push be for the client to crash?

A word of advice to any new Arch user: don't use lxdm for your display manager. It's utter shit. The package hijacks the symlink of any other DM when you install it, and it refocuses the DM on a 5 second loop while it's running, making it a pain in the ass to use a VT. LightDM was broken temporarily so I had to install it, but frankly, I don't ever want to touch thiis piece of software again.

I'd like to learn about functional programming. What books, courses, tutorials or articles would you suggest? I have a good understanding of abstract algebra and I felt the need to learn it because my Typescript is a mess and I visibly don't know what I'm doing.