analog_daddy

no profile record

comments

9 วันที่ผ่านมาdiscuss

Fair enough that I did not mention any timeline. And could’ve been general with “VCS”. And you are absolutely correct, that basics of some of these tools can be learnt in an afternoon.

In fact the industry i work in we don’t have git, but something similar to SVN (and proprietary, expensive and pathetic UI/UX)

Since, I am not in software industry, I won’t comment on whether such people might survive for more than 5 years without knowing about ‘VCS’.

However, I have slightly died inside when some Computer science students (graduate school, mind you) were using google drive with manually created timestamps as a backup strategy. The submission for this entire semester long actual project was on Github. as a final single commit uploaded a day before. (And no this wasn’t a squashed commit from a different repo.)

There might be a blurry line between people not sharpening their auxiliary tools vs never using or being slightly curious about them.

I am more of a glamour and bling on my tools person, and I don’t expect every engineer to derive the same pleasure that I derive just from tinkering with them; however, does make me wonder if there is a point when such an approach to not fully caring about simplifying your workflow (aka being lazy), might spill over into making poor engineering decision?

12 วันที่ผ่านมาdiscuss

Any experience with ‘programmers’ not knowing git?

12 วันที่ผ่านมาdiscuss

My first thought as well! Even glancing through their website I don’t see an FAQ section or even a section just answering what value addition it brings over pandoc?

21 วันที่ผ่านมาdiscuss

Not sure if this completely helps with the full setup aspect, however, I got introduced to secure enclave when i was researching a git app for iOS. The following app has, as one of its paid features that you can utilize secure enclave. Pretty cool app and pretty cool technology! https://workingcopy.app/

The setup was a breeze! Did not try it with a server yet, but i don’t think anything would be radically different.

21 วันที่ผ่านมาdiscuss

Really surprised that this is not the first thing everyone does on their repositories.

I am not a celebrity on github and not even agents bother with my repositories, however, even before the bot pull requests/issues, I always made sure to enable only the things I felt I would want to use and provide a way for someone to reach out in case I was expecting collaboration/feedback.

I realized that anyone can create a PR to upstream, when I accidentally did so using the github web UI on mobile. Felt embarrassed and immediately closed it. But, then it made sense that why people were frustrated with this sort of thing happening to big repositories.

21 วันที่ผ่านมาdiscuss

Locked behind a login screen. Maybe its for the best.

29 วันที่ผ่านมาdiscuss

Oh my god! I hate using anything that is not my keyboard anymore. Laptops are not ‘lap’tops for me since I will just be slow without my keyboard. The split keyboard with many thumb keys is tough to achieve on laptop.

30 วันที่ผ่านมาdiscuss

Small note: You need admin privileges only once for the first install which creates a new user `linuxbrew` and everything is based around `/home/linuxbrew` prefix. The issue is on systems where getting an admin access is not possible, you cannot ‘reliably’ install to a different prefix. It is currently unsupported.

Honestly, I would settle for a custom prefix if it tells me exactly what packages will break and what won’t without having to read each and every formula recipe. That’s one thing that bothered me for a while and I did not have the willpower to explore that direction without having community support.

30 วันที่ผ่านมาdiscuss

Yes. I daily drive pop os now. Hate to use flatpak for anything. Only install core packages, google chrome and vscode using apt. Almost everything else is installed using homebrew. The idea is have a base stable system for UI and basic shell. Usually get the latest packages from brew. Earlier same base system but had distrobox with arch toolbox. Planning on using this scheme going forward, especially since while I love rolling release, they sometimes might have regressions which I don’t want to deal with right away. And these regressions can be both at system level or user packages level. Having a stable base helps significantly in daily driving linux in real world.

30 วันที่ผ่านมาdiscuss

Yeah I tried nix about 8 months ago. Not really as simple as homebrew. Even the detereminate nix tutorial though nice felt too much of a hassle. I feel homebrew really is a nice interface which is pretty close to conventional package manager, while nix even though the concept is revolutionary, felt lacking in user experience. Hope the documentation improves.

เดือนที่แล้วdiscuss

No, it is an advantage.

I am not a rust evangelist, I am not a rust programmer or programmer at all; however while evaluating tools to use, anything written in Rust and Go at-least gets me to look at the project in more detail, since they most likely are able to ship statically linked binaries, which has been one of the key criteria for my personal evaluation of tools to select and use.

So, you might not consider it as a valid signal, however it might be for other users. Even if it has a negative connotation for you. Which in itself, again might be a good filter in case you don’t want to use it.

เดือนที่แล้วdiscuss

Just curious, any reason to prefer using age (you mentioned that you would prefer it if starting over), over something like keepass? I am currently using keepass-cli and only reason i did not use age even though i found it was that it was new to me and I never heard of it (probably not the best reason, but in this era might be a reasonable thing to stick to devil you know). So curious about your take on this.

เดือนที่แล้วdiscuss

Okay. Here is a pattern i follow everywhere in my init files for almost every program. Define two key env vars. $DOTFILES and $ECORP. The first is path to your personal set of dotfiles. The second is path to your corporate specific dotfiles.

