HN user

nonconvergent

104 karma
Posts0
Comments34
View on HN
No posts found.
Git is too hard 6 years ago

The main problem I run into with git is communicating with my teams about editing history and how they shouldn't.

Particularly on teams that like to keep main clean and avoid reverts and merge commits in favor of rebasing. Thankfully my current team likes to keep their PRs clean and main is whatever works.

That and merge conflicts, especially on a stale branch. I use cli for most things and Intellij's merge tool for merge conflicts because I can get a clear view of what's what.

Because they still benefit. They benefit when people consume their products and they benefit when they're given a forum within the community.

A VPN isn't itself secure. It's only a secure tunnel. If the VPN's exit is insecure, then you're insecure. DNS-Over-HTTPS hasn't reached ubiquity yet but VPNs are very useful but are having a reckoning with serverside attacks and governments demanding "oversight" and backdoors (like the recent move by China on foreign owned but China-located companies VPN usage).

or you can say something equivalent yet unambiguous

A good commit message isn't about convention, and no convention makes a commit message good.

When I review a commit, I need only the information I won't get from the diff that I need to understand the context and the behavior.

My brainpower is a limited resource and extra noise in my signal is extra work.

I'm totally here for `ISSUE_123456 fixes defect` and `wip` are insufficient, but I'm not writing a code blog post in there.

The CEO of SpaceX did commit a couple crimes in the same podcast.

Uber's autonomous car fatally collided with a woman, raising questions of negligence and liability in automation.

Uber acquired some of Alphabet/Waymo's trade secrets when they aqui-hired one of their former engineers who apparently kept a bunch of Waymo's IP he worked on. That engineer himself is now facing a federal indictment, and Uber and Waymo have settled.

E-scooters are facilitating a number of city-specific crimes (it's usually illegal to operate a vehicle, bike, or skate on a city sidewalk and the e-scooters do not provide helmets but neither do the riders). To say nothing of the legally dubious use of public property to deploy them.

Move fast and break stuff indeed.

Let's keep in mind that this is an end user application for pixel artwork. You and I might care that it's Rust. End Users will not. It could be written in Malbolge or BF for all an end user cares about.

Namespace collision is gonna be a pain for end users and newcomers, possibly depressing discovery, which is our point.

which is why you want more tracing and less logging. log messages are always an art and I myself am a poor artist when it come to predicting what is both necessary and useful enough to log without overall increasing the log noise.

Tracing will show you the distributed behavior, but the best log, at most, can only show you the current state of information on a single service on a single node even when you aggregate. Tracing also works hand in hand because the correlation id should associate with the relevant log message when you do decide to drill down.

I was not referring to that. I was referring to the matter that they weren't ready to jump TO JDK 8 when JDK 7 was EOL, nor the next year, nor the next year after that.

What did they do with security updates when they were available for the version they were on?

Questions.

Don't get me wrong, they're not the only ones ice skating uphill on this.

Java 8 is EOL in January for public support/security patches. Java 7 was EOL in 2015. What have you been doing for 3 years?

I could guess, because I've been at companies doing the same. Active development and support on the product, but no time for tech debt.

Java 9 and up I understand people getting frustrated with a more frequent LTS release and these weird microreleases every year.

The type of status/error matters. It's how your communicate, server to client.

Think about your normal interactions with problem solving as a team. What's more useful, a teammate who tells you when there's a problem what the problem is or a teammate who hides things, obfuscates, and makes random jokes?

400 tells you asked in a way that wasn't understood.

401 says you're unauthorized and 403 says you're not allowed (similar but potentially different implications, not my favorite nuance but it's a common example that might come up)

504 says there's a problem communicating between the two of you.

404 says that your data doesn't exist.

500 says the server is having problems doing the thing and it's completely out of your hands.

418 says "I'm a teapot"

What's more useful data?

Wouldn't that be more of an issue of not having an SLA between SaaS and client?

If the silly non-automated dashboard is part of the SLA, then it costs someone money/liability/trust to not maintain it, otherwise "who cares as long the issue gets resolved, people who care about the issue are tracking the bug report?"

That's what contributors are for. OSS has always been dependent on localization support from contributors, especially for documentation.

Yeah, it just explains Dijkstra's and not very well. A big point is that Dijkstra's like many MST producing algorithms gives you A minimum spanning tree, not necessarily THE minimum spanning tree.

And why does the price of 2 drinks to the same vertex change? Shouldn't all edges on a vertex share the same cost if the edges are only weighted by the cost of 2 drinks? If the edges were a combination of drink and travel costs, maybe this makes more sense (though you still wouldn't see a $0 edge).

Senator Isakson gave a townhall Monday. One of the questions was a rambling explainer that could be best summarized is "Net neutrality is about not censoring the internet so do you support it?" to which of course responded "I do not support censorship so we have to deregulate to ensure it."

The guy practiacally showed Isakson the door.