Hacker News new | past | comments | ask | show | jobs | submit | AndrewSChapman's comments login

This. High level OKRs should be set by the company to steer the ship, and engineering OKRs should align with the company OKRs. Thus, the roadmap is defined by the OKRs - I believe that's the whole point.


It just takes so many cycles to get to a point where everyone in the company is on-boarded to OKRs properly and by then people are burnt out on them, going through the motions without seeing the value, at least from the bottom up.


A better version of this article: https://vhsoverdrive.neocities.org/essays/oldweb


I could be wrong, but I think Vertx would be a better choice? https://vertx.io/

It's actively maintained with full time developers, performant, supports Kotlin out of the box, and has more features?


I've used vert.x in a big project once. I don't ever want to do that again. Performance is pretty good, but the developer experience is beyond clunky.

My current favourite Java server framework is Micronaut.

Great performance and easy to develop for!

https://micronaut.io/


Another vote for Micronaut. I’ve moved a Vert.x project to it recently. I love it. I will say though there are a lot of footguns and the wide variety of choices e.g. for persistence, views, etc make it hard to figure out the “right” way to do things. But the framework just really clicks for me.


I kinda liked the freedom to choose persistence myself, it was one of the things that enabled us to choose it at Mojang, since at the time it wasn't clear if we were going to migrate to a different cloud or not, being able to replace the persistence layer was essential.

As for footguns, I agree there are plenty, but in my experience at least, fewer than in most Frameworks I've used.

Didn't use views much, we built a JSON API, so there wasn't much need for it.

One thing I really liked about it was that it was so easy to get in touch with the Devs, and they so quick to fix things!

We started implementing our API with it before they released 1.0, and as such there were plenty of bugs in the beginning. Quite frequently we submitted a bug report, and there'd be a new version released the same or the next day with a fix for it! Very impressive!

I might've had bad luck with the team where I used vert.x but I've seen a few things in there I would categorize as foot-howitzers, I guess it's just hard to create a framework that can be used for anything without also enabling users to blow their feet off.

Sorry about the rambling comment, just happy to share my thoughts with a fellow Micronaut fan <3


I’d say Javalin is more of a successor. Vert.x is too focused on reactive programming to qualify as a successor IMO.


The community of vert.x is quite active. There’s a Discord server where discussions, releases info and help questions are being published in live chat.

Vert.x has already adopted VTs and in general its documentation is still one of the best I‘ve seen.

Really impressive work on the toolkit all these years. I love working with it.


Reactive garbage.


Personally I think that anyone who believes that they're going to die before climate change kicks them in the nuts are in for an almighty shock (unless you're 80).

My prediction is that we have at best 10 years of anything resembling BAU before systematic failure.

https://medium.com/@smokingtyger/the-crisis-report-27-4e7e9f...

Happy reading.


Really? You're looking at the graph, showing a clear and frankly ominous anomaly, especially in the context of the clear wording around "the oceans should be warmest in March, not August", and this is your response? Well done.


Right?

You'd hope that the kind of audience that this site has would be able to read and understand graphs and statistics. But seems like nope.

Imagine looking at e.g. some service RPC logs and seeing P95 latencies off the charts during certain peak hours of the day but then just taking the average of the whole day and being like "only 10ms higher than the day before so it's fine"

I mean, I failed high school math but have since had to learn enough stats in my career to understand the consequences of ignoring variance...


Anomaly (your word) != trend . It only becomes a trend when it happens more than once, by definition.


Agree! I am in the UK and have an electric bike, but I only use it for trips where I know I can safely store the bike and where I know the roads intimately. The UK needs to solve this, in addition to improving the safety of roads. There's too many pot holes, poor visibility due to people being allow to park pretty much anywhere, and not enough dedicated bike lanes.


IndexDb is not a relational data store. It's much closer to Mongo than it it to Sqlite.

If you want relational tables, joins, aggregations etc, you want something like this (or the original Web SQL that was deprecated).

There is definitely a use case for it.


> It's much closer to Mongo than it it to Sqlite.

If only. It’s much closer to DBM than it is to Mongo.


- The use of AI will become mainstream with your average person using it directly - it becomes the first truly revolutionary technology change since smart phones were invented. Serious social questions start being raised.

- The war in Ukraine will continue on but not conclude, with many more casualties on both sides. Consequentially, the stock price of principal US defence contractors such as Lockheed Martin and Northrop Grumman will continue their significant upward trend.

- Once again, CO2 emissions will continue increasing globally. There will likely be some significant food shortages in part of the world.

- The UK will continue its economic descent, with more significant energy price increases and continued inflation.


Agree.


This is great for when you have to send someone a link to something but you don't really want them to open it.


“Our terms of service have recently changed…”


Dear shareholders...


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: