Hacker Newsnew | past | comments | ask | show | jobs | submit | more BiteCode_dev's commentslogin

We have roundabouts everywhere in France, but in the US, they seem not very popular.

They do removes the need for traffic lights, make priority checking a non issue and avoid left turns among other benefits. Although they prevent you from going to fast locally, they tend to make traffic more fluid on average.

Why are they not used that much in the US ?


They have started to appear in Austin, Texas, where I live, but only in the last 10 years. There are many more places they could be added, but I think when two country roads meet you just make a plain "+" intersection, and as it gets gradually more urban it just never gets rethought as to whether it should be turned into a roundabout. But it is (where I live at least) slowly starting to get adopted.


There's roundabouts where I live in the USA with stop signs. People didn't know who has right of way and it led to road rage confrontations so the government had to add stop signs to them. People in the area now complain that roundabouts suck. Which they do when you have to stop before entering. So now we get more four way stop signs and traffic lights instead which cause traffic to stop and start, wasting fuel and increasing congestion. Sigh.

On the other hand at least you can turn right on red which is something my home country needs to allow by default since I haven't once seen an issue with it in my years in the USA.


> On the other hand at least you can turn right on red which is something my home country needs to allow by default since I haven't once seen an issue with it in my years in the USA.

> Right-Turn-on-Red (RTOR), in its “Western” version allows motorists to turn right on a red signal after stopping and yielding, unless specifically prohibited by a sign. The objective of this study was to determine the effect of Western RTOR on pedestrian and bicycle accidents in selected jurisdictions adopting the rule in the mid-1970s. The results showed significant increases in pedestrian and bicyclist accidents involving right-turning vehicles at signalized locations following the introduction of Western RTOR. These increases were: 40 % for pedestrians and 82 % for bicycles in New York State; 107 % for pedestrians and 72 % for bicycles in Wisconsin; 57 % for pedestrians and 80 % for bicycles in Ohio; and 82 % for pedestrians in New Orleans. Analysis of police accident reports suggested that drivers stopped for a red light are looking left for a gap in traffic and do not see pedestrians and bicyclists coming from their right. Countermeasure research and development was recommended to deal with this well defined problem which involves between 1 % and 3 % of all pedestrian and bicycle accidents.

https://www.sciencedirect.com/science/article/abs/pii/002243...


> People didn't know who has right of way and it led to road rage confrontations so the government had to add stop signs to them.

“Yield to traffic in circle" clarifies things just as well, is commonly used, and restates the actual right-of-way rule applicable to an otherwise-uncontrolled roundabout. An amateur generalist politician like most city councilors and mayors I can see thinking stop signs are the answers, but presumably they had a roads department with at least one professional to consult, so one hopes that there was more at issue than people not knowing the rules if they chose stop signs.


You have roundabouts in the middle of Paris in areas with lots of pedestrians? Please show me. Certainly not any parts where anybody would think, hey, this is a great bit of infrastructure for people traveling on foot.... Roundabouts may be great for vehicular traffic, and yes, I believe they should be far more widely used in the US, but not in dense urban areas where pedestrian safety is meant to be a priority.


Yes, we do.

Even if paris is probably the city with the least roundabout because it's the oldest, you can use google map and zoom to see the little circles:

https://0bin.net/paste/xL8ni-vJ#Sv-WUYiKnM2WuRDTCBX0iHfLCWDm...

We even have to giants ones on Nation, Arc de Triomphe, etc. The later is actually dangerous, since priority is reversed, and the cars entering the roundabout should be given way.


I've driven in places that use them regularly; I've never felt comfortable: Trying to change lanes and turn, while going around a curve, with traffic behind and in front of me going around curves (reducing visibility and judgment about position and speed), and also reguarly changing lanes and entering/exiting.

Are you comfortable with it? How do you do it? (Empty roundabouts are fine, of course.)


We are train to do it when passing the driving licence, so it's second nature. In fact, I can do it without thinking, which I can't do with a crossing: too many variables.

The hard part is the signaling (it has very specific rules), and you can see that the older drivers don't use their blinkers properly because they have never been taught to do so.

