It's a macOS app and I've found it great. However if given an ASCII diagram, you cannot edit it with the same ease as creating a new one (e.g. reflowing text or resizing boxes).
I really like the idea of having the mermaid source and the ASCII diagram together, so you could use the source to change the diagram if needed. But I feel that would feel cluttered to have both in a plain text file or comment, where ASCII diagrams shine.
> [Elon Musk] also said he would ask any executive who retained more than three workers who “don’t obviously pass the excellent, necessary and trustworthy test” to resign.
Is this "excellent, necessary and trustworthy test" referring to some specific criteria at Tesla or is it judged at an executives discretion?
The bridge is assembled over 2 nights at a motorway exit (so traffic can bypass it by driving off and immediately back on to the road). During night 1 the two end ramps are assembled and attached together to make a short bridge. During night 2 the ramps are driven apart, the central section is built to reach the full length and the entire structure is driven to the final location.
The entire length is 236 meters long providing a working length of 100 meters underneath. The assembled bridge can flex slightly at the joins between sections, and has a turning radius of 2 kilometers.
The whole Marti youtube channel is a marvel for engineering geeks like me. If you have the occasion, you should take a look (talks about tunneling, big machines, etc)
They use a tunnel boring machine to bore a tunnel with a 45° slope.
They do go into the mechanics of how they make this insanely massive machine drive up a grade that steep, and how they ensure it doesn't slide backward.
I was glued to the screen more than with most movies.
If you like channels like Practical Engineering, you will enjoy this.
The boring company isn't move fast and break things. They literally just bought a drill and use it like any other construction company. There's no innovation at all.
They started that way, just buying a drill, but are now trying to innovate and build their own one. They are just starting using Prufrock-3. The Prufrocks are machines the Boring company have made themselves. They say "Prufrock's medium-term goal is to exceed 1/10 of human walking speed, which is 7 miles per day." which is way faster than anyone else. The Swiss machine in the video did 400m in 4 months. They are also experimenting with evacuated tunnels (https://youtu.be/nV07jqwCy0A?t=879) which may not go anywhere but is at least an attempt at innovation.
"7 miles per day" is all talk and no proof it can actually be done. The Swiss dig a lot of holes from easy to very complex terrain. If there was an easy way go that much faster they would.
There was a derailment of a cargo train the the Gotthard base tunnel last year [1]. It caused a huge amount of damage and one tunnel will be close until September this year. They need to replace 7km of track. If there way anyone to do this correctly faster they would as it is costing millions not having this route open. Concrete needs time to cure etc. some things you can't just make faster because someone said so.
It’s incredible how defensive people get around others’ ambitious goals.
Every Elon company sets super high goal targets. They are often completely unrealistic with current technology but it inspires certain types of people to innovate and it works quite well.
> The Swiss dig a lot of holes from easy to very complex terrain. If there was an easy way go that much faster they would.
Nobody said anything about “easy”. Also, The argument of “the established players don’t work on X so X isn’t possible” doesn’t work.
If the Swiss are happy with their industry the industry isn’t going to risk really capital intense experimentation to do better. See: Innovator’s dilemma
> The Swiss machine in the
> video did 400m in 4 months.
No, a lot of the time the machine was stationary because the needed to manually reinforce what they were about to drill through, so the machine wouldn't get trapped and buried in gravel. Wouldn't Prufrock-3 be similarly slowed down!
In addition to that I assume that the 7 miles a day claim assumes 24/7 drilling, whereas I wouldn't be surprised if the swiss were doing 8/5 drilling.
Nobody said “break things”. Making one specific thing reliably, quickly and cheap is a completely different approach to the “move fast and break things” approach.
Fast. Fast always wins. Trying something, regardless of outcome teaches something about the world. The more trials, the more you roll the dice, the more you learn.
I really hate being wrong, but it is much better to be wrong a lot, and quickly understand why. The alternative is to try nothing. It’s kinda sad.
Fast wins for something like mobile apps but not infrastructure where safety matters and you can’t just shrug off liability. The Boring Company is a great example: fast to market themselves but almost all of their projects have fallen through.
Which nascent technologies have became common, dominant by innovators unilaterally adhering to the precautionary principle?
The cliché "Worse is better" describes this (turrible) phenomenon. (The flip side being "safety regulations are written in blood.")
I really wish this wasn't the world we live in. I want to live in a world with consequences (and justice). I've been railing against it my whole career. And judging from my meager savings, failing in my efforts.
Iteration always wins. There may be other constraining factors, but if you can violate those to iterate more (i.e. cheat), you’ll beat your competitors who honor those constraints.
This has nothing to do with the success or failure of any given company.
You seem to have misunderstood what I’m saying. Iteration is how you learn. Learning through iteration, which is known under various names like Wright’s law or more generally experience curve effects [1], goes hand in hand with economies of scale in driving down costs.
Yes, iteration requires you to survive. Not sure how that’s relevant. Cutting corners also isn’t necessarily a bad thing - you’re focusing on the extreme example where people die. Cutting corners can also be a careful evaluation of what processes are and aren’t relevant to a given situation but that becomes trickier when it’s enshrined in law. Imagine if guidelines from the 80s about how to write software were enshrined in law.
Regulations more often than not do ignore the flip side in terms of the cost of compliance because it’s difficult to show the counter factual universe in which a regulation may save 10% more lives (or maybe even 0% more lives) but drove up costs by 100x.
> A number of these phenomena have been bundled under the name "Software Engineering". As economics is known as "The Miserable Science", software engineering should be known as "The Doomed Discipline", doomed because it cannot even approach its goal since its goal is self-contradictory. Software engineering, of course, presents itself as another worthy cause, but that is eyewash: if you carefully read its literature and analyse what its devotees actually do, you will discover that software engineering has accepted as its charter "How to program if you cannot.".
It does depend on the domain though. Sometimes moving slowly and carefully can result in a faster successful outcome than throwing shit at a wall and seeing what sticks.
> The more trials, the more you roll the dice, the more you learn.
If you have infinite dice rolls this is obviously true. If every dice roll costs you something or indeed everything... heh. Maybe don't just roll it to see what happens?
Yes, sure fast wins when building a bridge. Or a tunnel. Which then collapses. Safe wins, this is not Facebook where people share some holiday pictures.
"but it is much better to be wrong a lot"
I disagree, "Oh the bridge collapesed, I was wrong! But this is much better than being right" - Nope.
... which has its own reasons, namely regulations (you know, every time there was a new disaster they added another one) or maybe some corruption. You don't see bridges falling in US regularly killing tons of folks, do you.
I am not saying its ideal and there is no room for improvement, nothing in real world is, but please consider other, 'fast' scenarios for long term (100+ years) existence when not only many lives are at stake.
> You don't see bridges falling in US regularly killing tons of folks, do you.
Falling yes. Killing is hit-or miss. I would be surprised if the reasons bridges are failing due to lack of maintenance is entirely unrelated to the cost of building.
There are many ways things could be better, and many ways things could be worse.
Attacking something only because it's cheaper and faster seems silly.
Please share a single recent example from US, I am only aware of one relatively recent catastrophic case from northern Italy, where maintenance was subpar.
Cheaper reflects many things, overall quality testing, attention to detail, how much effort went into design etc. Its not a silver bullet but oh boy does it always show on result, without exception.
I was more impressed by the OP seemingly from Swiss public body. The Marti one in GP is exactly the sort of sales demo type video I'd expect 'for a contracting company', though with lashings of high speed chase or shooting narrated video (you know, the 40% ads, 50% rehashing what we've seen or telling us what's to come, 10% content variety) for some reason.
Because there are American (or Canadian, British, etc) companies that do what's necessary for American Civil Engineering.
When it is worth it, American public works entities do reach out to German (and other national) companies. As to issues like this specifically? Because the US generally has wider freeways/highways, so is less impacted by single/double lane shutdowns for surfacing. In addition, many states have opted for less long-lasting quick pack asphalt for surface streets which can be resurfaced in place and ready to drive on again in a few hours.
I know it's Internet rhetoric to assume America and it's government are incompetent, but the Civil Corps of Engineers, CalTrans, etc are actually pretty good at their jobs. The biggest horror stories are jobs given to private entities that go overbudget and overtime.
One factor you’ll see in many areas of government is the second order cost of eliminating civil service positions. It’s most common to talk about how contractors usually end up costing more and being less efficient due to additional overhead and conflicts of interest, but there’s a deeper problem that the government doesn’t have a staff of people with the knowledge and experience to select and manage contractors. That’s how you end up in situations where none of the alternatives are better than eating the cost of a bad plan or accepting a lower project lifetime, and because it’s a managerial failure the blame is often spread between three or more organizations and often has no effective accountability.
Well, for the California example, CalTrans is the govt. They're well staffed and don't (generally, it may occur occasionally) rely on contractors for their work. I believe the same goes for CDOT and other agencies, though many of them are more willing to contract out as they don't necessarily prioritize roadwork like Californians do (for obvious reasons).
Generally, it's particularly rare (at least in the Western "blue" States) to rely on mostly or, especially, exclusively private public works programs.
Wait so all this lets them pave a 100 meters a week (assemble bridge on one weekend, pave on Monday, then disassemble the bridge the next weekend after the asphalt has dried)? That seems horribly slow and expensive.
100m at 1 lane is around 430SY. That's probably 2hrs of milling and an hour of tacking and paving, with maybe another hour or so for incidentals. So you may only get half a workday of production. For time consuming repairs, like full-depth replacement, the setup time cost may not be significant.
Keep in mind, though, you don't lose a lane of traffic. There is no need to truck in jersey barriers. You don't have to build an entire temporary detour road. You don't pay a consultant $200/hr to design a traffic control plan.
I think the real value is safety. The crew is shielded by the bridge and you have complete grade separation from traffic. That's a lot better than an orange barrel being the only thing between you and a minivan.
oh this is cool.
I did think for a 2 day setup and 1/2 day takedown it wasn't a huge efficiency saving but it is if you move it down the road at the same time.
As the comment above mentions, safety is a huge factor too.
During the night, there will be 1 lane open in each direction (one on the side of the bridge, and one on the opposite carriageway), so the bridge can be moved.
I guess it's theoretically possible to engineer a bridge that can move with traffic on it.
But this bridge is engineered with solid feet for taking traffic loads. The wheels are only extended for movement and wouldn't be able to take the load of traffic.
Having to stop traffic, and then redirect it into the one emergency lane, every time 100m is finished in order to advance seems like a huge disadvantage.
If the road is anywhere close to max capacity this will cause traffic jams either way.
But usually roads aren't even close to max capacity at night, when the shifting happens – which, I imagine, is much less stressful and time-critical than doing the whole resurfacing in a single night.
It would be awesome if the the entire bridge could slowly move as one while traffic keeps flowing over it. That would require far more and far bulkier wheels than the current ones designed to carry only one support segment. That will have to remain the stuff of fantasies...
The bridge could temporarily lift just the 2 ends and traffic could continue slowly under the bridge while the bridge moves ahead. However, it needs to also raise its height for trucks to pass under or alternatively, trucks could be temporarily suspended/rerouted from the road while the bridge moves.
Sure, but that can happen at night with minimal disruption to traffic as it takes only the time to move it, not the time to disassemble, move, and re-assemble.
Possibly, but unlikely IMHO - it looks like the bridge deploys rigid hydraulic outriggers when stationary, and changes to flexible pneumatic tyres when moving.
If the bridge was supported by flexible rubber tyres while heavy trucks were driving over the top of it, it'd probably wobble enough to make everyone involved uncomfortable.
I don’t think ragebol meant that the bridge rolls forward with traffic on it. Just that once a 100m long stretch is finished they can roll the bridge 100m forward with the traffic re-routed or suspended during the repositiong. If they time it right the resurfacing can be done with minimal disruption in the dead of night.
Half right. At night, they direct all traffic onto the shoulder / emergency lane and roll the bridge forward 100m with no traffic going over it at the time. By day, the bridge is stationary, traffic goes over it, and work goes on underneath.
It's a macOS app and I've found it great. However if given an ASCII diagram, you cannot edit it with the same ease as creating a new one (e.g. reflowing text or resizing boxes).
I really like the idea of having the mermaid source and the ASCII diagram together, so you could use the source to change the diagram if needed. But I feel that would feel cluttered to have both in a plain text file or comment, where ASCII diagrams shine.
reply