Taxes are supposed to pay for public services. An efficient visa system is a public service. If you pay tons of taxes but don’t get a public service that’s personally very important to you, it’s natural to feel let down
My version of that is to just use a (high-end) Chromebook. The OS never gets in the way, can’t remember the last time I had to change a system setting or manually upgrade anything
Ironically the UX on Reuters and AP wasn’t hugely worse than the blogspam:
* the text of the blogspam is pretty faithful to the AP article
* Reuters had a fullscreen paywall
* the AP had a floating video ad and an interstitial you have to click to get below the fold
I agree it does a pretty good job of communicating that. I think the other commenters are pointing out that doesn’t show how to efficiently get all the smaller items left of the partition and larger ones to the right. While that’s probably second nature to most people who’ve taken an algorithms class or done a decent amount of programming, I guess it’s up for interpretation how obvious it would be to the “intended audience” of the ikea manual
It’s a class/geographical thing. In my early childhood in a fancy suburb of a big city, my parents and people in their social circle used mixes 0% of the time, but when we moved to a smaller town it was way more common.
Agreed. I work at a highly successful small company with a reputation for being grindy, and what that looks like in reality is probably 55 hours a week of largely focused productive work: typical core hours are 9-6:45ish, and you work longer a day or two a week and put in the odd evening or weekend hour. It’s hard to imagine working 9-9 every day
IMO, effective "scripting" just means the ability to solve ad hoc problems easily by writing task-specific glue that delegates the hard parts of the program to (1) an effective set of libraries you've written yourself and (2) external code or tools when it makes sense.
From this perspective, the languages of the glue, the libraries, and the external code all matter less than the ease of writing the glue; interfacing with the external code; and maintaining the libraries. The best language for this probably comes down to a combination of what you're comfortable writing (and reading, and maintaining) and what kinds of tasks you're trying to solve.
For me personally, using Python glue and libraries strikes a pretty good balance here. Writing a script "in Python" doesn't mean you need to reinvent the wheel. If you think `parallel` provides a better interface for map-reduce parallelism than `subprocess` (or than a library function you've written on top of `subprocess`), no problem: you can just call `parallel` from Python (and you'll probably find yourself writing a library function on top of it to abstract away the fact that it's a shell script).
But if you're much more effective working in Bash than Python, then writing your glue and developing your libraries in Bash could be the way to go.
I interned on their SQL engine team and maybe half of the long-time employees were ex-Oracle, including two of the three co-founders (Thierry and Benoit).