However, it can becomes dangerous if it's overused.

E.G: Nantes is a city famous for chaining roundabouts, to the point they sometimes have double-roundabouts, which are awkward even after years driving around them. I hate those with a passion.


>E.G: Nantes is a city famous for chaining roundabouts, to the point they sometimes have double-roundabouts, which are awkward even after years driving around them. I hate those with a passion.

Get on Swindon's level:

https://en.wikipedia.org/wiki/Magic_Roundabout_(Swindon)


> We are train to do it when passing the driving licence, so it's second nature.

> The hard part is the signaling (it has very specific rules)

That is a revelation! I never had that training or even knew it existed, and roundabouts are occasionally deployed where I live without implementing any training. The training seems an essential component?

Any suggestions on where this training might be found (in English)?


> That is a revelation! I never had that training or even knew it existed, and roundabouts are occasionally deployed where I live without implementing any training. The training seems an essential component?

Like for any part of driving a car, training is important for 2 reasons:

- you don't have to think when you are approaching a roundabount. You know where to look, you know what speed (and gear if applicable) you need, you know where lane to go and what signal to use. Since it's a situation with a lot of information, it makes your decision process relaxed and accurate.

- socially, if most drivers are trained, they will behaved consistently, and hence, produce a stress and surprise free experience, but also letting you identify easy the drivers you need to watch out for.

> Any suggestions on where this training might be found (in English)?

I have no idea, it's part of all french drivers training automatically, anywhere you go.


It’s really rather easy. The UK had lots of roundabouts so you’ll find lots of English language media. Here’s one https://youtu.be/koK_a4KYs-E

It’s all very common sense so you should be able to switch the directions around pretty easily.


Unpopular locally. The Seattle area has quite a few and people adapted pretty well to it, but the few in SF are stop-sign controlled as well, which makes them prettification projects.


If you are caught one time out of 10, this is still profitable and those people, being professional risk manager, will take the chance. Not to mention they can then invest the benefits in a difference venue, and make money from that, which will not be part of the fine.

Jail time however, is not something everyone will want to gamble on.

So, it should be what you said + jail.


As a Linux user for now 20 years, I think the author is under some kind of delusion that windows doesn't provide enough value to exist on its own.

I thus assume the autor must be very young, and has little experience with the reality of the corporate world, which loves:

- compatibility

- inertia

- deployment automation

- technical support

- strong legal support (compliance, contracts, DOD approval...)

- social proof (reputation, certification, etc)

- have a big player that can be held responsible

- predictability

Apple is not interested in it, Red Hat is not big enough, Google has desmontrated its incapability to do it, and so on. But MS provides all that, and better than any Unix shop in town.

It would be economically ridiculous to turn Windows into Linux and lose all that stuff.

Merging the two could happen if they manage to keep all their pieces of the pie, and I assume WSL is a first step in that direction.

Or maybe it's the embrace stage, I don't know.


Well, they are going to be disapointed when they'll realize we haven't even figured out the catalog yet.

Software is half a century old, we are still using flint to produce it. The only reason it looks fancy is because it makes more sparks, and a lot faster.


We're just starting to get out of the alchemy stage right now. Wise men and magicians everywhere telling royalty that if they only pay them treasures that they will reveal the future and show them miracles. Meanwhile it turns out that NSS has a straight-forward vulnerability that everyone just somehow missed.

If you look at the history of chemistry, mechanical engineering, or astronomy then you kind of get the impression that we're probably 150-300 years away from software development working the way everyone already imagines it working.


I swear my lord, this Python oil will do miracles with your data ailments.


Lord: I doth smeared mine data with thine Python and lo, it persists in having holes and errors even unto duplicates. Guards! Execute this man!


You remind me of a quote I heard at a conference (paraphrased badly).

The Data Revolution is like going from the bronze age to the iron age.

It will get industrialized eventually, but that time frame will take much longer and will look completely different from what you expect.


I believe we miss solid common ontology - an agreement what individual pieces of data mean. Then individual pieces of software are either incompatible or inconsistent and must be constantly built anew, resulting in all kinds of bugs.


