wakeless

I'm assuming there's an optimisation in the source of this:

``` if(github) return false ```

I did a similar set of evals myself utilising the baseline capabilities that Phoenix (elixir) ships with and then skillified them.

Regularly the skills were not being loaded and thus not utilised. The outputs themselves were fine. This suggested that at some stage through the improvements of the models that baseline AGENTS.md had become redundant.

So I built a thing that looks _very_ similar to this a while back: http://pipie.io/agent-tracker (it doesn't orchestrate)

And what's really fascinating isn't that multiple people have built the same thing is just how convergent all the ideas are. This makes a heap of sense given that they are all vibe-coded and using similar libraries. It's just very real when you see it right in front of your face like this.

I think there's a heap of really interesting stuff when you start linking into hooks which can also create tmux splits and really make the agent the center of an ide which seems like this is on the way to.

Don't forget the Paul Kelly song of the same name.

A very cool approach, well done.

There is a great episode of 99 percent invisible about this.

https://99percentinvisible.org/episode/the-weather-machine/

Fair enough, I suppose. I still think the additional complexity of having to bring in the context for the save of passing 1 variable through the whole tree is overkill though.

This is actually a really weird example of using the Context API. I have no idea why you would want to use it to manage a single switch of state.

The far better examples are providing a "theme" across multiple disparate components, and each of them being able to access the colours, or styles. (You could also just use CSS)

The other good example is being able to set the logged in user into a context and then being able to consume the context if you need access to the logged in user.

How does this work in the case where the majority of your customers currently pay by direct-debit/cheque? This is certainly the case for us, but we have long been looking for a affordable solution to have them managed with some sort of managed subscription engine

Beer isn't in 'publicly' accessible vending machines any more as far as I can tell. It is however often available in the foyer of a place that normally sells beer (that might be currently shut.)

Ski resorts are my main source of vending-machine beer. Nothing better than cracking a can of Sapporo Classic in your first gondola ride of the day.

My favourite part of this is the "All systems operational" in green at the top. Yet, all systems are clearly not operational.

No [video] ?

Gee I spent far too much time on Astaria in the late 90s. I'm sure there's a few people around here that are in the same boat.

We've been using this for a while, documentation isn't great, but it seems it's the best library for what it does.

We had particular trouble with double tap recognition early on but I believe V2 improved this substantially.

There is significant friction from changing to anything that isn't Word (PDF/Latex to a lesser extent) in this space. I wonder what it is going to take for that monopoly to be broken

You are right in a sense. I think people are demanding more flexible, realistic and more consumer favourable laws. Rather than the rigid structures that are in currently in place.

Here in Queenstown, NZ there's spa (jacuzzi) as a service.

But my cat's name is quizzical.

Credit cards have little wire antenna in them. If you basically cut it in down near the chip, the chip still works when inserted into the machine but the NFC doesn't work.

I did this accidentally and have been using my phone with chip and pin for about a year.

Personally I'd prefer to swipe.

In a lot of ways it's tricky, but easy at the same time. We end up trying to build strong concepts that can be mapped onto a few different problems within the event. A lot like an online store product, but with a better grounding in events.

We then try and provide the right management/reporting/organising tools so that they can work with it better.

As someone who is working in this space with a reasonably unsexy product, I'm a believer that back-office is where it's all at.

UUDDLRLRBA

These guys live in here Melbourne, cost of living is pretty crazy high. Sure, you could get away with paying yourself less than that, but 60k (less business expenses) puts them in the realm of basic office clerk.

Maybe the startup founder's lot in life is to be poor while they are starting up, so could probably do it with less. But they are hardly overstepping the mark.

I personally think that the Git approach is closer to how I envisaged a (non-distributed) VCS should work. I'm the same as you, coming from SVN it was a godsend.

Checkout the device called a Thermomix. It essentially cooks, prepares, does everything except buy and measure the ingredients.

The article basically compared Nespresso to an unknown, un-sighted, possibly stale, possibly ground month earlier coffee and a coffee that was roasted incorrectly for the brew method and ground days earlier. You wouldn't really call this a good baseline to compare to any data that anyone provides.

One of the major reasons for this is that these chefs get crazy good deals from Nespresso as part of it's marketing, ie, it's in the best restaurants, it's good for you.

In fact, of all the home cooked dishes that is easiest to reproduce with minimal effort/intervention, I'd say roast chook it about the best/easiest/simplest.

I'd suggest people that say they can't cook, try to cook roast chicken from recipe. Make sure to use a timer and you really can't go wrong.

I'm from Australia and I can't understand from the Australian province New Zealand.

Today it went down, just as I needed our CI server to do a pass. Which is fine, grab a coffee, then I sat down and thought, I'll catch up on some code reviews.

Thankfully, it wasn't long till it came back up.