223 karma · joined August 20, 2007
I'm only on day three with a moonlander but it hasn't been that bad so far. I'm up to 60wpm now so I'm past the part where I felt unproductive. I've settled a bit more into a layout I'm happy with today too.
250,000 customers is approximately $300m a year.
250,000 * 100 dollars a month (approx - maybe less now) * 12
There isn't really a best seed. There are simply tradeoffs. That probably sounds familiar :-)
Disease resistance, water tolerance, soil conditions, climate, daylight, tolerance to heat and cold, pest resistance, taste, yield, time to grow, harvest period, storage period.
There are usually an incredible number of varieties for any given plant. It takes quite a few years to start to find ones that work the best for you. It's also doubly tricky as your conditions will change each year.
I like to plant a wide variety of seeds as that makes it likely that something delicious will thrive.
I'd also say that typically home grown fresh vegetables are so much tastier than ship bought that you might worry less about iothan you think.
Last week I wrote a blog post (https://blog.atomist.com/comparing-docker-base-image-layers-...) telling the story of how a container scanning feature came together and started to show us some interesting data about our vulnerabilities. We've just pushed it live (into Beta!) and I'd love to hear some feedback from people able to test it out by scanning of their container registry.
You need a GitHub account to sign in and we support Docker Hub, Elastic Container Registry, Google Container Registry and Github Container Registry.
Let me know if you have any comments or suggestions. We've had loads of fun exploring our vulnerability data and managed to patch up some issues!
I'm an engineer working at Atomist and a very long time HN reader, if a bit of a lurker!
https://adit.co.uk/sliderulev2.html
One thing that struck me was that it does require a good instinct for the magnitude of numbers to use. Lots of fun though and surprisingly quick to use.
In the UK rear facing is a legal requirement up to 15 months - I think that's being extended to older kids soon. We used rear facing until about 3.5 for our eldest. At that point we got her a new forward facing one and gave that one to our youngest.
Two child seats basically means no one can fit in the middle unless you have an extra wide car. Some of the compact but bigger cars seem to be incredibly popular with parents around here.
I can't say we ever had an argument about front versus rear facing - that was just the direction the seat was in. They didn't even know there was another option! I can see how it might be difficult if you tried to change a seat a kid was already used to though. That said, pretty much everyone here uses ISOFIX bases with the extension bars so maybe we do have more room (as per the article). I'd recommend them either was as being able to clip the seats in and out is fantastic if you have a sleeping baby.
> In the United States, the average diaper sells for about 25 cents
That's so much more expensive than here. Looking at the pictures you can get the same brands and nappies for half the price here.
In the decent sized packs from amazon pampers are only a touch more expensive but yeah the Lidl ones are just as good as far as I can see. We mostly used pampers because they are cheap with a subscription but have used Lidl ones fairly often. Shame we're not very close to a Lidl store (well we are, but traffic).
Oak wooden frame is sometimes (can be expensive) used but the wooden cladding approach is very rare. That said prefab panels which combine stud work insulation etc are sometimes used. Not particularly commonly but they are quite new. I'd have made pre-fab panels for my workshop but I ended up using brick as the fire rating made building control regulations easier to pass. It took me a long time to lay all the bricks though so I may have made the wrong decision!
For starters radiotherapy is often used to control symptoms. It may not do anything for length of life but targeting key tumours can keep you mobile for longer, reduce the risk of seizures etc. It can be a boon to quality of life.
There will also almost certainly be other things that occur along the way that require visits to hospital. That is complications that could kill you but can be treated without too much discomfort where you can get back onto your feet. Infections are incredibly common for example. Particularly if you're on steroids.
Obviously you'll rule some things out, e.g. chemo as not worth the cost during palliative care.
My rule is that a desert that's home made - by me, my wife or whoever is allowed. It seems to work. If I really want to eat something sweet then I have to cook it first. It's the instant availability of sugary food from shops that get you.
Secondly - it gets much easier with time. Whether it's habit or a change in your gut biome or both: the sugary cravings do get less.
Thirdly - try and get enough sleep. I think most people crave sugar when they are tired. I find this one the hardest at the moment. Sometimes life can be like that.
Struggled to start with, sure. But ultimately for me those are the best parts. Immutability particularly. It takes a few weeks learn how to solve problems again but I do think it makes things simpler and removes a nice category of bugs.
Actually maybe Java interop was the best part. Without that I doubt we could have picked up Clojure. It's far less true today but this was almost 6 years ago. Back then knowing there would be a library, even if we had to quickly wrap it was essential.
They struggled with functional programming and immutability. At least to start with. I actually found it amazing how easily people moved over and how enjoyable they found it. Out of 30 people only one didn't take to Clojure. He moved to a C# team for a while but eventually decided to rejoin and pick Clojure back up.
Obviously everyone is different but this was quite a good sample.
We're imagining the idea that your whole development flow is expressible in terms of trees and expressions that we can use to navigate those trees. Say for example a webhook pushes a commit event. We can navigate from that commit, into the chat channel associated with it. Find the repo that contains it. Associate it with the build and link the two together in chat or, most relevant to this article, navigate into the code itself and perform an action such as changing the code or opening a PR with a suggested edit and comment.
The interesting thing is that it's trees the whole way down. We can use the same expression to reach across all all kinds of events or to pick out individual tokens or structures inside the code.
There's lots of information on our blog: https://the-composition.com/
We've open sourced a lot of our core work at: https://github.com/atomist and are also interested in talking to teams about joining out alpha (see atomist.com)
It's a really interesting problem to be working on.