Heck, chemistry is practically a baby compared to the 1,000+ years of engineering


> If you look at the history of chemistry, mechanical engineering, or astronomy then you kind of get the impression that we're probably 150-300 years away from software development working the way everyone already imagines it working.

If it is to happen, a serious plateauing of "progress" will need to happen all the way up the layers of the tech stack to the point where app developers or data engineers are now working with tools stable enough that previous generations would at least recognise let alone even be able to work with.

Engineering maturity "nirvana" for software will happen not by us getting more experienced/better at it, but by "progress" stalling in all the tools we use.

Software changes a lot basically because it is easy to change. And because we as an industry value constant work towards making it even easier to keep changing - eg cloud, containers, devops, agile etc etc

In the physical world, things have stabilised and reached a kind of local optimum across the vast majority of areas. Sure there are still incremental improvements happening, and occasional revolutionary improvements in different areas. Mostly the main bits being radically changed are the bits that coincidentally touch computers downstream from the constant churn happening to software.

Also another factor is when I think of physical engineering (and I used to work in civil/structural engineering in the 90s), for nearly all work going on, the scale of the problems being solved hasn't changed. Most building sites are the same size they were, most materials are the same, some regulations have changed, but ubiquitous CAD tools etc seems to be the major change.

So maybe, when we can't make transistors smaller, and we can't make cpus faster, and can't increase memory or storage things will slow down. eg as each layer up the stack plateaus, each layer above it eventually changes from working on new capabilities to making what it already does more efficient, that will eventually (it will take a while) bubble all the way up. Progress slows down a lot and us end developers and engineers are working on a stable set of tools very much in a local (or even global) optimum. Also maybe when/if the worlds population stabilises (in decades/centuries/whenever), that might lead to an eventual limit on how much user data can be mined from people and the scale of the data we deal with might stabilise too even beyond the limit reached where we've stopped collecting more because of capacity limits talked about above.

Heh, I started off trying to disagree with your quoted statement by saying I don't think it would ever stabilise like other disciplines. But by laying out one way it could happen, I think I may have ended up agreeing with you :)


Hard sell, but a laptop with a reversible 2-1 screen, one side OLED, and one e-ink, would probably be a winner.

Or something like the framework laptop, but with a plugable/ unplaggable screen, and you switch as needed.

I would buy one. Espacially on travel, where the prospect of working outside in nature, and having a one week battery life would be fantastic for work.


> a laptop with a reversible 2-1 screen

The Lenovo ThinkBook Plus has an E-Ink display on the outer side - but I think it remains an outer side.


Yes, that's the deal breaker. If I can't type with the keyboard, or if I have to add some additional keyboard for mobility, it gets very cluncky.


At the same time, there have been so many convertible tablet/laptop systems that either have the pivot at the bottom center of the screen or less commonly a screen that turns over between two arms on the sides that it's hard to believe someone couldn't do the same with a two-sided screen enclosure.


Not in MY garden you don't, you little photosyntard!

smack a leaf with the back of my hand


Training remotely is not like a remote work meeting or peer coding. It's terrible IMO.

Half of my money, I make with dev, the other half, with training teams.

Since Covid, most training are requested to be remote, even now that I can travel again. Companies have tasted the flavor of trip expense savings, and see only the numbers.

But as a teacher, I can tell you those trainings are a far cry from the in-person one.

For once, engagement plumets, people are easily distracted, doing something else, etc. They ask you to repeat more often, and network/sound problems plus the indirection you get to communicate kill the rythme of the training.

The whole communication is harder. You can't use humour as much, because it's way risker if you can't feel the room. You can't pass behind them to check on what they are doing, so you have to pull feedback constantly, which people are poor at giving. Sharing screen expose the most shy participants, and you can't read facial expression since most don't turn the webcam on, so you can't really know how they feel.

I'd say they learn half less, in the same amount of time. It will probably also stick less. And they also clearly enjoy it less, in general.

