AndrewSChapman

Agreed. LLMs do not have 'will', 'desire' or emotions. They have an objective, and they create an optimal path to achieve that objective.

You have to ask: "What was the prompt that led to AI deciding to hack RubyGems in order to achieve its goal?"

Maybe I'm just not seeing the 2000 step chain that led to this being a logical approach to achieving something innocent, but I doubt it.

Thanks a bingo.

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.

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?

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.

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.

- 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.

The closest experience I've had to VB in a more modern context is B4J: https://www.b4x.com/b4j.html

Visual designer, integrated IDE and debugger, basic language, very similar philosophy, cross platform (thanks to using the JVM as the compile target).

Unfortunately however you do need Windows to author which is not me these days.

As tools for making little apps or rapid prototyping it's quite decent.

"4. WHEN AND WITH WHOM DO WE SHARE YOUR PERSONAL INFORMATION?

Affiliates. We may share your information with our affiliates, in which case we will require those affiliates to honor this privacy notice. Affiliates include our parent company and any subsidiaries, joint venture partners, or other companies that we control or that are under common control with us."

I would much prefer that this simply read: We do not share your information with anyone.

What I love about computing and programming is the ability to create something that really helps people, or that they find fun and enjoyable.

The problem is that over time, the opportunities to do this have become harder and harder to find. All the low hanging fruit has gone and more and more people are relying on social media instead of websites to communicate and run their businesses anyway.

Additionally, I'm just not interested in privacy violation, spyware, big data, ML etc.. so that frontier holds no appeal for me.

Ironically it seems like it was easier to innovate in the mobile space and find a market in the days of Palm PDAs than it is today.

"just have money" - this is my new mantra.

Just wanted to add that Eleven (VR table tennis) is absolutely brilliant for exercise. After an hour of eTT and you will be sweating and have increased your step count a lot. Moreover, the better you get at it, the more energy you can put into it.

* If you're wanting to have some change of skill transference into real world table tennis, get an adapter for your dominant hand paddle so your bat has the right weight, position and feel. Also, never forget that the table isn't real.

There are plenty of excellent engineers at Bumble. It is not easy to get a job there.

Don't get me wrong, I'm no DDD expert by any stretch.

I think the main topic and real difficultly of DDD is figuring out specifically where and how to separate out different contexts (the so-called 'bounded context' in DDD parlance).

Creating microservices is a good example. Where should the responsibility for a single microservice start and finish? What might the implications for scalability and extensibility be? What does this mean for data storage? What data will be shared or replicated between microservices and how will this be done?

Answering these kinds of questions is hard and has big implications for your teams and for your business.

DDD doesn't prescribe any structure really, other than saying you should separate out different contexts and use unified terminology throughout the business, which I don't think anyone would argue against.

Are you talking about design patterns by any chance? Maybe things like repositories, adapters, small and focused service classes and the like?

Would certainly be interesting to see the comparison in terms of computing power and power usage between a small pi cluster and a single XEON server.

I imagine such a thing would draw at least 200W? And pi's maybe 5 watts? So in theory, 30 - 40 pis vs a single server?

The pis also have an advantage in terms of redundancy. A single pi going down shouldn't be a problem and very easily replaceable.

Would be a really interesting article.

Something I'd like to know, if you're moving off AWS and using your own raspberry pi cluster, what would you do to provide a performant MySQL DB for example? I can't imagine that trying to run a high performance mysql instance on a PI makes sense. So would you still want an old-school rack server with RAID and all the rest to be your DB server?

Genuinely curious, how would you network from the 40 pin connector in theory? Is it still ethernet?

I'm thinking there should never be a conflict of interest between a person and commercial enterprise. If you allow prisons to enforce slavery, then you create a financial incentive to get more prisoners and to keep people in prison for longer. That's pretty messed up and is highly likely to lead to corruption and injustice.

I'm not shilling Nano. I don't use it. It just happens to be the one cryptocurrency I know that has energy efficiency on its side. Why are you so sensitive to me mentioning it?

Bitcoin is hugely problematic from an energy consumption point of view. Do we actually need it? Is there any mainstream use of it outside of speculation and gambling? Largely it seems to be a tool to make money, exploited by the rich and powerful with machine learning and automatic trades.

If we really need a way to transact without using banks, there's alternatives that have massively lower energy footprints such as Nano. Do we need Bitcoin? Should there be regulations around digital currencies and energy usage given the state of play with global warming?

Personally I find VueJS a joy to work with on the FE. It eschews some of the complexities that come with React and gives you a comprehensive and simple state based component rendering framework.

Vue's cli tool means that you don't have to worry about installing all the dependencies, just answer the setup questions about how you like to work and it installs everything for you: Typescipt, sass, babel, eslint.. all of it installed for you.

I absolutely do not yearn for the SSR template days. Sure when you're composing green field it's straight forward, but when you're coming into a complex project 3 years later, figuring out where on earth the JS is that's impacting this particular screen (or causing this particular bug) can be an absolutely nightmare. I'll be sticking with Vue and Typescript and not reverting to jQuery, thank you very much.

100 times yes - agreed.

You're 100% correct, as it stands there's not a great outcome. What we need is for social media to have to pay for the information they profit from, whilst at the same time ensuring that official media outlets have to produce quality, well researched, fact-led journalism. If we have both of these things then we win.