HN user

arcologies1985

69 karma
Posts0
Comments30
View on HN
No posts found.

literally just 'git rebase origin/main' to insert new commits to main into my branch history prior to the commits I made. No rewrites of later commits required if there are no conflicts. You seem to have an extreme misunderstanding of how git works.

Kimi Claw 5 months ago

What you and I consider routine work, someone who works with mostly Webdev or might consider extremely difficult. There a lot of programmers who have never used a Linux shell, or know much about networking beyond TCP, or used Linux before outside of a uni class 20 years ago.

Kimi Claw 5 months ago

Installing it on your PC or laptop puts your personal data and ISP subscription at risk, while installing it in a hosted VM yourself requires a bunch of Linux security and networking knowledge or else you'll get pwned pretty much immediately (https://youtu.be/40SnEd1RWUU). So this service is giving you a VM already set up with a security baseline.

At my workplace we now use Claude Code to parse written specs and source code, search through JIRA, and draft, refine and organize tickets (using the JIRA API via a CLI tool). Way faster than through the UI.

However as you point out we have no program-accessible source of data on who stakeholders, contributors, managers, etc. are and have to write a lot of that ourselves. For a smaller business perhaps one could write all of that down in an accessible way to improve this but for a large dynamic business it seems very difficult.

Issues, CI, and downloads for built binaries aren't part of vanilla Git. CI in particular can be hard if you make a multi-platform project and don't want to have to buy a new mac every few years.

I have worked at organizations where most engineering and many product decisions were made bottom-up, through written RFDs and ADRs, and horizontal conversations between lead, staff and principal engineers. The tradeoff is that it can take weeks, months or years to both agree or schedule work on larger projects, where other (especially small) organizations might take hours to weeks.

Vouch 5 months ago

In my OSS projects I appreciate if someone opens an issue or discussion with their idea first rather than starting with a PR. PRs often put me in an awkward position of saying "this code works, but doesn't align with other directions I'm taking this project" (e.g. API design, or a change making it harder to reach longer term goals)

Various patents expired and now you can get excellent typing keyboards from China for $30-50. Basically everyone I know who types for a living has one.

Gamers have moved on to analog keyboards which are controversial because some of their features straddle the line into cheats. e.g. with an analog keyboards you can negate all inertia in Counter-Strike or do speed tricks in Trackmania not otherwise easily accessible to keyboard players.

Planes are required to comply with instructions; if they don't they're committing a serious crime and the fighters are well within their international legal framework to shoot the plane down. They would likely escalate to a warning shot with the gun past the cockpit, and if the aircraft is large enough they might try to shoot out one engine instead of the wing or fuselage.