At first you'd think it's better for introverts, but if you have a good teacher, it's way better for an introvert to have a benevolent warm person calmy and discretly comes by your side to give you a hint than to have to share your mistakes on screen in front of everybody after being called out in the mic.

Twice already I had people this year, almost giving up mid way. Took me all my compassion and kindness to cross the virtual barrier and reassure them. It never happened to me in 10 years. They felt too much pressure, they felt they slowed people down, they felt exposed, they feld they couldn't find a solution and that I couldn't really help them because of the distance between us.

I'm getting good at remote training, and the sessions are running mostly smoothly.

But I still hate it. Such a waste of human potential.

You can do more training though, so I guess we trade quality for quantity.

Today I'm training people in Africa, from Europe. The connexion is aweful, participants are being asked by colleagues to interrupt their training to solve work issues, and MS Teams has been a train wreck. Thank God they are good coders, and they exercices are quick to check, because they are 7 of them, and they each need to share their screen with their own particular bug.

So sure, it's better to be able to train them at all than not to, given that their company would probably not pay me to fly there (I would have come, I worked a lot in Africa).

But damn, it's low quality.


What do you think would make the remote training experience better? It sounds like one on one conversation as part of the training rather than needing to talk to the whole group. That can be accomplished through chat, but it could be people don’t use that when others are verbally communicating.


First, you need excellent network and hardware conditions, which you can control on your side, but not on their.

Of course, better software to worktogether, but that's a given. Bugs, misconfiguration, latency and ergonomics add up a lot.

But I think until you get a fantastic VR experience, it will still be subpart.

The human aspect of the training is hugely important, otherwise, a trainer has no added value over a youtube video. In fact, the video would be better, since you can pause.


It's a good disclosure, so I don't want to remove the merit out of it.

But it also shows they have the capacity to target and remove accounts when they need to, but they let bots run rampant.

Last week I quoted HN on twitter, and the article name contained something about a pirated instagram account.

In under a minute, I received a dozen answers to that tweet, phishing attempts by bots pretenting they could help me with what they thougth was me, loosing my insta account.

So twitter can easily find them: setup a honeypot, wait for bots to show up, ban them to oblivion.

Since the service is now playing a game where you need to provide your phone number to create an account (they say they don't, but practically, they do), it's quite pricey to create bots nowaday.

They could destroy thousands of bots in a week.

They don't.


It's the same thing the Match Group does with their dating apps. They leave the bots up to drive traffic, and keep real users engaged.

Then they clear out the bots after letting them run for a bit. You see 20 matches, likes, etc. The moment you pull out your credit card, to "see" your matches you'll find most of them are from bots/ deleted accounts.

It's against Twitter's profit motives to clamp down on bots in any meaningful way. Ultimately, these bots do simulate traffic, and when you get your endorphin rush from getting your bot retweets, Wells Fargo or whoever else is advertising on, Twitter gets to monetize you.


Alternate interpretation assuming incompetence instead of malice: they _do_ ban thousands of bots a week, but their security staff isn’t aware of this particular attack vector and so they haven’t banned these particular ones (or the attackers have some way of evading analysis, honeypots, …).


Every casual twitter user jokes about it, so the "they dont know about it" is a claim that would require a lot of evidence - they've taken action against the "elon musk" twitter bots, but the same scam is effected constantly.

After years of incompetence you can start to assume incompetence.


It's simply not a priority for them.


This is the right answer.

It's never that they can't do it, they just don't care enough to do it.


They won't care until liability is attached to it which will make their entire business model of profiting off "engagement" at the expense of others unviable.


The obvious answer why Twitter hasn’t banned bots is to help keep their DAU metrics up


Bingo. Just the other day I saw someone arguing with bob8374922 in a very long thread. When I clicked on bobs profile he had zero followers and account was created this year, no tweets that weren’t replied to others arguing insane “I’m a critical thinker!” Positions.

A very common theme.


So is this a bot or a brand new user who decided to spill his frustration about society online and accepted the default username suggestion that Twitter offered him?


I myself had a full conversation with one of the bots that appears if you say "Metamask" before I realized that @meta2mask was not really a helpful support person from the internet, and was actually a scammer trying to get crypto seeds.


In an efficient market public investors would demand to know the true/accurate DAU metrics with bots removed.


Only if the benefit of actually knowing outweighed the effort of finding out.

Twitter is a mature business. Revenue is driven by ad rates. Ad rates are driven by big buyers who know how effective their buys are — regardless of bots and whatever stats Twitter gives them or us. Therefore, investors have little reason to care about bots.


Devil's advocate;

1) Number of bad actors will always be several orders of magnitude more than number of people twitter can appoint to the topic to. For example: this is the first time I'm hearing instagram-lost-password bots. There should be bots for every topic you haven't even heard about.

