451 karma · joined October 9, 2014
I don’t know what I’d do if I could just YouTube any topic and get a meaningful answer 30 years ago, it could be incredible? Would have made things faster but maybe that’s not the point? I’ll find out I guess with my son, it will be interesting.
The architects -> engineering -> builder handoff is obviously the most lossy, tons of context/intent/purpose is lost in these steps, and normal way incentives align doesn't help with each group being sympathetic to the greater mission, the more they care or clarify etc the more time things take / cost incurred. It is natural to assume everyone is thinking the same as you and will be motivated because you are paying them, but they rarely are, they care less about the result than you do so staying on top of the details you care about throughout the process is a must.
What worked great for us was to have the builder part of the architecture design process and inject their learnings of how to actually build the thing along the way, rather than trying to bolt it on at the end. This isn't normally the way things work as normally architectural drawings are a primary input to a tender process to find a builder.. so is a bit cart before horse but we already had a builder so could avoid that.
They would want to be confident there are no more bugs, only a few days ago this happened, did they do a full audit of things before tipping it in? Imagine if they lost another 320m !
Real value for me would be to integrate it with containerd or similar to speed up image layer pull times, I imagine that isn’t shelling out to a separate binary tho.
What language is it implemented in?
Hard to change the entire container ecosystem away from tarballs tho so this is still useful. Is it available anywhere? I didn’t see a link?
Buy and use an EV for all the easy daily stuff, then rent something more suitable for the yearly/less frequent long trip. Other than range we have a similar problem with space, for big trips we end up with tons of stuff and more space is useful but day to day less so. So the 90% EV could be smaller as well and still solve the problem.
I do see the attraction of having one thing that solves 100% of the uses though.
Nope, bookies only want to keep profitable customers, or provide some other upside to them. In the context of bookies they have limited other ways to make money but sometimes their are weird edges that pop-up, like legislated restrictions.
In Australia those running the licensed tote (totaliser) market pools on horse racing can't make the market themselves, they can't legally seed a pool, and since a tote win is a portion of the pool total customers are less inclined to bet on a low value pool, so the markets allow a few high value bettors to seed the pool for them (with generous rakebacks) which they make a net loss on, but has overall positive effect on their business.
Seems like eventually this should become a priority for library writers to support dead code analysis, otherwise going to get worse and worse..
I played with this when first announced, and then now and all the things I wanted when i first tried it out are now fixed (mainly transparent networking..) and the option for dockerd container engine makes migrating pretty simple.
The MBA thinking ignoring intangibles is exactly the problem, trading short term win for long term loss. Will it actually matter in the end? Probably not and the cycle will continue..
I’m a big believer in manual simple sql migrations via flyway or similar, but if you got this working in theory and built the features it could do a better job on average than non expert humans, it could enforce patterns / naming / conventions / indexes etc. Could do with sql migrations too but would be more difficult as it wouldn’t have the full declared model.
Does seem like there is a growing movement to explicitly not do leetcode style reviews at many places which is good.
i guess the core of the statement was that the net cost to the db is more tied to offset than select, yes they interact and 'select * with offset' is more expensive than 'select foo with offset', but its really the offset that is the problem. If you did keyset style pagination and still did 'select *' you'd be fine and roughly the same cost as 'select foo'.