skysight-inc/HackerNews huggingface dataset:
Indeed. You can do all sorts of complicated analysis of where, when, and how frequently buses bunch. But the explanation is very simple - like magnets, buses attract each other, in a positive feedback loop. As long as the waiting time at each bus stop depends on the number of passengers that have to get on and off, then buses will always bunch. This is caused by the bus schedule being tight, so the bus has to keep on driving to stay on time. The problem will be worse the more frequent the service is.

The solution is also very simple. Stop the waiting time at each bus stop depending on the number of passengers that get on or off. Slacken the timetable, so that every few stops the bus waits for a minute to match the schedule.

On bus routes with very frequent service, for instance every 10 minutes or more frequent, there is no longer really any need to have a timetable - it will be a bigger win for the customer to just make sure the buses don't bunch than it is to actually publish a timetable. In this case, you may want to implement a negative feedback loop based on vehicle tracking. Most buses are remotely tracked now anyway, so it shouldn't be too hard to return a signal to each bus saying either "carry on as normal" or "you're too close to the bus in front, wait a bit at the next stop".

This is basically the one problem that needs to be solved for buses to not be rubbish, and it is so simple to do so.
Good point. Spare a thought for anyone who's gone through the various releases of Angular in the last 18 months. The other points may be valid though...
This project seems very interesting, yet unfortunately I can’t think of how it could ever be the best solution for a wiki.

It’s said on the site that html and coding are often too complex of an abstraction for a wiki because so many less technically oriented folks have use for editing them.

This audience I would guess doesn’t want to hear lambda anything, I doubt they could ever fully understand the concepts. Not because they are dumb, but because they have other specialties and by definition are not investing time to learn the theory.

It’s probably been a while for many people here since they first learned about lambda calculus, functional programming, or other concepts. But try to think back to when it first hit your brain. You may have started to do some things quickly but even for many in the field it only really sinks in over time and with some continued investment.

I love how there are some undergrad theorems that someone with a middle school understanding of math can grok and learn to prove and derive the result themselves in a matter of hours. The simplicity can be so beautiful for what someone might have thought was scary.

But that doesn’t apply here. This stuff would be scary to lots of people, it’s made my brain hurt before. Now after however many years I have the luxury of reading the paper, appreciating the elegant aspects, and even enjoying thinking off all the connections to other cool concepts. But even for me is this really the most efficient abstraction?

So I like the design and theoretical aspects, nice work on all of it. I just have trouble seeing any mainstream use cases as described on the site that don’t have better potential solutions.
Address issues as they are raised. Don't wait too long to get rid of debt, and most certainly don't rely on fixed time cycles of fixing things. A team has good sense of the issues they deal with, and you can capture their view in retrospective meetings. Depending on how bad the debt is, you should allocate time to improve. Velocity will only get worse as debt grows, so there is a clear business case for such stories: the more debt, the slower the velocity and the lower the quality. Spend time now, to speed things up. But just don't do it from a theoretical perspective. Address real issues, set real goals and measure them.
I know plenty of parents who let their 3/4 year olds "play" away with tablets. Like really, they give toddlers internet connected devices and let's be honest they're not always supervised. Or even most of the time from what I've seen. It's the modern pacifier. When some of the kids come over to ours to play, their withdrawl from the devices becomes very bad. I won't let my kids near tablets/smart-phones. When they're a bit older, they can start their journey on a family desktop in the sitting room. Call me a neo-Luddite all you want, I have a feeling all other things being equal my kids will have a better chance at life than the ones left to explore Youtube on their own before mastering how to cycle a bike.
I have a ton of advice for the 25 yr old me, but I think most of it wouldn't generalize well to other people.

The one thing I'd stress to everyone is - don't take your (good) health for granted, it's really the foundation for everything else. Late 20s is about the time when random issues start popping up. Personally I wish I'd taken the MMR vaccine before travelling...
I think you're succumbing to a distortion brought about by Thiel's wealth and status. Ordinary people make blanket oversimplified statements all the time but because these people don't have such elevated status those statements are not taken as seriously. As a result they don't sound quite so glib.

As a general rule the higher your perceived status the more criticism you get.

Another example would be Elon's Twitter spat. Some random dude on the Internet gets into it with another random dude on the Internet and calls him some bad names and nobody cares and nobody takes it seriously, but when it's two high-profile people it's an international story.
> Also, why would you want classified info that’s not related to domestic surveillance shenanigans leaked to the public?

I guess if the documents aren't related to domestic surveillance, I'd really wonder what else he took and why.
Why do they not replace the kiosks with QR codes on the dining tables? You scan the code and order directly from your smartphone.

That's the experience I know from China. Are there any restaurants in the US that do it similarly? Or perhaps not due to the lack of WeChat and suitable payment providers?
I interpreted that as socialist, communist or attempting something like that. And because of the fuzziness I asked you for a list.
Definitely harder than 20 y'old skinnyfat you but also definitely easier than 40 y'old skinnyfat you.

Just focus on the process and enjoy the ride, I guess.
That would be the state in which everyone thinks an internet connection and an audience makes them an expert?
Darpa dedicates $75M (to start) into reinventing chip tech
For the last 5 years I've worked primarily with startup CTOs and enterprise directors/VPs to build teams practices XP, lean product development, and user-centered design.

My advice to them, and my philosophy on this topic, is that technical debt is just that- debt. It's not a dirty four-letter word to be avoided, it's something to be managed the way you manage actual financial debt. There are some projects where the software you build will be self-contained (no dependencies), will require minimal changes in the future, or it may have a short shelf life (e.g. it's a stopgap before you cut over to a new system). In these scenarios, accruing technical debt isn't the worst thing in the world if it allows you to reap business value faster.

When you're building software that's going to live long-term, or that drives core parts of your business (and therefore will need to change frequently as your business changes), technical debt needs to be tackled early and often. It's ok to accrue technical debt in the short term ONLY if you make that decision consciously knowing that you'll need to address it later (e.g. I had a client that needed to release their software for a trade show, so we accrued tech debt and created tasks to track every piece of debt we'd want to tackle later, and then prioritized that work immediately after the trade show).

That said, it's also important to be clear about what constitutes tech debt vs what is over-optimization. Outside of libraries and frameworks, I don't really need the software to be "perfect". I need it to be clear enough, tested thoroughly enough, and easy enough to change to maintain a high velocity. If a part of the code has become spaghetti-like, or if we see code duplicated more than 3 times, or if we have disparate code that's too closely coupled to easily make changes, that's technical debt worth tackling.

The vast majority of organizations I've worked with typically think much shorter term, which is why they find themselves repeatedly accruing technical debt to the point where changes to the system occur at a snail's pace. It takes a lot of discipline, and coordination between IT and business, to practice what I'm describing, but that's the ideal that I strive for and advise my clients to strive for.
Why is the pace of releases an important metric for using a programming language?

Focus on code quality, and maintenance simplicity.

If anything, being able to use the same version for x years and having it be consistently better than any JS library/framework I used, means that the work done is of high quality.

Maybe you should watch Evan's talks from various Elm conferences ( search on youtube, for example https://www.youtube.com/watch?v=uGlzRt-FYto )
He addresses that concern that some people have, and why it has the pace it has.

As I understand it, it's better to do things right and take as long as it needs, rather than hurry and ship fancy things just to ship them.

Elm is perfectly production ready as is, and beats any JS stack for me. Both in code quality and maintenance cost.
GM launches a peer-to-peer car sharing service
Do you happen to live in Europe? I live in Germany and while the Silicon Valley mentality doesn’t look healthy or sane, Germany is surprisingly “lame” for such a successful country. The German economy relies too much on old industries and the politics here are unwilling to change anything about it, be it policies, funding or infrastructure.
I do pay per minute in 6 second increments but the price is so small to be barely noticeable.
I've been using https://foreceipt.com/ (iOS and web app, Android coming soon). It keeps all your data on your Google Drive account.
A ton of them play Oldschool Runescape where they can either do a repetitive task at around 25c usd worth of gold per hour (can do it on 2-3 accounts simultaneously)then sell it at the end of the day for btc/usd. The type of account required for that would take 1 month to create and about $17 usd in membership/items. Others offer services like training your account up. As to how they spend it who knows. I donated my account to one when i quit, it has the levels to make $2 usd per hour.
Not a CTO.

1. Not only legacy code eats resources that can be thrown on new developments. While legacy code is most troublesome, it still will be at maximum only twice as bad resource-wise, than new and pretty code.

2. As company grows, it may well be that a piece of software being used by by less than 5 people at the company, but require an own developer team to continue actively support it.

3. Maintenance resources vs resources spend on development is a never ending drama.

4. You should proactively think how to cull you internal projects, and be able to dictate to the rest of the company to stop using it.

5. Custom software for "business guys" - an easy way to multiply IT support budget. Hiring technically illiterate analysts, finance people, supply chain people costs a lot, a great great lot.

6. Last point. THERE SHOULD BE AN IRON WALL in between people making "money making code" and all other tech at the company. Can't stress this more.
Author here. Happy to answer any questions anyone has about this post.
Elm doesn't need to be merely maintained, it needs to grow and evolve.
"useless or actively harmful, like e.g. most of FDA regulation,"

You should be careful with such sentences. Maybe it's ok to say "some" but saying "most" is nonsense and dangerous.
They run in ring -2. Proprietary software with networking stacks, file systems, device drivers, web servers, all running in a mode more privileged than the operating system. There's also the Intel Management Engine with pretty much the same features but running in ring -3.

https://www.youtube.com/watch?v=iffTJ1vPCSo
Yes, I looked at the link. But the claim (I was questioning) is that it's full of lies and absurdities to further political ends.
Not knowing when/where to stop is like a big weakness among humans.

This is not just with scams and crimes, but even with good things.
The most frustrating part is explaining technical debt. From a business perspective you have a running software. You can sell it - it has all the features needed. Now you come along and tell me you need to fix something, that no client can see, that does not add any features and it might even lead to bugs. And you need two people and x weeks. I can imagine how "technical debt" is perceived as "snake oil" or "developer fun time" for management.

To avoid frustration it is best to fix technical debt in small steps, mix it in with others open issues. Devoting developer time for a big technical debt rewrite is hard to communicate.
I wonder what happens when you forget your key at home. If I forget my keyfob for work, I usually have to do the walk of shame, around the hallway from the reception desk, whenever I use the bathroom. But I can still get in. And if I really wanted to, I could get a temp key for the day.

Do compiles like Google, et. al. have security departments that give people temporary keys that expire after a day, or do they have to run back home?
Not sure if sarcasm, but no.
> What you're describing as what you didn't expect is how PhDs were done traditionally. It's the more recent US model to have classes and exams.

Classes and exams in a PhD programme? I've never heard of this anywhere - I had no idea that was a thing in the US.

There is an ugly trend in the UK to having "credits" for attending workshops as part of your "personal development". You basically have to go and sit in a workshop pretending to listen to someone talking about academic writing so that some admin can tick a box. Considering even postdocs and RAs have to write reports on how their "personal development" is progressing I don't think the powers that be will be happy until everyone can be placed into a spreadsheet.
If you're trying to scale Wordpress, pay wpengine to handle it for you and move on to other things. Down the rabbit hole you're staring into lies madness.
In newer cars you can turn off the passenger side airbag. But there were many years when you couldn't. If an airbag deploys and the infant is in a typical rear facing infant car seat, then the child can be crushed by the force of the airbag.
Apple Piazza Liberty Opens Thursday in Milan
I didn't state it that clear, but I am well aware that adding overtaking to the equation doesn't solve the bunching problem .

But the bunching itself is not a problem. The problems are the effects it causes like:

1. crowded busses

2. arrival delays

Overtanking has a major impact on the first effect as you have stated too, the 'crowds on the buses quickly equalize'. The impact on the second effect depends on some other parameters. If all busses are crowded there will be no effect at all, but if only a few busses are crowded (the front busses) and the busses behind them are empty, there can be a positive effect on the arrival delays too (the worst case drop off time will be lower).

So I would not say 'it does not help' as it certainly decreases the negative effects.
Hard ? Because of getting the PhD in the first place or refocusing your career afterwards ?
Thanks, that's a really useful tool and a good write-up on the utility of it.

In the short term I can probably convince the higher-ups that if I download the images manually and do some level of investigation using a tool like yours then it should account for some security.

Have you considered container scanning tools?
Yes, just as a sleep aid only.
The military agrees with you. The DARPA Grand Challenge was what really got autonomous ground vehicle research going.

https://en.wikipedia.org/wiki/DARPA_Grand_Challenge

The US Army is still putting funding into a variety of autonomous vehicle programs. For example they want to send a convoy of vehicles to resupply a remote outpost without putting human drivers at risk.
I think there's no one best solution for a wiki, because audiences differ.

Some people prefer a feature-laden word processor, some, a complex language like LaTeX, and some, the distraction-free notepad.exe. For each group, for their subject tasks and mental habits, their chosen solution feels best.

I don't see why this approach can't be best for some niche.
With 10B monthly requests, you speak from a position of having an operations team who spend 40+ hours a week on keeping your site secure (possibly even a dedicated security team?). Most sites do not have that luxury. If you're doing that on your own, then you're far from the average site operator that I'm referring to here. In fact, most everyone on HN is not the average site operator I'm talking about here.

My poorly communicated point is that by using extreme language like "I'm going to hack your static site" dilutes the message and makes average operators less receptive to more advice in the future. Troy does a lot of good work on reducing friction and advocacy, but sometimes he puts out more extreme content like this which makes me worry that it may have the opposite effect.

PS - Do you think the vaccine analogy works? I'd appreciate some advice on how to improve it
UK Judge Says Accurate Journalism Is an Invasion of Privacy
Usually in a higher security environment, we'll make sure the authenticator is a separate device (phone or hard token) and expressly forbid having a soft token on the same device that has the password safe.
I actually do agree.
But does this not conflict with our current concept of democracy in general?

Because democracy is supposed to implement the will of the people .. so populism?

But I don't think we should abandom democracy, but maybe make the system simpler, smaller - easier for people to understand. So more power back to the local communitys, instead of up and zentralized.
> We could've spent 10% of what we spent on GDPR on education about tracking and the result (if the goal was to reduce tracking) would be much better. How do you know it would be much better?

How would you implement this exactly? The GDPR effectively has global reach as it doesn't apply only to EU citizens, and it's easier to implement one compliant system than have a separate one for non-EU data subjects.

What sort of timeframe and expenditure are we looking at for worldwide education surrounding tracking on the web and privacy? How do you plan to keep people up-to-date with the latest techniques Ad network deploy to defeat past best-practices?

In your example, what sort of recourse would exist for people who are currently privacy-minded, but not savvy enough to know someone's collecting more data than they'd actually have consented to (in your analogy, the equivalent of the Ad network sticking its fingers in people's wallets, taking what they're not entitled to)?
Hey All
Are you essentially reverse-engineering popular images like mysql/mysql? Are you not running vendor products that might reference public images?
Yes, Atlanta. Only slightly (2* or so) warmer, on average, than DC. And, this time of year would typically have the hottest days. So, I'll stand by my point. If you're idling your car for 20 minutes while eating a Big Mac in April, you're needlessly polluting. Hot days in July and August - I get it, but would prefer you just went inside.
If I have full control of a DID, implementing callback isn't hard. That would be a bandaid type solution built on top of the existing phone network, however. Fixing ss7 at a systemic level so that all call routing in and outbound is verifiable, CID spoofing is impossible, is what is nigh impossible.
> any advantages Elm might have had initially, is coming to parity with other solutions.

Absolutely. Elm filled a particular void in front-end development for a while, but much more mature, well-maintained, growing communities are now sprouting up that offer powerful statically-typed functional programming that transpiles to Javascript, all valid alternatives to Elm with far fewer risks. ReasonML probably being at the top of that list.
You can't usually buy just a house - you buy the land too (or at least a lease for the land).
Zeus and Sherlock Holmes could both be argued to have had transitive causal influences upon us - so in order to make that statement make sense there must be some other implied constraints on what is considered to "exist."
If you want something that's (really) easy to get started with, and yet won't artificially constrain you from using your functional programming tricks as you evolve, I recommend trying out Concur [Haskell version](https://github.com/ajnsit/concur) or [Purescript version](https://github.com/ajnsit/purescript-concur). I wrote an initial introduction which also compares it with elm - https://github.com/ajnsit/concur-documentation/blob/master/R....
That is sad :(
I think a lot of the time when a developer shouts “technical debt” what they are really shouting is “code someone else wrote that I’d rather rewrite than understand”. (The rest of the time is the same but they’ve understood it enough to think it’s a disaster area.)

I have found it’s best to not take tech debt complaints very seriously and instead look at actual success metrics. For example if every change to a bit of code introduces new bugs then that might be a reason to tidy it up.
That's a valid point. In this case, two reasons:

1 - active development is relevant. Is it being updated once a year, once a month. Is it going to take 1 year, 2 or 3 years.

2 - Above is not a deal breaker along. But, the new release is going to break stuff. you need to have ability to plan around things, especially as the new release will have paradigm shift (from what I'm gathering). You don't want to write lines and lines of code, then needing to rewrite it all.

I think what makes it even more unreliable, is lack of any communications. I think part of the problem is, Evan (the creator) probably is still not sure what this future looks like. He is very articulate, but not seeing any blog post update makes a reasonable person assume that this new release has not been fully conceived. So, everyone knows there will be a break change. But who knows what will break, when it will be released, etc.

On top of that, this new update has become a gatekeeper for bunch of pull requests and bugs on the existing system that is not being touched.

The people who sit next to Evan the author of Elm in Action and the biggest users of Elm (Richard Feldman) has pushed back the release of his book by one year. Basically the remaining part of his book, is all the SPA stuff that the version of Elm is supposed deal with. From what I've seen, it seems like even he doesn't know what to expect [0]

Put everything I mentioned together, it makes it hard to recommend Elm for anything your company will be depending on, especially when there are other solutions out there. Why take the risk.

[0] https://www.manning.com/books/elm-in-action
The smog from China is not under the control of CA...
Our World in Data for teaching – what we are learning from your feedback
anyone knows best structure of node js which include security of endpoints , kind of management of memory leakage and have high scalability with requests
if suffering has a transformative power, it’s that you are compelled to learn humility.

With luck, from humility comes empathy and compassion. Unfortunately, you’re just as likely to get fear and despair.

That doesn’t make suffering belong to any privileged ethical class— it still sucks!— merely that in responding to the normal fact that “time and chance happens to everyone”, we can extract the opportunity to grow and get something out of it other than pain and despair.