2) Increasing the "police" will increase the false-positives. Bots are an inconvenience, but undeserved punishment is a reason to leave the platform. Multiply this by number of connections that user has.

3) You'll inevitably hire one person who will police for fun, trolling, personal gain or religious/political/philosophical agenda for every N number of people you can hire to "police".

4) Bad actors have a lot of time, sometimes capable and rarely even well organized. They create sophisticated tools to mimic real users to "warm up" bot accounts.

5) Bad actors could be, and quite often are, from 3rd world countries. It is expensive for twitter to hire good engineers to fight them, but for bad actors, several dollars per hour could be the best thing they can do with their life at the moment.


Bots contribute to “engagement” numbers. Engagement-driven platforms will only take action when the bad PR from the bots outweighs their “engagement” contributions such as when they post the “wrong” things that go against the narrative they want or when such actions fit nicely within said narrative (and state-sponsored misinformation is all the rage in the current political climate).

Take example of the January 6 insurrection against the US Capitol - the whole thing has been brewing for a year on Facebook out in the open (this wasn’t some sort of advanced terrorist attack organised in the shadows protected by end-to-end encryption) but nothing was done because all this craziness has been generating insane amounts of “engagement”. It’s only when the whole thing blew up that the bad PR from being associated with it outweighed the engagement that actions were finally taken.


Same goes for the Elon Musk scams[0]. They have the same photo as Musk this is not rocket science. On photo upload do a similarity check before allowing new tweets to go live.

[0] There is a vast, unending sea of bots that shill scam cryptocoins or other scams that copy Musk's account and name.


Not just elon, any popular account, movie star, politician, has some scam bots in any thread.

And that's just what is visible. The bot to farm clicks, likes and rt are less so, and probably more numerous.


Twitter allows parody, so this would be hard to enforce without banning legitimate uses.


You could say the same about every other law against actions that are outlawed, and yet things seem to work out well. People can't set up a Ponzi scheme and then claim they're merely running a parody of Bernie Madoff and nobody seems to complain.


The subject is automated enforcement, not law.


Devil's advocate- bots running rampant is merely an annoyance but not necessarily horrible. Targeted disinformation campaigns designed to hurt an individual or group is bad.

Given finite resources- you go after the activity that causes the most harm.


Years ago, freshly out of school, I ended up in a job at a french small shop that required me to learn a lot of things.

They had a brillant sysadmin, that I bothered to explain them to me. Sometimes, he'll come to my desk, looking at my screen, typing the solution while explaining the problem to me with simple words.

Standing up, typing with one hand, and working on what was supposed to be my specialty, he was doing a better job than I was, despite me interrupting his workflow.

I left the job, and levelled up. One day, I read an article about docker, and the name of the dev caught my eyes: it was the friendly former sysadmin colleague, Jérôme Petazzoni, who went on becomming docker's biggest evangelist.

Thank you Jérôme, for making sure I started my carrer by not being the smartest guy in the room. I kept it as a habit.

Or I'm just dumb :)


> for making sure I started my carrer by not being the smartest guy in the room

That's indeed invaluable. That should be the first advice to anyone starting out: if you find yourself being the smartest in a room, go find a new room. Right now.


I left the company I was part-timing at because after college I realized I was the smartest one in the room; my boss thought some of the code I wrote was "brilliant" and for this reason did not let me improve/fix any of it, which led to the company shipping a broken product to some very annoyed customers.

