skysight-inc/HackerNews huggingface dataset:
A lot of people in tech (myself included) would benefit greatly from this attitude. How many people get caught up arguing over minutia in tech, such as which distro to use, or which editor to use, or which way to do something when all options are perfectly fine?

I'm not saying cut corners, but instead keep your focus on what's important.
I am curious how the chat extension is architected.
I would recommend taking the time to actually watch the talk [0]. It's well worth it.

[0] https://www.youtube.com/watch?v=2V1FtfBDsLU
There's also a Wikipedia section on their hiring: https://en.wikipedia.org/wiki/Renaissance_Technologies#.22Qu...
When the demand for a good increases, the price increases - which is why currently a single bitcoin goes for ~$6,400.
Unfortunately jumping to definitions in Ruby is often hit-or-miss since the language is very dynamic and idiomatic Ruby code often uses a fair amount of metaprogramming.
That tweet just tells me not to use Homebrew.

Just kiddin'. I think, inverting the binary tree probably means mirroring it. I had an interesting Google interview as well a few years ago where I aced the automated coding test but then the first human interviewer didn't get why I said that regular expressions run in linear time :) Our background was just very different.
True story.

In the late 70s my grandmother was annoyed at my aunt (her daughter)'s decision to finish high school instead of dropping out. She actually said this:

"You don't need a high school diploma to push a baby carriage."

Yeah, sure that's not "now," but now we make it into "wholesome" TV. (The Duggars)
I'm beginning to suspect that, in the context of these debates, "most static languages" is a roundabout way of saying, "Java", or other static languages with a similarly anemic type system. Also it's a roundabout way of describing the particular way that Java code tends to be structured.

In one that has better support for generics (i.e., reification, contravariance and covariance) and some form of mixin, you generally shouldn't have that much trouble adding behaviors to an entire class of types without having to modify any of them. This is the fabled open/closed principle that is oft lauded and rarely practiced.

To take it a step further, if you're using interface polymorphism and decorators to build your types instead of relying on subclasses, you won't be able to paint yourself into the corner you describe in the first place. The problem is, of course, that a language like Java that doesn't let you add new behaviors for types without either modifying the original source file or resorting to some Gang of Four awfulness, will tend to punish people for writing cleanly-structured code like that.
Wow, I wasn't aware of that.

