They’ve got a solution for you! https://github.com/tbg/bikesheddb
977 karma · joined July 29, 2016
1 on 1s can vary a lot from person to person. I absolutely love my manager, but we’ve never had a 1 on 1 where she spelled out how I’m tracking towards goals. That’d be wayyyyy too formal for the nature of our working relationship. She just lets me know if I make mistakes as they happen, and relies on me to raise issues to her when it makes sense.
Now that I’m a manager as well, I have some team members who prefer to keep things less formal, in the same vein as me and my manager, and some that prefer more direct and organized feedback. I think a good manager needs to be adaptable and willing to match the working relationship that each person is most comfortable with.
It's statements like that which drive me crazy. It may very well have lower overhead, but even a function call has overhead, and OSGi's overhead is not small (at least last time I used it, circa 2012).
Remember Eclipse? Remember how, once you installed a couple of java plugins, it'd take up to several minutes to start up? All those plugins were OSGi, via the Equinox framework. The overhead was noticeable and severe. Contrast that to IntelliJ, where I have it set up to support a dozen or so languages, all with various plugins, and startup never takes more than 30 seconds. Still not as fast as I'd like, but I shudder to think how Eclipse would manage.
I also echo a lot of the commenters here from the development perspective. OSGi is one of the least pleasant systems I've had to write for. Some of that comes down to Java's questionable approach to dynamic class loading, but OSGi added a ton of cruft and complexity on top of that.
This is actually super simple to do in Cockroach, as it supports time travel queries - https://www.cockroachlabs.com/blog/time-travel-queries-selec...
So you can run a script at, say, 12:05 AM every morning, saving the table state “AS OF SYSTEM TIME 12:00” (simplifying syntax). And thereby get a fully consistent snapshot of all tables, as long as your backup script takes less time to execute than the configured table TTLs
So security isn’t a concern to you at all, huh? Or are you just really bad at understanding security?
I’m an engineering manager in an infrastructure team (not at all affiliated with Digital Ocean, tho full disclosure, I do have one droplet for my personal website). I know how postmortems generally work, and it’s messy enough to track down root cause even when it’s not some complex algorithm like fraud detection going off the rails.
I’d rather get slow information than misinformation, but I understand the frustration in not being able to see the inner working of how an incident is being handled.
That’s akin to saying “we’ll never ship a bug”, or “we have an SLO of 100%”. That’s impossible for anyone to claim. Same goes for the response handling. There is clearly a lot of room for improvement there, but if you’re insisting on not getting canned response, that means a human needs to be involved at some point. Humans will at times be slow to respond. Humans will at times make mistakes. This is just an unavoidable reality.
I get that mob mentality is strong when shit hits the fan publicly, but have a bit of empathy and think about what reasonable solutions you may come up with if you were to be in their situation, rather than asking for a “magic bullet”.
I could see a good response here being an overhaul of their incident response policy, especially in terms of L1 support. Probably by beefing up the L2 staffing, and escalating issues more often and more quickly. L2 support is generally product engineers rather than dedicated support staff/contractors, so it’s more expensive to do for sure, but having engineers closer to the “front line” in responding to issues closes the loop better for integrating fixes into the product, and identifying erroneous behavior more quickly.
Companies are made of people. Let the people have a life. Their night is shitty enough as is after this, I guarantee you.
Removing competition is literally the most anticompetitive thing you can do. Like definitionally.
That’s why all major (edit: US) acquisitions take months to years to get approval from the SEC.
A lot of the power of go comes from it being opinionated, but that same opinionated approach is a real pain for some (it turns out common) use cases. With all that said, Go is my language of choice, and I'm happy that Rob seems to be less involved with Go 2.0, and that the core Go team is incorporating user feedback rather than just dismissing complaints as Pike seemed so inclined to do.
But that’s a pretty big risk to do with a single novel. Harry Potter had a massive and loyal fan base by the time the 7th and 8th movies came out.
The long of the short of it is that moon goes boom, kills life on earth, humanity survives onboard the ISS and a flurry of small habitation pods which are splayed out into a string so they share an orbit, but isolated in case they get hit by space debris.
The book came out in 2015, and despite having a fictional plot, nearly all of the science checks out.
And for those that like videos, that link includes a Tom Scott YouTube video as well.
They may never describe Kafka itself without the word "semantics", but here are some other snippets:
- "I know what some of you are thinking. Exactly once delivery is impossible" - "While some have outright said that exactly once delivery is probably impossible!"
They mix their phrasing depending on what they're talking about, and whether they are referring to Kafka directly or indirectly.
They are intentionally using this phrasing to obscure the fact that nothing novel is happening to push sales, and it is absolutely infuriating how well it works.
Calling it “exactly once” is marketing BS. It’s the same as Oracle claiming for years to support serializable transactions when they didn’t, except that one is technically possible, they just didn’t support it in actuality.
Crypto currencies overlook the benefits of a centralized currency - some entity to correct mistakes. Fiat currency is backed by the trust in a nation state for example. If my money disappears, I have some authority I can appeal to for addressing it. Whether they do address it or not is a different question, but at least there’s a process.
When someone in stellar screws up and locks out wallets, or when Mt. Gox loses mounds of bitcoins, there is no recourse. Just a “oh, the math makes fixing that impossible” response. Or they can take the ethereum approach and just rewrite history to cover up your mistakes, delegitimizing the entire currency in the process.
In a world with pure intentions and no mistakes that may work, but the real world is messy and people are any combination of stupid, forgetful, and malicious.
Crypto currencies and distributed ledgers are interesting in theory, but will fail due to the implications of needing to operate in the real world.
Stellar, like the rest of the cryptocurrencies, can go die in a fire as far as I’m concerned.
No idea what I did to deserve that tone. That site also gives a high level overview of the change, which is why I linked it.
> What’s to stop someone else from backporting security fixes as needed ad infinitum?
Who? I haven’t heard anyone express a willingness to take up that mantle. “Someone will probably support it by the end of the year” is not the most robust security model.
An end is in sight, is coming soon, and it’s sort of concerning that more folks haven’t realized it yet - https://pythonclock.org/
One truck parked in the middle of the road to deliver something, or one car blocking the box at an intersection and it’s a standstill.
Also, Highway 101 turns into a residential street with stoplights for several miles.
But they refuse because of “historic significance”. That’s one sure fire way to get your city to be historically insignificant in the long run.