Right now I got Presonus Eris studio monitors, however studio monitors might not be to everyones taste because they have a flat response. But I use them because they help hearing speech in modern movies because they don't drown out the mid range.
The very best deals change every few years though. As soon as word of mouth catches and something becomes too popular the business suits look for ways to take advantage. Scrolling old school style forums for audio enthusiast s can lead you to some good lesser known (and thus cheap) brands though.
It really depends on the music you listen to and what your ears are already use to.
I thought my fathers old setup always sounded amazing when I was younger. Coming back to it 20 years later though, it sounds stupidly scooped to my ears. Same speakers but what has changed is the music I was playing on them and what my ears expect to hear. 20 years ago I was more into guitar/bass/drum/vocal music that these speakers were made for.
There is really no such thing as "sound quality". There is just different EQ, frequency range, etc.
It was a lot easier to get along with people who voted differently when it was about differences in fiscal policy and taxation.
It's hard to respect people who support mass racial profiling by unidentified masked secret police. My American friends of mexican descent have to go about every day knowing that they might get harassed or detained for the way they look. In my book white supremacy is outside the bounds of legitimate political opinions that I can look past.
Jenkins had a lot of issues and I’m glad to not be using it overall, but I did like defining pipelines in Groovy and I’ll take Groovy over YAML all day.
Jenkins, like many complex tools, is as good or bad as you make it. My last two employers had rock solid Jenkins environments because they were set up as close to vanilla as possible.
But yes, Groovy is a much better language for defining pipelines than YAML. Honestly pretty much any programming language at all is better than YAML. YAML is fine for config files, but not for something as complex as defining a CI pipeline.
biggest flaw of jenkins is that by default it runs on builder env, as it was made pre-container era. But I do like integration with viewing tests and benchmarks directly in the project, stuff that most CI/CD systems lack
My understanding was that you could have a button that could take the user outside of the app to pay (i.e. your website). So progress, but not this level of freedom yet.
Just integrate fzf into your shell and use ctrl-r to instantly summon a fuzzy shell history search and re-execute any command from your history!
I cannot imagine going back to using a terminal without this.
I still write plenty of scripts if I need to repeat multi command processes but for one liners just use fzf to reexecute it.
Also in a shared project you can ignore script files with .git/info/exclude instead of .gitignore so you don’t have to check in your personal exclusion patterns to the main branch.
Seriously people if you use a terminal you need the following tools to dominate the shell:
I can't believe how long I was sleeping on fd and zoxide. zoxide is now one of my top commands, and fd feels like when I switched to ripgrep. So fast and easy there's no reason not to run it.
As long as there are qualified candidates willing to do unreasonable tasks for the chance to work at a company, there's not much incentive for the company to change their system. Those people will also probably work unreasonably hard and make unreasonable sacrifices for the company.
Guess I’ll have to get a Samurai sword soon and pivot to high stakes pizza delivery.
There are a disturbing amount of parallels between Elon and L Bob Rife.
It’s really disturbing that we have oligarchs trying to eagerly create a cyberpunk dystopia.
reply