What cemented GoG for me was two events: One, they got the entire classic Thief series (my all time favorite game series which won't install on modern Windows from my game discs) and two, when a few games on Steam that I thought I owned were pulled or otherwise tampered with; something I paid for was suddenly gone or altered with no recourse. I still have my Steam account and I do play games on it, but going forward all of my game budget goes to GoG and thrift store finds.
A little more than that.

Navlab 1 was built in 1986 using a Chevrolet panel van.[2] The van had 5 racks of computer hardware, including 3 Sun workstations, video hardware and GPS receiver, and a Warp supercomputer.[2] The vehicle suffered from software limitations and was not fully functional until the late 80s, when it achieved its top speed of 20 mph (32 km/h).[2] https://en.wikipedia.org/wiki/Navlab
Yes low dose, 100mg, hard caps with extended release.

which is slightly stronger than the 75mg "micro" dose.

It can still mess you up.

https://m.apotheken-umschau.de/Medikamente/Beipackzettel/ASP...
According to what? There is no restriction when you register a domain. org is short for organization, just like com is short for company. I see lots of .com websites owned by individuals or non-companies. It is definitely a guideline and not a hard-fast rule. The only TLDs that are actually enforced are ones like .gov and .edu.
The Case for Dark Life
What about the other 99% of the users who don't want to pay? This really doesn't change the equation for Facebook in any significant way.
DIY 360° Review: How I asked colleagues for anonymous feedback about myself
Knuth reward check
Sharing Secrets (Without Giving Them Away) – News – Communications of the ACM
You should try Fox News.
Pre internet news were ad supported but they didn't have growth expectations like Google and Facebook. It was a pretty static business so once they had enough ads to survive they could keep things steady. Google and Facebook on the other hand have to push the limits every year to keep growing.
That has to be one of the worst presentations I've seen. Is it ironic?
If you have heard of the Curry-Howard equivalence, that programs and proofs are the same thing, the proofs in question are constructive, intuitionistic proofs.
I don't think that any of the common development methodologies are crap. I see no problem with writing tests as a way to work out ideas. I see no problem with not doing so. I think the main flaw in these methodologies is that they assume people problem solve in the same way. It only becomes a problem when you have a methodology zealot telling you to work in that way only. I am happy to write unit tests to cover my code. Unit tests can and do prevent bugs/outages in many cases.

What I do think is kind of crap is the holy war of methodologies that exists. In my experience, it usually happens that some new CTO or other manager comes in and says, "We are doing it wrong! From this day forward, WE ALL MUST USE TDD/AGILE/WATERFALL/YOURFAVORITEWAYHERE".

There is no latitude given, and folks who are not used to the methodology now take 1.5 to 3x longer to complete things, and deadlines slip. Then the push to complete work means that things get written sloppily and tests are not well thought out or people arent fooing their bar with the baz properly. Quality suffers in the short term, but eventually everyone catches on, and life goes back to normal.

Then the new CTO shows up...
Confirmed, you suck as a moderator. Can't take any critique, no, must be my fault you're such a snowflake. You're quite literally what's wrong with society these days, you outright reject anything that might potentially hurt your feelings; you don't have a right to not be offended you overly sensitive little fucking man baby. Grow some balls you poor excuse for a man.
I've talked to some people on the team who works on Edge, and they are a fantastic group of people.

They know they are in an uphill battle, and everyone is writing them off, but they are doing damn good work.

Edge's performance is getting leaps and bounds faster every update, they are doing incredible things for battery life on many devices, they are catching up to google for web API support, and nobody is taking them seriously.

I know nothing about what it's like to work at microsoft, but whatever they are doing with the Edge team is working. They know their product isn't perfect (what is?), and they are just trying their damn hardest to make it better.
When I'm working on some web thing in visual studio, I'll tend to have:

- a web browser

- framework documentation (another browser window)

- two or more code files (split editor panes)

- a separate window for various sidebars

And sometimes more (maybe another editor window), all open at once. Right now, that all gets a bit crowded. Even on a single 4k screen, it would probably end up slightly crowded.
Whatever floats your boat. My experience in large enterprise products is exactly the opposite, but I'm glad it works for you.
Everybody is different, of course. I have been taking an aspirin a day for more than a decade and do not routinely get nose bleeds. If I'm at a high elevation and it is cold, I get a nose bleed. But other than that I do not.
That's a fair objection. You can view my rule as a heuristic that's easy to compute and gives good guesses in most situations, rather than calculating the mathematically correct probability.

My AI does actually account for this, but only in the endgame when there are a small number of squares left -- then it considers the global configuration instead of just local. This works out because the endgame is where this problem is the most significant, it's computationally expensive unless there's a small number of squares remaining.
> So you disagree with TDD, but you need to rebuild your system from scratch every 5 years? I feel like this is an argument for TDD.

Not necessarily. If the rewrite is only addressing issues that would have been prevented with tests, then sure, this is clearly an argument for TDD. However, if the rewrite is going beyond what could have been provided by tests, then having a large testing system could actually make the rewrites harder, which means it's an argument against TDD.

It's hard to say which is the case without knowing the details, and I'd certainly err on the side of saying a yearly rewrite is not a good sign. But if a company is undergoing rapid growth, it's not that unusual for certain systems to be rewritten frequently as fundamental new insights are gathered about how to tackle problems that are hard to scale. And if the system isn't that large to begin with, periodic rewrites could be easier than writing a single version that's supposed to last 10+ years as business requirements dramatically change and expand.
Amsterdam Airport´s AI Program Streamlines Operation
For me AVRs stopped to be interesting around the time when Arduino gained popularity, which also caused significant price rise and also availability problems.

In 2010 for one-off art project (lot's of MCUs on RS485 controlling LEDs and pushbuttons) we had to switch from ATmega8 to AT89C2051 because it was the only MCU that we could source in time for the event for reasonable price and we had (semi-)reliable programmer capable of programming it (notice the 89C, not 89S).

After that I pretty much switched to MSP430 for such things.
Waymo has a big lead in driverless cars–but here’s how they could lose it
How do I get in touch with you?

I have a couple of ideas with legit legs. I am also pretty competent at implementing stuff.
I've been using Firefox's reader mode to good effect lately. I'd give it a try, or something like it for Chrome.
As someone who only has a fuzzy understanding of these concepts, this reply was enlightening. Thanks!
I think that everyone should have a 5 year stint with zero tests. I genuinely believe it offered me an insight into the deepest parts of depression.

In saying that, it was raw and I think I enjoyed my job more. There is no safety harness. You write decent working code and sign your name by it or you run home to your mothers nipple.

I definitely learned a lot about programming during that time. To take a terrible system and try to research ways to make it better for your own mental health, not the companies is a personal drive and golden age of discovery which plays a part of my programming to this day.

I get none of this from TTD. It is intensely dull and unsatisfying but gets the job done.
I would argue that the 2004 DARPA challenge was a failure with the best car, Sandstorm, only going 7 miles before getting stuck on a rock. That led to a do-over in 2005 that was really the first success.

https://en.wikipedia.org/wiki/DARPA_Grand_Challenge#2004_Gra...
My experience is with 100mg delayed release over 10 years.

And jesus, 500mg? Holy crap
It's almost playable with no hardware accelerated graphics.
Researchers Devise 2FA System That Relies on Taking Photos of Ordinary Objects
They steadily make their way into the mainstream. Silicon has been used in batteries for several years now, in low amounts. Usually the new "big news" comes with a significant gotcha. For silicon this has always been the cycle life. Silicon hasn't seen larger use because it expands by 400% when filled, compared to graphite's ~12% expansion. This though- this is very cool. If they've actually demonstrated 100 cycles in a pouch cell, made with reel-to-reel, that may mean that commercial cells are <5 years away.

Commercial cells have 500-800 cycles in their lifetime (until their capacity falls to 80%) and are universally made on reel-to-reel machines. There are a ton of difficulties moving from a coin cell to a prismatic/pouch cell to a cylindrical cell, but I can't understate how encouraging it is that they got to 100/400 cycles.

> Are there any good websites to gauge battery development progress as opposed to the vital, but often ephemeral research progress.

Not that I know of, sorry.
His "recommendation" stems from a DDoS incident, and possibly, a hack.

https://news.ycombinator.com/item?id=10998661
It is my understanding that this is like Invision but for chatbots. The cool thing would be integrating this with something like Dialogflow (previously known as API.ai)
> I appreciate your answer, but the destructiveness of the reward loop is directly addressed in the PDF.

I've gone back through most of the PDF, and I can't figure out what section you're referring to. There's a bunch of discussion of perverse incentives (mostly involved incompetent managers or painfully sloppy developers, who will fail with any methodology), but I don't see where the author addresses what I'm talking about.

Specifically, I'm talking about the hour-to-hour process of implementing complex features, and how tests can "lead" you through the implementation process. It's possible to ride that red-green-refactor loop for hours, deep in the zone. If a colleague interrupts me, no problem, I have a red test case waiting on my monitor as soon as I look back.

This "loop" is hard to teach, and it requires both skill and judgment. I've had mixed results teaching it to junior developers—some of them suddenly become massively productive, and others get lost writing reams of lousy tests. It certainly won't turn a terrible programmer into a good one.

If anything, the biggest drawback of this process is that it can suck me in for endless productive hours, keeping me going long after I should have taken a break. It's too much of a good thing. Sure, I've written some of the most beautiful and best-designed code in my life inside that loop. But I've also let it push me deep into "brain fry".

> No amount of TDD will solve you getting half-way through a design and then finding you needed many-many because you misunderstood requirements.

I've occasionally been lucky enough to work on projects where all the requirements could be known in advance. These tend to be either very short consulting projects, or things like "implement a compiler for language X."

But usually I work with startups and smaller companies. There's a constant process of discovery—nobody knows the right answer up front, because we have to invent it, in cooperation with paying customers. The idea that I can go ask a bunch of people what I need to build in 6 months, then spend weeks designing it, and months implementing it, is totally alien. We'd be out of business if it took us that long to try an idea for our customers.

It's possible to build good software under these conditions, with fairly clean code. But it takes skilled programmers with taste, competent management and a good process.

Testing (unit, integration, etc.) is a potentially useful part of that process, allowing you to adapt to changing requirements while minimizing regressions.
If I wouldn't know better, it sounds like we live at the same place!

I get you - that your work is likely higher quality, and you could claim ignorance if anyone did have a complaint.

But yeah, on Sunday, I redid some of our outlets and switches. We live in a trailer, and some of the switches were getting intermittent, and some outlets were loose to the point of turning off stuff if they jiggled. But.. I did find out that 1 outlet in the bathroom, the hallway lights, and 1 wall of the living room were on 1 gang... (sigh). I have my work cut out for me if I actually want to do it right.
My point is that those transpiled languages aren't that stymied. You can use them without a lot of problems, and they're being left on the bench for reasons other than their feature set.

Companies generally choose JavaScript because there are lots of developers to choose from, it runs everywhere and the ecosystem is huge.

Engineers choose something like PureScript as it's not a 'blub' language and people think that by choosing it they will be able to hire (or be seen as) "math geniuses". I'm sure the feature set is important, but it's not enough to unseat a language with the previously described properties.
It was 13 years from the Wright Flyer to the first commercial fixed-wing aircraft. And that was still very dangerous. Jet engines (which really introduced the safety we are used to in airlines) took 50 years.
you sound kind of salty about Google not hiring you.

More likely your interpersonal skills were not up to par with their standard. Raw technical ability matters, but so does your ability to work with others.
Hi, off topic but-- my father had these, several a year for two decades. Some mornings we would wake to a note on the counter that said something like "Kidney stone, at the hospital."

That being said-- the trick for him turned out to be stopping soda, and keeping a water bottle by his bed and drinking a gulp of water everytime he woke up-- basically staying hydrated during the evening, and at all other times.

Just wanted to mention this in case it was of any use. Also, keep an eye on RCC. :-/
Except that in my experience, unit tests just end up being a big ball of mud too. And at that point, they don't make refactoring easier, they actually make it harder.

Having good integration tests means that you're free to completely re-organize your code, and you can still test that it works as expected.

Given that requirements change over time, even a well thought out code structure will likely need to be refactored at some point, and being able to have a test suite that doesn't have to be re-written during a refactoring is extremely valuable.

I've also seen code bases become unnecessarily complex because so much thought was put into how to unit test it, that not enough thought was put into writing clear, easy to understand code.
I have been doing web app error tracking and debugging wrong all these years
NetWorx 6.0.4 Crack and Serial Key (2018) Here Download
This was actually the very sole purpose of this project. There are numerous similar products out there. Oh god, it took me hours and maybe days to learn them. So I made Captain for people how do not need super advance configs, to be able to deploy apps easily.

I am so glad that someone actually found it useful :)
Basically, you must understand that you are fighting against yourself. Each day, you fight your former self. You must WANT to become better. The best thing for that is to code a lot (:important) & reread your ancient code (:super important). You will fall in ALL the pitfalls, at first. And then, you will learn to circunvent them. And then you will learn to draw straight lines between the pitfalls, and things will start to become clean. At the end, like Neo in the Matix, you will no longer see the pitfalls.

(And then, you will learn FP and you will have to relearn everything. And then Haskell... And then...)
Very good slide here:

https://github.com/matthiasn/talk-transcripts/raw/master/Hic...

Caption: "The problems of programming"

And you can call them problems, and I'm going to call them the problems of programming. And I've ordered them here -- I hope you can read that. Can you read it? Yeah, ok. I've ordered them here in terms of severity. And severity manifests itself in a couple of ways. Most important, cost. What's the cost of getting this wrong? At the very top you have the domain complexity, about which you could do nothing. This is just the world. It's as complex as it is.

But the very next level is the where we start programming, right? We look at the world and say, "I've got an idea about how this is and how it's supposed to be and how, you know, my program can be effective about addressing it". And the problem is, if you don't have a good idea about how the world is, or you can't map that well to a solution, everything downstream from that is going to fail. There's no surviving this misconception problem. And the cost of dealing with misconceptions is incredibly high.

I'd suggest to consider the diagram cited above, it is a good representation of where the real difficulties lie in programming.
I've never had one, and it's as difficult for me to understand why people think they need one, as it is for them to understand how I survive without one.
The story doesn't end there: aspirin is an irreversible inhibitor of a platelet aggregation pathway.

So its effects last longer than the circulation of free aspirin in the bloodstream.

Its effects last until the enzymes in that pathway get regenerated. The enzymes' turnover is over a period of several days.
"The first is that most of the analytic data for describing the class of smooth manifolds can be encoded into certain fibre bundles on manifolds: namely bundles of jets (see also jet bundle)."

Oh, mathematics, you are crazy.
Facebook Phishing Targeted iOS and Android Users
Indeed, those are good ideas for improvements! It's hard to say whether they will improve the AI, as in both cases you're replacing one heuristic with another heuristic. You'd need to implement it and experiment with it -- and I haven't done so for my AI.
Why didn't he use firefox?
Goodcover (YC S17) Is Hiring a Claims Manager to Rebuild Insurance
Goodcover is building the next generation of personal insurance focused on clearer pricing, better coverage and returning unused money back to our customers. We set out to do this because the insurance industry’s incentives are wrong, no one should profit on someone else’s misfortune. Our aim is to be the fairest home/condo/renter’s insurance company for the 21st Century.

Role:

Own the claims management process at Goodcover.

Design the claims customer experience in collaboration with the CTO to ensure that Goodcover clients get paid what they deserve, in full, as quickly and painlessly as possible.

Set up a Third Party Claims Administrator management procedure in collaboration with the CEO and execute on it.

Give comfort to State Regulators through communication as needed.

Requirements:

4-5 years of Homeowners Insurance Claims experience

At least some experience with each part of the end-to-end claims process

Able to flourish in an unstructured environment

Passion for reforming the claims process to center on customer outcomes

Bonus:

Experience with insurer’s digital transformation initiatives

Experience with managing Third Party Claims Administrators

Apply at jobs@goodcover.com

Referrals to good candidates welcome!
You should read all the context before stating that this comment thread means the system is broken. Just because extremely self-motivated individuals now have readily available resources to learn almost anything on their own does not mean the system is broken for everyone else.
> nobody is taking them seriously

Because it's 2017 and I'm STILL having to write workarounds for IE.
does University of Michigan count as a top college? It's not an ivy league or stanford/mit/caltech
The headline is clickbait. The town has a population of 1,100, so it's not a ghost town, and the article mentions Tesla exactly once, in what's basically a side note.
As Albert-Jan and I discussed at PyCon this weekend, the long-term future for Skulpt quite possibly involves compiling to WASM rather than Javascript. This is very unlikely to happen until every modern browser supports WASM. Neither Trinket's educational mission nor Anvil's "web apps for the world" mission are compatible with leaving users behind just because their workplace or school runs IE.

The runtime can be remarkably small (Skulpt is 228kb minified and gzipped, including the standard library), so I think it's a feasible target. (Pypy.js is, of course, enormous!)
Raise the child, build a business from home.

I would sign for it in a heartbeat.