There's also another unusual way - the Caisson lock.
Its design is TERRIFYING.
The boat is floated into a tube that get sealed at both ends and then (in the dark..) that tube is winched down into a completely flooded chamber until it (hopefully) lines up with the egress port at the bottom. The tube with the boat in is unsealed and the boat floats out.
Ooof, I'd never seen that. Thanks! From the wikipedia link:
> The May 1799 test at Oakengates carried a party of investors aboard the vessel, who nearly suffocated before they could be freed.
(!) ...and eventually they built a flight of nineteen locks instead, with a steam-powered pump to return water. The lift locks (and Falkirk Wheel) are a really impressive and elegant solution in comparison.
Oh that is terrifying; interesting, it "was first demonstrated at Oakengates on a now lost section of the Shropshire Canal in England in 1792". That little bit of rural UK was hot and happening from 1700 to 1800 and doing a lot of canal and river transport; it claims some part in the Industrial Revolution. Within 20 miles around Oakengates around that time was:
- early good quality cast iron; Abraham Darby in Coalbrookdale in ~1710 smelting iron from low-sulphur coal/coke for the first time, dominating the market in iron pots and pans.
- his foundry casting iron parts for early Newcomen steam engines in 1715 [2].
- the first iron bridge in the world[3] in 1781, now a town called Ironbridge. John Wilkinson invented a method of boring accurate cylinders for Bolton & Watt static steam engines, a friend wrote to him about the proposed iron bridge and he funded it.
- the first iron boat in 1787 in Brosely; the Trial by the same John Wilkinson, "convincing the unbelievers who were 999 in 1000".[7]
- the first iron framed building in the world, ancestor of skyscrapers. Thomas Telford[5] was a surveyor and engineer in the area, took inspiration from the iron bridge and started making other things out of iron, became friends with a flax mill owner whose mill burned down; they decided an iron framed building would be more fire resistant, and they built the first one ever[6] in 1797.
- very early high-pressure steam engine and high-pressure steam locomotive. Richard Trevithick around 1800; Coalbrookdale foundries built a static high pressure engine and a high pressure locomotive[4] within a couple of years of his Puffing-devil road locomotive and Pen-y-Darren rail locomotive were trialled in other parts of the UK.
Then Regression To The Mean happened and the area faded back into history.
When my son was little, he would say things like “Yes means no and no means yes.” He would also say things like “milk is good, butter is made from milk, cake is made from butter, why can’t I have cake for breakfast?”
Through persistence and speaking to him calmly, he eventually stopped his petulance. Usually if he wanted something, we would only give in after repeated conversations. We wanted to explore decision making with him and ensure he would not quickly want something else. The main thing I wanted was for him to talk and explain why he wanted something so bad.
I believe he only threw a full tantrum a handful of times. When that happened we followed the advice of pretending to leave without him. When he realized we were not rewarding his tantrum, he stopped.
In short, we wanted to reward him for communicating not for throwing a tantrum.
Imagine you woke up, learned that you have your own feelings and ideas and agency, and yet... you don't get to choose except what's between handed to you (the blue pill or the red pill). And you start to realize it keeps happening. Maybe that's what being 2-3 is like? To a toddler it will be eons before they get to make their own choices.
Yes, "no" can be petulant, but it's also could be deeply beautiful and true.
Typically you don't work straight till 23:00, you just might log back on later in the evening (perhaps after putting the kids to bed) to finish up something when you know you'll get quiet time, or to align with colleagues in the AMER or APAC regions etc.
If pushed, I get my developers to give estimates in jumps of ~5x.
Their options are
2 days
2 weeks
2 months
10 months
Then I triple the estimates before sharing with the business.
We don't estimate individual tickets/bugs at all, just overarching projects.
I also ask the business to estimate the commercial/user impact of the projects too, and we track and report the reality against their estimate, to hold a bit of a mirror up to them and as a way of pushing back on doing pointless work. Those estimates we use similar orders of magnitude for - £1k, £10k, £100k, £1m, £10m.
Fermi estimations like these really help avoid protracted negotiations and the lack of precision is a feature that makes clear they are estimated.
Hi. I have wanted something like this for YEARS, but have never had the motivation to hack something together.
A few questions:
1. Is the dev edition hardware different?
2. If not, it possible to upgrade to a dev edition later, ie. Is it just a config thing on the server end?
3. If I have multiple trmnls how do I manage them? Is it possible? Do I need multiple accounts? Do they show the same stuff etc? Is "dev edition" for my account or per-device?
4. Using multiple apps - is it a split screen display, or do it cycle through the apps every x seconds? Is there a button to advance to the next one?
5. What's the resolution in real terms? Ie. Can I get a full month calendar to show and still be able to read entries? How many lines of Todo-list items can I have? What happens to over-flowed items?
6. how does it get updates? does it connect to my phone via Bluetooth or to my WiFi? Can it store multiple WiFi networks, for if I want to take it places?
1/2. hardware is the same, just a permissions switch. you can upgrade any time in-app.
3. one account can manage them all, there is a device switcher in top corner that makes it easy to jump between playlists, content orderings, preferences etc. you can also “mirror” a device like child<>parent but they are independent by default. dev edition currently device specific but if you say “hey not cool” we can bump both your devices on the same account. ;)
4. yes and yes and yes. you can choose from several layouts (full screen, split, 3-way split etc) and you configure refresh intervals per device, per plugin, per time of day. so maybe you want calendar only from 8-9a, or reddit / hn only in the evening. there is a skip btn on the device which can also be double-clicked to do other stuff (go backwards, email me this, etc).
5. res is 800x480. not amazing but we make it work. built our own design system with special fonts. preview: https://usetrmnl.com/framework. yes we have calendar in Month view and it looks fine IMO. you can fit in /read a lot of text. for overflow we have some JS magic that auto truncates and you can control these params as well. see “Overflow” section in Framework docs above.
6. connects via wifi, yes supports multiple SSID, and receives OTA updates automatically (which you can disable). firmware is open source as well.
As someone who has worked in ecommerce for decades, Shopify is fantastic.
It's not the cheapest, nor is it the most expensive. It's not as powerful as some systems, but it's not weak. It's not the easiest system to work with, but it's also not the hardest.
What it is is right in the goldilocks zone, and it allows businesses to DO BUSINESS, not end up having to worry about or even think about many decisions.
Day-to-day I work across 4 ecommerce platforms and Shopify is the one that doesn't keep anyone awake at night and "just works". Sure there's a ton more stuff some of the other platforms we use can do, but we also have a LOT more meetings, dev tickets and headaches with those platforms.
For like 80%+ of 0 to $50m+ online businesses it is by far the best choice because it means the team can focus on connecting with potential customers and selling stuff and not have to allocate nearly as much time or headspace to the Storefront system.
Fundamentally, you can't use the same data to both generate and validate/disprove a hypothesis.
Srgmenting and data dredging is fine provided you run a new test with fresh data to validate if there is a causal relationship in any correlations found.
Its design is TERRIFYING.
The boat is floated into a tube that get sealed at both ends and then (in the dark..) that tube is winched down into a completely flooded chamber until it (hopefully) lines up with the egress port at the bottom. The tube with the boat in is unsealed and the boat floats out.
https://en.wikipedia.org/wiki/Caisson_lock