itchynosedev's comments

A hidden cost of self-hosting.

I love self-hosting and run tons of services that I use daily. The thought of random hardware failures scares me, though. Troubleshooting hardware failure is hard and time consuming. Having spare minipcs is expensive. My NAS server failing would have the biggest impact, however.

I am not sure it's meant to be a negative thing. Obviously, a lot depends on the context here.

But, I've developed a dozen or so projects with Claude code. I am meant to be the only user.

I am maintaining a homelab setup (homelab production environment, really) with a few dozen services, combination of open source and my own - closed sourced - ones.

I had tons of ideas of how to set things up. It evolved naturally, so changing things was hard. Progress was quite slow.

Now, I have a pretty much ideal end-state - runs on auto-pilot, version bumps mostly managed by Renovate, ingress is properly isolated and secured (to the extent I am familiar of).

I was able to achieve things I wouldnt've otherwise in that time. I skipped parts I did not care about and let LLMs drive the changes under supervision. I spent more time on things I did care about, and was interested in learning.

Yeah, most of my LLM code is sitting closed source and that's by design.

I noticed some of my hybrid repositories were slow on regular git commands (eg log) and running garbage collection manual resolved it. Perhaps, jj created a lot of unreachable objects?

I really loved jujutsu for the few weeks that I used it. However, I did find all my tools that rely on Git (eg Gitlab CLI that can open merge request from the current branch) breaking because JJ operations result in detached head in Git.

In addition, mixing Git and JJ will result in your repos becoming really slow when you do need to run some Git operation.

Cline is a great alternative to Cursor if you are not willing to switch over to another (forked) editor.

However, it's baffling to me that by default Cline ignores `pkg/` folder that is common in Go projects. Check this issue - https://github.com/cline/cline/issues/927

I think Aider, Cline and Cursor are not far from each other in their capabilities.

Cursor was probably the most polished experience - especially their `Tab` autocomplete. However, I found this effect really interesting. Let's say 7 out of 10 times it's seamless, but there's uncanny valley of autocomplete in 3 out of 10 times - where you expect it to the right thing, but it either predicts wrong or takes a tad too long, 'breaking the immersion', if you will.

Cline does the job really well if you're in VSCode. Aider is great if you prefer terminal based workflow, or do not want to commit to another editor. Another great thing in Aider is `//AI!` comment. You can start Aider in --watch-files mode and it will watch for instructions, and start executing them. This way I can work in my preferred editor and have a tool in the background performing AI tasks.

A slight edge in my case goes to Aider for this reason, despite the fact that it does not feel quite as polished as the other two.

I use syncthing to sync from paperless data folder which runs on Kubernetes (k3s).

It's a one-way sync. Paperless is the authoritative location. The only reason I back up to Google drive is so that my phone has easy access to the documents I may need on the go.

Disclaimer: I don't have a horse in this race, and don't use Jetbrains products.

I read the dialog, and the contents is extremely clear - I can send the non-anonymized data to help improve the product, or not. It doesn't say this is a required action to use the plugin. Less is more. I prefer less text with the clear prompt to consent or not. I don't think this needs a fine print of pages long terms and conditions.

I ran over a 1000 searches as an early adopter last month and this is a welcome change. I also notice how often I search for the same thing over and over, or use product name searches using Kagi as a gateway. I think this shows how poor my learning comprehension / documenting habits are. Thanks for bumping up the limits, though.

I want to utilise lenses and optimise my search better. Any tips?

Never used disko, are there any gotchas? Will it format my drivers if I run nix rebuild?

You can also go to the specific line you pick from fzf search

nvim $(rg . --vimgrep | fzf | awk -F: '{print $1, "+" $2+0}')

On a scale where one extreme is buying a refractometer to optimize every last aspect of coffee making, and the other end is instant coffee from Lidl, there is a wide range in the middle.

V60, Aeropress (only one needed, but I like both for some variety), a decent hand grinder, and good beans is hardly that much money (amortized over years of use, or "cost per wear"), let alone maintenance.

I bought these around 10 years ago (well, v60 twice, I broke it, and I like it ceramic, and I have to buy beans every few weeks), and they are still going strong. The process takes about 5 minutes total time, including brewing. I would never replace it with an instant coffee, I would rather stop drinking coffee altogether.

It does make traveling a bit tricky, as I refuse to carry additional gear around, and don't always have access to good coffee places.

I have to admit, in the beginning, I was looking for the holy grail setup like with other hobbies, but luckily, was not wealthy enough to sink a ton of money into it.

I actually had a lot of fun playing Stadia games.

I think FPS and reaction type games are not it's strengths, but some third person action / adventure games have been super fun. Sometimes I forgot it was not running games locally. Impressive tech.

I went to see his live performance in Amsterdam a few years back. The show had been postponed due to back injury but it ended up happening a year later, and it was mesmerizing.

From what I understood the transition is of strategic nature. Less dependency on third party suppliers for vital components.

The performance and/or battery gains is almost incidental.

I love the experience of firing some adventure games on my Macbook, grabbing the controller and chilling on the sofa.

My xbox one x and a 4k screen in the office room, but I can't be bothered to sit in the chair and wait until everything boots to play for an hour on a Tuesday night.

The video artifacts can make the picture a bit muddy (esp. darker levels or games) but all in all, it runs smoothly, I can't notice any input lag that's longer than on my xbox.

Games start quickly, run smoothly, and there are some bangers that will take me months to exhaust, so I am not that worried about the library.

The issues start when someone in your house starts streaming HD videos, than stuttering begins. I have 100 mbit copper, I am pretty close to google data centers it seems, in Western Europe.

I bought Stadia controller and a few games. The controller feels great and pairs quickly. I mostly game either on my Windows PC through chrome (4k) or my macbook (1080).

I really love it!

It says it right there in the article.

> Apple’s chip-development group, led by Johny Srouji, decided to make the switch after Intel’s annual chip performance gains slowed. Apple engineers worried that sticking to Intel’s road map would delay or derail some future Macs, according to people familiar with the effort.

I think it's more coincidental than ironic.

I agree! You know what takes it to the next level? Sticky keys!

Accessibility feature in macos where modal / control keys will "stick" for the next keypress (non-modal / control) and then release.

Double tap will stick it for the duration until the next tap on the same key.

Essentialy, double tap control key and move around with n and p keys, kill with k, move more, yank somewhere else with y. All without touching control! But there's more, you can save the buffer with x followed by s press. It takes a while to get used to but saves you awkward wrist moves. I guess it's closer to modal editing in vi, just not as advanced.

I found that living with a native English speaker in the same house does teach you a lot of intricacies of the language - pronunciation and grammar. However, it's a deep territory of diminishing returns. In Europe, everyone's English is kind of bad (a lot of people are fluent, of course, but almost never above the level you want to reach), so there are not many people to appreciate your fluency. I found it to be more enriching to learn a new language instead, that gives massive appreciation of the languages you already know.

wrt point 2. I always assumed that it's not only chip performance or efficiency, but ecosystem and software compatibility that's a larger issue.

It's not trivial to port x86 software to ARM, or even run an energy efficient emulator.

Is that correct?