I guess everyone uses 20% percent of Jira - just a different 20% ... [1]
We're using GitHub for everything here, but was using Jira as an email first helpdesk.
Was hoping this was that - but apparently not at all.
We almost went with libredesk - but it's a little too simple (no merging tickets?). We're giving FreeScout a go - looks like we might need the oauth2 plugin to work with o365 mail ...
> A lot of software developers are seduced by the old “80/20” rule. It seems to make a lot of sense: 80% of the people use 20% of the features. So you convince yourself that you only need to implement 20% of the features, and you can still sell 80% as many copies.
> Unfortunately, it’s never the same 20%. Everybody uses a different set of features.
> When I was a kid, my grandparents were involved in a pretty decent intercontinental floppy disk piracy ring. They would buy and clone software sold locally and send it forward and get copies of games in response. My parents ran a small business converting peoples university notes/recordings into well written essays. My grandparents had a PC with Prince of Persia, and as payment for my parents essay writing services one of their friends from Hong Kong used to come around and teach me how to play. See he couldn't speak or understand english very well, but he had memorised the potions you needed to drink to get past each level, and also the fighting technique of most of the bad guys.
Sounds like the summary of the opening chapter of a Bruce Sterling novel.
Love that your Hong Kong friend memorized the DRM codes.
Of course, DRM was no issue with a cracked copy of the game...
Stow only symlinks. That's even one layer below GoboLinux, and GoboLinux is not extremely active either (it is not dead, but kind of semi-dormant, that is sometimes a few changes and improvements are added, then it goes back to hibernation again).
Since there was a recent thread on react compiler[r] - I wonder if adding/pushing the code through react compiler would help? (Assuming it's not already being used)
[r] Thread was about rewrite in rust, but it made me have a look at the purpose/claims made by the project - and fine-grained, automated memoization for speed seems central.
One way in which automated drones might be considered bad, is (if) they cannot accept surrender - but are used in scenarios where human operators could.
This is a much more difficult distinction to make than you're letting on. Cruise missiles offer no quarter, but manually operated drones might (though there is often no way to capture the opponents). The question is what is the difference between the two weapons systems...
The docker compose example is just a demo. I don't know anyone who runs Postgres with docker compose / swarm in prod :) But yes, happy to add volumes so it seems more real.
But clearly that was before LLMs captured the zeitgeist - I'd be curious to how people see it today - I'm sure a few people have parts of this (or equivalent) in their AGENT.md or similar?
I also wonder how the last part holds up:
> 80/15/5. Spend 80% of your time on low-risk/reasonable-payoff work. Spend 15% of your time on related high-risk/high-payoff work. Spend 5% of your time on things that tickle you, regardless of payoff. Teach the next generation to do your 80% job. By the time someone is ready to take over, one of your 15% experiments (or, less frequently, one of your 5% experiments) will have paid off and will become your new 80%. Repeat.
Also, reading that recent discussion on hn - it's remarkable how much LLMs and AI has changed the discourse in a short time.
We're using GitHub for everything here, but was using Jira as an email first helpdesk.
Was hoping this was that - but apparently not at all.
We almost went with libredesk - but it's a little too simple (no merging tickets?). We're giving FreeScout a go - looks like we might need the oauth2 plugin to work with o365 mail ...
[1] https://www.joelonsoftware.com/2001/03/23/strategy-letter-iv...
> A lot of software developers are seduced by the old “80/20” rule. It seems to make a lot of sense: 80% of the people use 20% of the features. So you convince yourself that you only need to implement 20% of the features, and you can still sell 80% as many copies.
> Unfortunately, it’s never the same 20%. Everybody uses a different set of features.
-- Joel Splosky
reply