HN user

aequitas

3,657 karma

[ my public key: https://keybase.io/aequitas; my proof: https://keybase.io/aequitas/sigs/2znKsVxtw5qBmOCB8twAzeao8NVyBFLmwuT_05h1jsw ]

Posts12
Comments1,000
View on HN
Half-Baked Product 20 days ago

What you really want is 2 dishwashers! That way you never have to unload the dishwasher because you alternate your dishes between the two. The one that has just completed the cleaning cycle has now become a cupboard with the clean dishes and the other one becomes the dirty dish storage and vice versa.

SecurityBaseline.eu 2 months ago

Today we launch SecurityBaseline: monitoring 67.000 governments and 200.000 sites.

Headlines: 3.000 governmental sites use tracking cookies illegally, over 1.000 database management interfaces are publicly reachable, 99% of governmental email is poorly encrypted.

Yeah but, even ones that don't use literal tab characters use the tab key to write code, right? RIGHT? Like, does he hit space N times?

Now that I think about it, I think I haven't hit the tab key for indenting code in ages. I use cmd+] and cmd+[ to indent/unindent blocks of code in my default editor and doing so habitual for single lines now as well that I have 'unlearned' the tab key. For the few occasions I'm in a editor that does not have this keybinding I am actually hitting spacebar a few times as it is more predictable than whatever amount of spaces using the tab key would give me (or if it gives me a tab instead of spaces) and me having to dance around with the backspace key as well. Some editors I think use tab/shift-tab to indent/unindent blocks/lines of code, but not insert a tab. But then you are having 2 modes for the same key depending on the context.

At least the setting does work in reducing the switching when you cmd-tab to an application with no open windows in the current space. But I think some of this annoying switching behaviour is application specific logic and they just didn't get it right with Safari, some other applications do get it right though.

Wonderful, that leaves 2 things on the top of my list for spaces: having to hover your mouse over the top left corner of a space and waiting until it shows the closing icon. And Safari deciding its better to switch to a space and open a window that was minimised there instead of just opening a new window in the space i'm currently in (even with the "switch to a space" setting turned off!) when 1 want to open a new tab.

If you are using it to write code, you really care about correctness and can see when it is wrong.

I heavily doubt that. A lot of people only care if it works. Just push out features and finish tickets as fast as possible. The LLM generates a lot of code so it must be correct, right? In the meantime only the happy path is verified, but all the ways things can go wrong are ignored or muffled away in lots of complexity that just makes the code look impressive but doesn’t really add anything in terms of structure, architecture or understanding of the domain problem. Tests are generated but often mock the important parts the do need the testing. Typing issues are just casted away without thinking about why there might be a type error. It’s all short term gain but long term pain.

>Next, Apple does not respect the multiple desktop boundary... This is a configurable setting.

If you mean the "When switching to an application, switch to a Space with open windows for the application" settings, this works only partially. When clicking the dock icon its behaviour depends on if there are windows in your current Space (virtual desktop) or not. And don't get me started on where macOS decides new windows should go.

Reminds me of that time I was taking climbing lessons in the Belgian Ardennes. Helmet on, in harness, hanging in the ropes, holding tight to not fall, we where climbing half way up the mountain, when a person out of nowhere ask if he can pass and just flew up the key section of the route. It was just a local, casual clothes, no harness, no helmet, no rope, maybe not even proper climbing shoes but I can't recall that. Just casually climbing the mountain like he was on a lunch stroll. Even now with years of experience I still don't have that confidence.

I consider myself a little techy, since I visit this site quite often. But for me YouTube is curing me from my addiction to it by ramping up its ad blocker blockers. I know I have to wait roughly the ad’s runtime looking at a frozen video before the video actually starts playing and it is often enough to let me go do something productive or useful instead. Thanks google :)

It’s very simple: format code to a standard. Preferably the language default formatting. But it must be a standard that can be auto formatted to with a tool. Now when someone doesn’t like that standard, they can auto format from that standard to one of their liking for local development and back again to the project standard for pushing to the project. This can even be done automatically with gitattributes during checkout and commit. But without strictly enforcing a autoformatable standard this is not possible and you end up with bikeshedding.

But there is only so much room for muscle memory or context to switch between. I tried Helix for a while, got used to it and I really liked it, especially the noun verb order being different from vim. Seeing what you have selected before performing the action. But for me the problem is that vim is everywhere I go or will eventually end up. All my servers have vim. Every server I need to randomly debug has vim or vi. So my muscle memory for vim keeps getting refreshed as well. And switching between the two constantly is just a pain. I could take along Helix to all these servers. But that is not practical nor do I need all the features Helix uses. Or I would miss specific feature which I then also have to bring along.

Now I’ve settled with Zed as desktop editor/IDE and still use vim on remotes. The context switch between a desktop app en cli is big enough that it’s never a problem. I don’t even use the vim bindings in Zed.

I use Nix exactly because it doesn't allow installing things at runtime. This keeps me from hitting surprises where the runtime environment changes from under me. Containers can partially solve this problem as well but have their own usability issues.

Nowadays I start every project with `nix flake init --template templates#utils-generic`. And put everything in that related to the project. I even had some projects where I had to put 'ssh' as a pinned package as it was used in some scripting and the default macOS and Linux versions accepted different flags.

I also do love that I can do something like `nix run nixpkgs#nmap` on any machine I'm on to instantly run a program with worrying where to get it from. I also use this feature in some of our projects so you can click a link in the admin web interface which is a 'command url' for iTerm2[0] like: `nix run gitlab.com/example/example/v1.0 -- test http://example.com` which will prompt to run that specific version of the command in your terminal, without have to checkout the source repo. In this case it is to rerun specific task locally for debugging purposes.

[0] https://iterm2.com/documentation-command-selection.html

I find it very easy to avoid the AI feature in every day Zed usage. Sometimes they do come in handy though. But nog often.

I have to try out the debugger yet. However I share your sentiment but for the Git feature. The basics are there but it is just not complete yet to fully replace my current git workflow. Hope they keep focus on that as well.

I have a mid 2015 Macbook Pro 15", also with OpenCore. Running just fine. No issues with Safari and Cloudflake. Only thing is the battery was mostly dead. I replaced it with a iFixit diy battery kit, but that one died completely after just 2 years (out of warranty of course). Probably the controller board, as the cells were nowhere near empty. Now I have the choice to replace it with a cheap battery from unknown source or yet another iFixit one which costs almost the price of this laptop second hand. But I have lost trust in this iFixit product as others seem to have the same problem. Just sucks to have perfectly fine hardware locked behind another expensive battery repair.

  yes &
A few times is still my favorite way to push a cpu to max temperature for testing. Used it a lot to detect faulty Core 2 Duo MacBook back in the day. They would short circuit some CPU sensor due to thermal expansion or melting of the wire insulation. Yes was an easy way to get the CPU’s hot enough.