On personal pc no need to define the $ECORP var in shell init. On work pc define that var.

based alone on that you can conditionally do almost anything.

- shell source files/aliases

- vim/editors enable disable plugins based on existence of env vars.

- define shortcuts in file manager.

- and i add the following to my main $DOTFILES .gitignore.

  # Any file that contains the following will be ignored.
  # Used to ignore files in corporate environment
  *ECORP*
  *ecorp*

Based on multiple years across different setups, using environment variables was the most reliable option since I have been in places where there are restrictions on where my init files can be placed and having to change a shit ton of paths in my dotfiles or just keeping a different branch for work and personal (and making sure they stay in sync) was too much of a hassle.

Additionally, maintaining hygiene is essential, where I only use a Read Only PAT token on my personal dotfiles in workenv. That way, there is no accidental way I would be able to push from my workenv.

เดือนที่แล้วdiscuss

Glad to run into this after some time!

I guess we are welcoming the software people to the world of expensive tools. Just sad that the FOSS alternatives of these tools are not as powerful whereas software industry still has FOSS tools to fall back on.

2 เดือนที่ผ่านมาdiscuss

Haha. I spent a significant amount of time getting vim keybinds everywhere, and eventually had to make exceptions for certain software. But, I had my share of making exceptions I guess and got frustrated when I couldn’t map Win+L in Windows to anything and I decided to solve it once and for all. Got a QMK programmable keyboard and now I use hjkl everywhere I would use arrow keys. Did it save me time? No. After 8 months of usage on split keyboard I am back at my original speed and don’t need a cheatsheet for my symbols layer, but it made me less frustrated and feel more free. I don’t need a AHk script or key remapping and their restrictions, this is wayy easieer especially with live VIA configurator.

2 เดือนที่ผ่านมาdiscuss

Yeah same here. Isn’t it weird, thet i used to be a lot more excited about space travel however, as I grow older I am excited about things more closer to me. Still curious, but focus has shifted from great for humanity to will make my life easier. Just feels more closer and impactful (to me).

2 เดือนที่ผ่านมาdiscuss

Not frequently, however in experimental phase where you need to debug if any specific combination of patch is causing issues, it helps a lot. For instance, I had issues with my delete key not working even with delkey patch and then after trying to enable patches incrementally I zeroed in on the fixkeyboardinput patch. Sure I can do this in a VCS flow but, it feels magical what a bunch of ifdef’s simplify the process to. And I feel it is still suckless philosophy since the code still compiles to exactly what you need.

Additionally, it helps lower the barrier to entry for a lot of people, who would have shied away from the manual patching flow. You’d be surprised how often i have seen people squint with default xterm on our servers, not knowing how to configure it and messing around with xrdb. (Which takes a while to propagate across LSF clusters). With flexipatch it feels easier to introduce it to them since I just say run make after any config changes to apply the setting and restart the terminal emulator.

Ohh i tried wezterm and ghostty. Couldn’t get them working using just software rendering. And once st worked, I realized I don’t need it tbh.

2 เดือนที่ผ่านมาdiscuss

Ohh yes, a minority of us do exist. I prefer it over appimages on my personal pc. Gets you almost rolling release software without needing to use a rolling release. I used to use distrobox with arch Linux on pop os base, but then just gave homebrew and nix a try to scratch the itch.

Nix is not there yet in terms of user friendliness. homebrew for linux is pretty awesome.

Only issue i have is that it creates a separate user and doesn’t support custom prefixes (their page says you are on your own if using custom prefixes). While their reasoning is sound, not having an easy way to know which programs will break if using custom prefix is a bummer for me at work.

2 เดือนที่ผ่านมาdiscuss

Ohh acquired taste it is.. I had two stints with suckless software. First, when i was in early twenties when I had a lot of time in the world, and thought the manliest way to talk to a machine is all through low level C code. Had a whole flow to patch it and heck the code is so well written and commented, i was able to understand it. Then, i guess life happened and i discovered more interesting stuff to spend time on.

And now in my late twenties, suckless terminal is the only one that would work reliably on a shitty old enterprise linux system at work. Yeah, we got xterm and konsole (the older one). I am seeing them in a whole different light now. I did not read the source code now and it is effectively a foreign language to me, but just being able to have modern features in it without too many dependencies is a different level of bliss. This time, I am glad I have the flexi patch to the rescue since, i passed on suckless terminal as a real alternative since I don’t want to patch it manually or solve merge conflicts!

Even though I don’t like the elitist attitude of the project, can’t deny they got a point. Why does a terminal emulator need to be so complicated!

https://github.com/bakkeby/st-flexipatch

3 เดือนที่ผ่านมาdiscuss

I like the very idea of tree sitter and even listening to the first talk video by the creator was interesting. However, it has been big barrier for me to write grammar for it for a custom lisp based DSL used in industry (called SKILL; think lisp but with support for both C and lisp styles syntax), and the regex based syntax shines well here since iterating over it does not need recompile and also is incremental independent rules compared to the syntax tree based with hierarchy.