wry_discontent

imo it's best practice to not use light/dark themes. The site looks the way I want it to look. This isn't your site, it's mine.

You can do some of it with Karabiner Elements and/or Kanata, but I don't think it's quite as good. I couldn't get the timing working as well with those so the layers were more trouble than they were worth.

Nice! I have a very similar tool I built just for myself to use for CR at work.

I'll have to install this and check it out

I don't buy this. You can be a poor listener. I am for sure.

Listening is definitely some kind of skill.

The only ergo keyboard I've ever enjoyed is the ZSA Voyager.

I tried the Kinesis, the Ergodox, and the Moonlander, but something about them didn't quite suit me. I think they all had similarly oversized thumb clusters, which I found very uncomfortable.

My current setup is the Voyager with homerow mods, which is super comfortable and I manage to mostly avoid typos.

edit: I should also say I'm an avid Emacs user.

Think of others and write more. Going into new stuff is hard, and if there's docs written down, that helps keep everybody working.

Write more in your PRs, write more in notion, write more in Google Docs; just write more. If things are unclear at your company, take it upon yourself to start writing and add documentation. If you come across a weakly filled out Jira ticket you know something about, write about it. If you know code conventions that aren't linter enforce, write them down.

I vibe coded an Emacs package recently. I've used Emacs for years, but never done any nontrivial elisp. Couple functions here and there, and advice to modify behaviors.

It worked pretty well, but there are pretty obvious shortcomings. The code isn't very good. It has some odd design choices. But overall, it works.

I know enough elisp to modify the existing package, so I'm using the LLM less and less as time goes on (which is where I've found they mostly start to suck), but I didn't know enough to get started, so I'm happy about the outcome.

We had a nontechnical person choose Next, against my recommendation but I didn't have the authority to override that choice, and it's been a total nightmare.

It's extremely messy. Hostile to debugging. Hostile to testing. Bad HMR. All this to offer us RPC and filesystem based routing (neither of which I even want in a framework).

Fool me once, shame..shame on..you. Fool me twice.......a fooled me can't get fooled again.

Using Next.js is malpractice. I've never had a worse experience with a web framework (and I'm using that word extremely loosely here).

I end up working with a lot of data transform pipelines, and Clojure's strong support for names (with namespaced keywords) and generic data structure manipulation makes the code you have to write more succinct.

This kind of task is also extremely well suited to a repl. You define a temporary var, and start threading it through a series of super small functions that only slightly change the data until you get what you want.

    (->> my-data 
         parse
         (filter some-pred)
         (map my-mapper)) ;; and so on, if you need more
        

For me, the big thing is REPL driven development, and immutable data structures. Everything can be inspected. It's easy to get insight into basically any small piece of the program as if you were using a debugger (but you don't have to).

In the circles I see, Java isn't popular because it's verbose and boring to use.

These days I don't see those as significant issues, tbh.

I would prefer a Clojure program, but I'll take Java over Typescript at this point.

> gosh, this would be so much simpler to solve in Clojure

My colleagues are so sick of hearing this.

I use Clojure a lot at home and Typescript at work. The experience is dramatically different. Clojure makes me feel free. It feels easy to experiment and the whole world feels open to me.

Typescript on the other hand feels like being confined to a small room. There's not much flexibility. Not much is open to me. It's very regimented and I can sense better solutions, but they're off limits to me either because of the required type gymnastics or the language primitives.

Is the code formatting not working for anybody else?

I've struggled to read Deleuze in the past; do you have recommendations? I find summaries interesting, but the texts themselves impenetrable.

I don't know what that means. I haven't changed how I resolve conflicts with jj.

I switched from Magit to jujutsu. The only difference for me is that stacking PRs has become simpler. It's also made me more conscious of making smaller changes and shrinking what I consider "worth shipping".

Overall a positive experience, but if Magit is working for you, there's no killer feature that makes it worthwhile.

I'm also using https://github.com/bolivier/jj-mode.el which lets me do enough of what I need with jj from within Emacs.

They mention magit, which makes me think Emacs, but it looks like there's lot of custom UI stuff.

Also wholly disagree. I don't have a kid, but I am married, and nothing has helped me more. Best thing that ever happened to me.

Start doing any year of Advent of Code with Clojure and you'll get it.

They're really amenable to the REPL.

I like integrant, but I feel like a lot of the examples I see use it for each web endpoint, which seems like a massive amount of overkill to me. I tend to use it just for the router, but it sometimes feels like I'm not using the library to its full potential with that.

Do you have a date when that policy was instituted? I've known a lot of air traffic controllers, and most of them wore glasses.

The ruling class makes the rules, though. That's their whole deal. That's why nothing works right.

My dad was an air traffic controller until the mid 10's and this has been a problem easily since like 2005.

They struggled to recruit people who could do the job at all, and when people got into the building to be trained (after an initial training) most of them would quit because they couldn't do it.

Everything is difficult for newcomers to understand. Newcomers should be helped to learn new things. Every programming language will be incomprehensible to non-programmers. That's not the target audience.

Multiple reps publicly said TikTok needed to be banned because they couldn't control the narrative around Gaza as easily. TikTok is the only platform I regularly see content about Gaza fed from the algorithm.

The JS community has no sense of quality. The community doesn't value things that are well abstracted or work well. I dread every moment I have to work in JS because everything is so badly done.

Something I think about a lot is that people tend to compare whatever the most recent innovation was to humans.

It used to be that what made you alive was electricity; you could Frankenstein shock yourself back to life.

It used to be that you were a clock. Your gears wound up at birth, and then eventually you wore out. You needed repairs.

People love to use metaphors, but none of these things are the full picture. Just because computers are so complex doesn't make you more correct. Your brain isn't the whole of your mind, we already know that's true. Why is this silly nonsense entertained?

I can't imagine having nice things to say about node after working in Rails. Rails does so much for you, provides a coherent picture of how things work. Node gives you nothing but the most irritating programming tools around