If you are ever managing someone who is "your best employee" and they want to do something you think is useless, please ask them why and what the expected results will be. Also when you get that data, listen a little? If priorities clash do a balancing act: "If you can do X in Y time, do it. But if day D comes along, switch over to my priority".


I graduated college and started working at a local tractor manufacturer. In hindsight, this company had no idea how to make software.

For instance, they required that all "software engineers" were from an accredited engineering program--at the time, none of the universities in the area had an accredited software engineering program, so they would hire electrical engineering majors who had no desire to write software but were looking for a way to get their foot in the door. Most of the EE majors had a single semester of C and that was their entire software qualification; however, I double majored in EE and CS and my passion was software. That said, when I graduated I didn't understand any of this--I just figured there was this successful company and there was so much I didn't know about software, so I thought I would learn loads there--and I did learn loads, but it was mostly about what not to do.

One of my first projects was to take over an embedded C++/Qt project that had been bid out to some contractors in the Ukraine. The software was super buggy and the code was immensely convoluted. Test coverage was part of the contract, so it had tests, but even still, no one could change anything without breaking everything. It took me weeks of plotting the code paths to figure out that there were many paths through the code that were only exercised by tests--literally they were just trying to boost their code coverage metrics by adding code that was unreachable at production. I guess it didn't occur to me that professional software engineers would be so bad at writing code, and that a large and well-known software company would hire them.

Thankfully, after eventually gaining my entirely-nontechnical manager's trust, we were able to bring in a consultancy who helped me demonstrate that it would be no more than half the cost to rewrite the code rather than try to fix all of the existing bugs even if we never found other bugs or introduced a single bug of our own. We did the rewrite and it was successful, but I was beginning to realize that in some overly simplistic sense, I was the "smartest" one in the room as it pertained to software development anyway.

Ten years later, when I talk to my peers who stayed, many of them have been writing embedded C programs and various MatLab models and they still don't understand pointers or dynamic memory or git or anything outside of their very local niche. Which would be fine if they were happy, but now many want to move to another company but they lack the skills and confidence to get anything more than an entry level job at many other software companies--so much of their compensation is derived from their knowledge of their employer's business and processes rather than their technical acumen, so they would likely have to take a significant pay cut to move to another employer.

Anyway, this is already a very long post despite oversimplifying many things, but I hope this illustrates what it looks like to be the smartest person in the room and why it's not good.


Once, I was working on an intranet web tool generating .odt documents for the user to print.

It worked perfectly, except on one machine, where the document could be downloaded but LibreOffice raised an error when opening it.

At first I though I had a bug. Checked my code, nope.

Then I though maybe there is a problem with LO, but no, same version, nothing special. It worked with a document I brough from an USB disk.

After an afternoon of frustration I noted Kaspersky running in the task bar, and did one last desperate attempt at finding the solution by disabling it.

It worked.

Inspecting the file revealed some parts were missing, Kaspersky assumed it was a malware, and not only intercepted the download, but removed silently part of the data on the fly.

No alarm, no pop up, just a broken file.

Disabling the antivirus was not acceptable for the client, so I created a self signed certificate, and turned https on.

The virtual vigilante couldn't spy on the wire anymore, and the user could download her files, unharmed.


I had a development machine once that had the weirdest problem building one particular C# project. Always complaining that one particular Microsoft DLL was missing. Double check references and Nuget, everything looks right, do a full package restore, no joy. Antivirus was eating this particular DLL every time it was downloaded.

I copied a bit-for-bit identical version of the file from a different machine into the correct directory, and bizarrely that worked fine.


I had a very similar issue with BitDefender recently. When downloading the WebRTC C++ library, one of the submodules is harfbuzz, which contains some maliciously crafted font files used by the test suite. BitDefender automatically deletes those test files. That means git sees the repository as dirty, since files are deleted. That means WebRTC's fetch script can't run the 'git checkout' commands it expects to be able to run, and the whole download fails.

While my summary here is brief, debugging this whole mess took a while.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: