skysight-inc/HackerNews huggingface dataset:
After a recent lost and found experience with Lyft, I can say that uber has thought through this process in their software.

Drivers can be paid for delivering lost items, and the process is kicked off without the need for customer service staff.

Lyft had no infrastructure fpr this, and relied on Zendesk and customer service reps to facilitate the delivery.

There was no function for paying the driver, the item was delivered days later because i had to wait for someone to answer a Zendesk ticket, and even then there was no way for the rep to set up proxy calls between me and the driver.

There are other reasons to suggest that Lyft lacks technological expertise, but this is a perfect example of a feature that is well considered by Uber and not considered at all by Lyft.

I'd love to support Lyft more, but I am forced to use a substandard product in order to do so.
It's a hard problem, but it's not necessarily harder than other approaches to dependency management. There's pretty much no approach to dependency management that isn't hard in one way or another.
This is false. I have learned the basics of assembly without knowing C first. My experience before learning assembly was: Java, Python and some Objective-C (without knowing pointers). So if your point is that you need to learn programming first, then maybe that is true but I highly doubt it. But I can't refute that with my own experience.

Here wa my roadmap:

(1) I first learned assembly by learning computer architecture from Tanenbaum's book -- Structured Computer Organization -- and related course at the Vrije Universiteit Amsterdam. This taught me a toy architecture (Mic1) but it give me a rough idea of how assembly worked.

(2) Then, later I took a course in binary and malware analysis and all that we were required to do was to read x86 assembly in IDA and interact with it via GDB -- and using the command: layout asm, which gives a layout for all the register values and upcoming instructions.

And once I have a debugger available and understand it well enough, I can learn quite well since I can make little predictions and check if they are right or wrong, and so on.
Most junior level positions are being filled with the massive influx of new grads from really strong intern programs at most companies now. If you're in college now, make sure you get an internship at a company in your field. If it's too late for that, then you'll have to do a little extra work and probably work on a couple side projects and post them on GitHub. That first job will always be the hardest to get, so don't feel bad if you keep getting turned down.
I have a strong feeling that Uber will survive time, simply because of the differences in their cost-of-acquisition and user lifetime value; Uber attracted me through their ~$40 cost of acquisition by paying both me and the referrer in credits which is small when you compare and see myself spending more than that amount in a year and definitely more as I move through life. I can also see them subtly increasing prices until they finally dominate transportation and ride-sharing.

Expending huge amounts of money to grow is actually normal, Microsoft had billion dollar losses trying to market their Microsoft Surface in an Apple-saturated market and are currently now profiting from their heavy losses in the past; you can't really see the past until you're in the future.
>> Taco Bell famously repackages

>> list of what you can work with in a Chipotle is short, very short

That's not specific to Taco Bell or Chipotle. That's called Mexican food.
At one stage this was built on pixi for 2d rendering ( http://www.pixijs.com/ ) but I think 3.0 it took out pixi?

Anyone know what the rendering is like now?
There is one problem with conclusions, they assume that interview score is the same as real world success of a candidate. It is not so, interview result correlates with future success but there is no strict determinism.
So companies prefer students that successful in interview AND come from good school, rather than just rely on interview results. It allows them to maximize probablilty of the finding a good employee.
They’re big enough to buy out any actually threatening competitors. A duopoly or a small oligopoly aren’t much better.

As for IBM or GE, buddy it took almost an entire generation for their stranglehold to break down, and in fields with much lower barriers to entry than this.
That’s simply untrue. Start with a small micro controller, a Microchip PIC for example and you’ll quickly find C is complete overkill.
Of course it is true that US intelligence is far from monolithic, but I think it's a useful-enough abstraction for the purpose of thinking about the issue.
Took me far too long to realize author substituted actual firewall rules for simple lists of numbers. I don't get the point of not doing the leg work to compare an actual list of rules from differing firewall implementations (as was the initial promise...)
California Employers in a Bind Over Immigration Enforcement
Huh?
targeting your home PC?
targeting your identity?
targeting your online servers?
When code quality is hard to enforce, one approach is to at least ensure that the design of public APIs, and boundaries between components reaches some level of quality. This is usually a smaller surface to monitor than the entire code base, and it allows islands of good quality to emerge. Good boundaries also will allow for easier refactoring over time of the really bad code.
Consider me seriously impressed by that stance.
Try this link: https://www.brave.com/publishers/
GiveDirectly: Can Universal Basic Income Eliminate Poverty?
"While analyzing the servers of malicious actors, Kaspersky researchers also found archives containing a cache of Telegram data that had been stolen from victims." more worried about that than the rest.
I guess it might sometimes be fine to be a relativist and write off the need for tests as a result of "nuanced thinking," but I think you have to accept that you are running a risk by shipping untested code into your product.

As others have said, line coverage is a misleading metric. Ideally, your tests would fully cover all _program states_, and even 100% line coverage doesn't guarantee full state coverage. If you have untested states, then the following facts are true:

- You don't have a formalized way of modeling or understanding what will happen to your program when it enters an untested state.

- You have no way to detect when a different change causes that state to behave in an undesired way.

So the answer to how many tests does a PR needs- as many as needed to reduce your software's risk of failure to a minimal level... And this is failure right now, and in the future, because you will likely be stuck with this code for a while. Since it's difficult to know how much a future failure will cost your company, IMO I always try to err on testing as much as possible. Plus, good comprehensive tests have other benefits, such as making other changes / cleanups safer by reducing the risk that they unintentionally side-effect other code.
Yes - about 200km north west of Sydney. At least we don't see taipans.

And... possibly. But my understanding is they're expensive / in short supply, require careful environmental control (though a fridge probably cuts it) and they have a relatively short shelf life.

Plus in many cases, people most at risk are a good way from cool storage.

I think there's also a need in some - but thankfully not all cases now - to identify the species via swab & test. If you get bit, you probably know the type that bit you, but it's not guaranteed.
Then you have to prize them away when you want to leave the house.
Wells Fargo bulk statement downloader (for tax season)
The Mill architecture:

> the mill uses a novel temporal register addressing scheme, the belt, which has been proposed by Ivan Godard to greatly reduce the complexity of processor hardware, specifically the number of internal registers. It aids understanding to view the belt as a moving conveyor belt where the oldest values drop off the belt and vanish.

https://en.wikipedia.org/wiki/Mill_CPU_Architecture
Its a large mix of problems. There is infinitely more demand for the top ~20% of developers then the bottom ~80%. There is a glut of new undergrads and transitioning professionals. There is a larger-then-other-industries capital expenditure in hiring, training, and managing, developers - which compounds the hiring difficulties of most small companies including almost every start-up. Oh and there's massive conglomerates with near infinite resources (Google, AMZ, FB, MS) hoarding top tier talent - which plays into developer validation of who the top 20% is.

It's a mess, and it paints a single reality. The tech industry isn't as easy to break into as pop culture has labeled it over the past decade, and in my view it won't be getting any easier... sorry to the younger generation paying big $$$ for a CS degree.
> How do you make sure that the refactored class does the same thing as the old one?

This. This is the problem. The answer, with tests.
> would lose the ability to control what that data is and who has it.

It's the same with Google, you cannot control your data and what they do with it.
I completely agree. I've met a few developers who think that 100% coverage is required, and that a complete set of tests will save them from all bugs. Perhaps unsurprisingly, they wrote pretty crap code. Passed the tests, but it was unpleasant to work with.

I like to see good coverage (say, 85%) because the act of trying to cover that much has led us to discovering some bugs that would otherwise have gone unnoticed until someone ran into them in production. But 100% line coverage is still a tiny, tiny fraction of covering all permutations of how that code is used, so I feel like trying to hit some kind of holy grail perfect coverage target over-emphasizes the value of tests. While tests can absolutely be very useful, it's the actual running code that needs to be high quality, the tests are just helpers.
> Most kids don't know how to self-regulate screen time.

I think that's the center of the problem. In the current times online media and mobile apps are designed to maximize the participant's screen time by being as addictive as possible.

Even grown-ups face problems self-regulating with regards to an "adversary" that invests huge resources in getting our eye-balls (and data and ad views).

Restricting screen-time becomes more and more difficult the more kids grow up, I do not think that this is a very scalable solution.

I think it's more important that kids are made aware and learn how to deal with this "adversary". Make them aware how the TV (or smartphone) "catches" them when they actually had planned to do other things. Make it a game to find out, together with your kid, how a device can have this kind of control over a person. Kids are curious, they will want to know about mechanisms and incentitives of the system and I think this can be explained even with the vocabulary of a 6 year-old.

Humans are very adaptable, maybe kids growing up in our current environment will just acquire skills that the older generation does not have and has difficulties to imagine.
I keep toying with the idea of building a system that allows services to authenticate with you. It's not going to be useful for the general population, but for people who have a clue it would be useful for detecting CA hacks. Theoretically it's not so hard -- you send the service a key when you first start using it. The service signs challenges to prove that they have the key. Now an attacker must both hack the CA and get the private key to impersonate the service. I tried to figure out a way to do it with a plugin, but unfortunately it looks like it requires modifications to the browser to make it work. Thinking pragmatically, I suspect that it would never make it into a mainstream browser (for the same reasons that things like Persona never made it).
Doesn't that kill the possibility that a visitor will already have common content cached when visiting your site for the first time? I know that's not the only reason to use a CDN, but it's a pretty big one.
Sure. Even if the volume dropped 50% Uber could just fire half their staff. There is no way that Uber couldn’t find some volume level to play at.
> You accept long-term “technical debt” with the adoption of any technology.

how long have they been using perl5 over at craiglist?
iOS 11 and Safari here. Same thing for me. I can’t do anything with the site.
On the flip side, encouraging good coverage usually ends up uncovering some bugs that might otherwise have gone unnoticed until they bit someone.
In this case page load times are being valued over everything (not just AMP but also the search rankings algorithm).

I'm not 100% sure if it's a vanity metric for Google or not.

...Google does have some of the greatest statistical minds in the world, just maybe not the best product/UX minds.

KPI's can be highly misleading when it's disconnected from raw UX. It's difficult to measure user emotional experience, especially when you have a monopoly on user attention with Google Search and total product lock-in with Gmail. When users don't have alternative options analytics stats can be deceiving.

And just because a user completes X task a hundred milliseconds faster it doesn't necessarily mean the UX was better. And just because the UX was made incrementally worse doesn't mean I'm going to use Google/Gmail any less. But enough of small cuts can build up into a serious wound.
Seriously. Would be great if somebody could just declare a new mime-type such as "text/html5" that could be used to activate modern html rendering in email clients and would be shipped alongside the existing "text/html" and "text/plain" components. Eventually when enough email clients support this, we could stop generating the legacy html emails and only include text/html5 and text/plain mime types in emails.
ArtStation, CGSociety, and various art subreddits.

/r/computergraphics, /r/animation, /r/photography, etc.

Recently I've opened /r/DigitalArt. It's a small community now, but you're welcome to join =)
> I thought a growable stack via a guard page that allocates more stack on a fault was common in C-based languages.

It is, but that's not how Go's growable stack works. Go's is grown by the language runtime and relocated when necessary, using its GC infrastructure, so you really can't put non-Go stack frames on it.
Like with Starbucks, it was the individual employees, their kindness, and their appreciation for the product that made Chipotle special for me during their non-mediocre years. I liked Starbucks the most in about 2006 and Chipotle the most at around 2010. It's too bad they're mediocre now. They still both feel magical occasionally, though. I'm not sure whether they compromised the product or the culture first.
ATH Zurich have a single prop craft that uses just a single channel high speed motor control to stabilise and steer it: https://www.youtube.com/watch?v=P3fM6VwXXFM

I wonder if this maybe has two contra rotating single blade props that they can control quickly enough to be able to speed them up for half a revolution to generate asymmetric thrust to provide pitch and roll?
Wait, I think that would be exciting. AMP on the other hand...
Poor frogs. The water temp just got upped a couple of degrees. Too late to jump out or not just yet?

Some relief for frogs that make it out of the pot:

https://mailinabox.email/

https://redmail.com/

https://protonmail.com/

https://www.fastmail.com/
I remember reading that article and thinking that the author either isn't old enough to remember the 90s web or has memory loss about how hostile it was to the user.

Ubiquitous banner ads, "free" 56k if you use our browser and click links, cookie bonanza, link hijacking etc... have been part of the web since day one.
Typical assembly languages hardly do anything more with cache hierarchies than C does.
I'm on the senior level side and as the previous comment mentioned, it's around 100k CAD (typing it from a phone, cannot easily convert to USD).
I think the "Junior" title is used entirely by companies to get a discount at salary negotiations these days. I work with a large mix of mid level, senior, and "Junior" developers by title. The practical difference in our technical skill levels is almost nonexistent. The proper progression should be: Intern -> Developer -> Senior/Lead, with Senior/Lead denoting that certain expectations are made of your organizational and management skills moreso than seeking genius rockstar programmers.
It really isn’t.

https://en.m.wikipedia.org/wiki/Mexican_cuisine
Learn basic digital circuits.
Learn an assembly language.
Learn C.
Implement a simple interpreted language.

You don't have to reinvent every level of the stack and connect it all together(your imagination can fill in the gaps), but this removes the mystery of computing.
Revisit this post in a year, and I'd not be surprised to see that it was correct. Turn Chipotle into an upscale version of Taco Bell and market the pants off of crappy food and sit back and watch profits grow.

Chipotle can't really compete with restaurants that actually serve good food, so why not fill the giant divide between them and Taco Bell?
Do you have a specific example? I wrote programs in Z80, AVR, x86/amd64 and MIPS assembly. In my experience writing C is MUCH easier.
The customers will eventually suffer a death of a thousand cuts through quality and reliability issues if direct attribution to revenue / customer requests is a requirement to work on anything. But of course you can't rewrite ever time you hear about a new language. Obviously there's a balance, and striking that balance correctly is a huge part of the job.
The Expressive C++17 Coding Challenge in D
Respectfully I disagree. I’ve found that ‘talking about doing it’ will cause problems if you aren’t able to do it and hold schedule with everything else. From personal experience, for parent post, I’ve found it’s been best to implement what you can for unit tests and grow it yourself slowly or at whatever pace you are comfortable with, but set the bar high for yourself, beat it, and then maybe try to get others on board. This only holds if there is no mentor you could talk into helping you. Just personal experience. :-/ If the culture doesn’t encourage them now, announcing you will be doing it might only hinder the effort.
These cost of living calculators are severely flawed. It fails to capture that RSUs form a significant % of compensation in the Bay Area. It also fails to capture the exponential impact of high dual income. Also, fails to account for rapid income gain from real estate appreciation. Finally, fails to account for the ability to switch jobs quickly and climb corporate ladder.
> I do not understand the hate?

Oh, the hate is just the new version of the ASCII ribbon against HTML email...
FB`s so tough on leaks that employee was concerned FB was tracking his location
Agreed.

When I did my undergrad, Ada was the primary language of instruction for first year, with x86 assembler taught as a subject in the second semester.

The idea being to get us thinking about programming correctness from the beginning, then to teach how the machine worked once we had a good foundation.

By second year we were just expected to know C, and coming from assembler, things like pointers were something I never had a problem understanding.

Start high to get a good grounding, go low to understand how everything works, then return high to write code that has a good grounding in how it will be executed on the machine.
I think maybe the case for expectations at all? These do not exist in nature and are a fabrication of your ability to express them. Most need to stfu about reasonable expectations
Saw this previously on hn https://github.com/google/boardgame.io/blob/master/README.md
DigitalOcean[1] has a one–click option to compile FreeBSD kernel with ZFS configured (for what its worth).

edit: including my referral link here will probably result in negative karma, but i'm desperate for points!

[1]: https://m.do.co/c/8c882a721944
It's aside from your point, but would that Toyota's embedded software were as good as its mechanical engineering...
The flip side is that any reasonably popular site on the web is going to cost a not insignificant amount of money to maintain, and the hard reality is that nobody really wants to pay for it out of pocket. They want it for free, paid for with ads that other people see while they block them with their browser plugin.

I've said for a long time that I'd rather see something that functioned much like Facebook does (or did, rather, maybe 10 years ago) but was completely supported by subscription. Let me pay something like $5/month and in return no funny business, no stupid manipulation to get more page views, etc. Just a place I can interact with friends and family.

But nobody would pay for that, even if that's basically what they pay for it indirectly through the products they buy.
"For the 99.9% of adversaries having a wipeable iPad will stop browser fingerprinting and switching up IPs or cafes will stop IP tracking."

Down my way, the streets are littered with cameras and I suspect they can match time and IP address and id you easily. This is the same in most industrialized nations probably.

(Not hiding from anybody here, just a thought experiment)

Edit: Very frequently the Police will ask for drivers who have in-car cameras when there is a crime or accident. And a lot of them do have cameras. In Australia.
That depends on whether or not you can easily replace fans. Or if you are even going to use the fans (if watercooling GPUs, you don't care).
Other than that, they were running 24/7, but usually focusing on efficiency (undervolted), many times without a case. This is usually better than "gaming" GPUs, which are overclocked and stuffed inside a case.
VPN providers are replaceable in ways in which last-mile ISPs are not, so they have more of an incentive not to trash their reputations.
And in a bad culture other priorities can be more important. As an employee your job is to adapt and support the business. Writing tests in a culture that doesn't value the time spent is not helpful.
Google is on a mission to own every corner of everything related to the Internet. Email sucks, but I'll keep my boring old email in lieu of Google shoving more targeted advertising in my face, thank you very much.
There is a point to be made in there somewhere, that your VPN needs to be an entity you trust (at least more than the alternatives), if you pay for its services, expecting privacy for the price.

A more helpful rant than the OP provided, would be one that informs you of ways to evaluate the trustworthiness of various VPN providers.
Honestly with all the versions of js libraries and all the CDN hosts, the limitations of cache size and the insane bloat of webpages, I think you're going to have to be pretty lucky to get any beneficial cache hits from unrelated third party sites.
It's pretty good. (Lyft also has the express concept, which I've used a few times. Most of those times the driver was under the impression it was a Lyft Line, and were wondering why there weren't any more rides showing up).
Isn't the problem the high turnover rate in the industry? Why invest in educating someone if they are going to quit in one year or so?
In my experience, the variety of specific versions of libraries sites are locked to dilutes that performance benefit. Just look at a cross-sampling of sites calling jQuery or <insert your favorite library or framework here>.

In theory, the maximum benefit of a CDN only comes if everyone is on 1) the same version or, similar but different, 2) an evergreen version. And the latter is a big red neon sign screaming "DANGER".