BossingAround

I'm so sorry, what's cool about the project? It's literally 10 paragraphs that you can copy. You can copy the same paragraphs into a comment here and have, presumably, very similar experience (without the megabytes of data) for a static site.

I don't mean this derogatively, I just don't understand how is this better than literally any lorem ipsum generator.

I'm getting very strong "It's not a generator, Jerry!" energy.

I'd say the majority of office jobs won't really use arrow keys. Most people will rather use the mouse to move around, and engineers would use something closer to the center of the keyboard (like hjkl).

Personally, I found the perfect keyboard in Ergodox [0][1]. Ortholinear, split, programmable (and open-source) keyboard with hot-swappable switches.

I've had my Ergodox EZ [2] for ~7 years now. The biggest problem that happened was that some of the switches started malfunctioning - fixing which was a matter of literally 5 minutes.

I don't think I would want to go back to non-split, non-ortholinear keyboards nowadays. 00Key looks cool though, that's for sure! :)

[0] https://github.com/Ergodox-io

[1] https://www.ergodox.io/

[2] https://ergodox-ez.com/

You know, I think you're right. I never realized that Python list comprehension is basically filter/map (and reduce is an external function). That is actually pretty horrible syntax for it from that perspective.

Managers have never cared about software engineering.

Isn't that how it always is as any company matures? In a big company, you don't need just 5-star devs. You also need a 3-star devs (and even 2-star devs) that work 9 to 3:30 (and maybe do emails/slack between 3:30 - 4; bonus points if they study from 4 to 5). You need people that can take basic requirements and turn them into code that your 5-star devs are too bored to write. You need people who look at customer bugs, can do debugging and submit a patch to fix a corner case your 5-star dev didn't think about 4 years when they were hopped up on caffeine, hopes and dreams.

Also junior developers, who might not realize that they are paid to think, not write LOCs.

Not only fixing the same bug twice, but also fixing bugs that happen because of using the same functionality in different places. For example, possible inconsistency that results from maintaining state in multiple different locations can be a nightmare, esp. in hard-to-debug systems like highly parallelized or distributed architecture.

Were the intense daily meetings any help? I can imagine that if there's a ticket to be solved, and I can talk about the problem for 40 minutes to more experienced coworkers, that actually speeds up the necessary dev time by quite a lot.

Of course, it will probably just devolve into a disengaged group of people that read emails or Slack in another window, so there's that.

Sometimes, I spend an hour writing a perfect function, and then spend another hour re-reading the beauty of it, just to be pointed out how imperfect the function is in the PR review :))

Oh man, these looked so awesome. I miss these phones sometimes. There was something cool about seeing what features different phones had. Nowadays, it's basically iOS vs Android, where both OSes do pretty much the same things, and it's all about the apps.

The use case is pretty much the 3rd sentence in the link:

> It is helpful if you accidentally record more than 100MB (the github limit) for a demo video you wish to put in a Github PR.

In other words, you have a video, you want to attach it to the PR, it's 105MB. Now your option is to put it on YT and share a link, or use this tool and be able to simply drag/drop it to the PR.

In the demo, the 118MB file is compressed to something like 18MB, which is quite impressive, and could also help people who have slow upload speeds.

Honestly, I would recommend never using "this" or "that" - it often makes sense only after you force the reader to re-read the sentence.

I would add eliminating future tense. There's very few times when future tense is actually required. It's one of my pet peeves when docs say something like "Click X. This will open a prompt ..." when it can say "Click x. This opens a prompt ..."

You can maintain it right now. Make a fork, and continue development. You might even get some shoutout from the original devs. It's all open source after all, making this repo read-only doesn't mean the project's dead if the community is vibrant enough.

By that token, nobody needs math today because computers do it for us.

RSS feeds are easily scriptable

Why do you care about filesystem performance in containers? If you're running a DB from it, you surely have <10-20 concurrent users (e.g. other containers) to that DB, so who cares whether a lookup takes 1us or 10ms?

Isn't Apple locking unsigned binaries from being run on macOS?

(which still doesn't work on mac)

Nope

Not sure how that relates to anything else, but sell it then?

Off topic, but when you click a photo in this blog, that's a proper nightmare. There's no way to get back to the article, and the back button exits the whole page.

Talk about bad UX.

Wow, this is a blast from the past for me - I was examining the framework in 2015. Amazing to see it's still well and alive. Back then, I'd simply use some resteasy framework.

It's either Spring, or Java EE's way (together with the new Jakarta EE paradigm, which is actually pretty cool if you ask me). I've seen the latter a lot more in the enterprise sphere.

> With ChatGPT, I need to copy the text into a premade prompt or pick a GPT made to improve my writing. But, the writing style may not match what I want. Going back and forth with chat instructions is slow

Sounds like a UX problem that's trivial to solve with a browser plugin.

From [1], "Adjectives modify nouns; adverbs modify verbs, ..." - so though you're right that both sentences are grammatical, I think a lot of styles would have a problem with "a proper written sentence" since what you actually mean to say is "a properly written sentence" (unless you make it clear that you speak of "proper sentences", probably).

[1] https://owl.purdue.edu/owl/general_writing/grammar/how_to_us...

True, but at least the author wouldn't be liable.

It's a depressing era with post-covid sugar crash, new wars, getting over inflation, job market being in the trash, etc. etc.

I'd argue there are no "happy offices" as a whole, and won't be for another ~10 years until everything settles and we're on an upwards trajectory (and sugar rush) again.

"Gratuity" is an amazing euphemism for corruption in a system :))