skysight-inc/HackerNews huggingface dataset:
> I understand why an academic thinks this is a good idea. More jobs for the boys.

This isn't fair. Academics usually have a true love of their subject and desire to teach that to the next generation.

>Third, try explaining programming without computers to a child. There are so many abstract concepts...it is just insane.

They teach many abstract concepts. The current curricula for many subjects are already full of abstract ideas that we expect children to learn. Programming is basically functions, logic and basic algebra. It's not remotely difficult to teach these to children.

>Fourth, this feeds into the aspect of British culture that reveres irrelevant knowledge (and despises practice). Nowhere is this more evident that in CS departments. Example: the UK has great CS depts but no innovation within business. The university local to me has a top ML department, they have been doing speech recognition since the 60s...all the PHds leave, there is only one speech recognition startup in the city...and that is govt-funded afaik. Taking advice from people like the OP is suicidal.

I think this is wrong. Developing strong theoretical understanding is not pointless. You can't have innovation without theory. I agree that maybe the country needs to apply that academic kowledge better to money making endeavours, but I don't believe that keeping the education system as it is now is going to help. We need more numerate people with detailed knowledge of scientific disciplines in order to drive innovation.
There's no way the Secret Service could enforce that rule. Freedom of the press applies - the best they can do is avoid having the President eat in public.

Politicians looking goofy eating (eating pizza/hot dogs with a fork is a pretty common gaffe) has a long history. https://www.theguardian.com/lifeandstyle/2015/apr/19/photo-p...
Using $this was just a simple example where all three cases could easily do the same. Make it $bar :)

Anyways: People are capable of writing loooooong expressions (chaining with && can be good to handle errors from multiple operations in one place (till you have to figure out which specific condition broke)) Thus "single expression" isn't neccisarily short ;)

Anyways: Point is "it can be useful, but developers should think, what they are doing" Perl's "there's more than one way to do it" probably goes too far, but being able to focus on the relevant parts and being able to providing the amount of context needed are good things.
Whoa. Posting like this will get you banned here. Would you mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the spirit of this site to heart? Basically: yes to thoughtful and curious conversation, no to being a jerk and snark.
Thanks for getting my username right. ;)

You specifically got one detail wrong: it's not just for analytics tools. It's the adtech industry in general using this technique, and Adobe offers its analytics as part of its marketing software suite.

From their own site: "What is Adobe Experience Cloud? It's a collection of best-in-class solutions for marketing, analytics, advertising, and commerce."
Out of curiosity, did anyone actually ask expressly Richard how he voted and why he voted this way?

I mean, escusatio non petita, accusatio manifesta:

https://en.wikipedia.org/wiki/List_of_Latin_phrases_(E)

or "he who excuses himself, accuses himself"
1. Be thorough. Be sure you fully understand the issue, instead of jumping to conclusions.

2. Keep asking 'why'. Make sure you understand what the problem (or rather the requested feature) is, instead of being able to parrot what someone else says the problem is. (Even if the conclusion ends up being the same, you need the gained comprehension to determine the right solution.)

3. Separation of concerns. Keep practicing on separating orthogonal concerns that are all seemingly relevant to a problem. Evaluate each concern separately. Drop any of the concerns that are irrelevant in solving the solution. This can save you huge amounts of time, enough to make a deadline you would otherwise never make. (This will also help you to reduce the amount of added complexity.)
Big picture: experience is the main way to get better at this. That, plus watching what more experienced folks are doing.

In terms of smaller strategies:

I think stepping back and asking "What is the real problem that needs to get solved here?" is very often the best thing to keep in mind when I'm stuck. Along with "How important is this, really?" These kinds of questions help you to evaluate whether a particular technical roadblock is actually worth solving, or whether perhaps it is not worth the time investment because some other solution (or just walking away) would be a better choice.

Also, I don't know if you need to hear the clichés, but context switching is a huge and important strategy for problem solving — whether rubber duck debugging, talking to colleagues, switching to another medium for thinking (like a white board), or just going for a walk around the block — these are often good ways to get unblocked.
Hardly. Microsoft did the same thing (or even started this trend) with Windows 8 but finally recognized they were wrong and did a almost a complete 180 with Windows 10.
One thing that would put you in a stronger negotiating position would be to get multiple job offers for remote jobs that you are willing to take. Then you are less likely to need to accept a salary that is high compared to local job market but low compared to international remote job market.
The Saudi government was the major investor. He pays them back with positive PR.

It becomes tricky when he mixes Vision Fund business with SoftBank business.
So, first, airliners aren't really expected to experience more than 1.3G's of loading in normal or even unusual operation.

They are expected to be able to survive 2.5G's (limit load) without structural damage. The 777X satisfied this.

They are expected to be able to survive a few seconds of 1.5x this-- 3.75G-- without outright failure but possibly with (irreparable) structural damage. Instead, it catastrophically failed at a loading corresponding to 3.70G's.

They are going to reinforce and fix the specific failure that happened at 3.7G's, and make an argument based on strain gauges and instrumentation that another, distant failure was not likely before 3.75G's.
Release 0.8 of MOSP is out with generation of MISP galaxies and clusters
Of course, that’s precisely my point. You can easily read about PRISM, and yet the government wasn’t held responsible and presumably didn’t change its actions, so it appears that censorship simply wasn’t necessary.
I will add one precursor for those stuck in analysis paralysis....

Make it.

You can't make it work if you haven't made anything.
Failing and redoing. On what doesn't really matter, I've found, just pick any area and don't be afraid to redo whatever you were doing.
SoftBanks next big crisis may be brewing in India
iCloud Bypass Pro – iCloud Lock Removal 2020
If there wasn't a risk of a high price to be paid by the heroic individual, it wouldn't be very heroic.

Also a friendly reminder that, for instance, Edward Snowden is hiding in Russia of all places from a possible death penalty.

Capital punishment for an ultimataly selfless act, motivated by his moral code and love for a country that very much would like to see him gone for good.
would like if they'd just change the syntax to foreach(something as k,v) or $arr = ['something':'value']... or then could use => ...or they could just use -> and change -> to . notation.. I use js a lot more lately so having it closer resemble es6 would make jumping back and forth easier.. I often start writing a json object when I want an associative array.
> ...where it makes sense to do so.

Certainly being able to trace code is one skill, and knowing how deep to go is another.
Or when they stop actually using tracking cookies.
Quantum Supremacy Will Be Re-Achieved Again and Again
> If only Jolla devs had kept their promises of open-sourcing more of their code.

I think that's a big part of the answer to why it hasn't caught among techies. When I tried using it (shortly after release), there were numerous issues in their default apps that nobody could fix because they are proprietary and Jolla didn't seem to have the resources to handle all the bugs.

I'd wager that if it had been open source, the early adopters would have put some time in to fix a lot of the bugs.

In retrospect I'm pretty pissed at them for not being honest and upholding their promises. In my book they're basically con artists that just tried to get the Linux community's money by saying "open source" without actually meaning it.
Well, if there's a 1-1 map between GP and NNs, shouldn't we be able to determine the effect of a gradient descent step on a GP by combining the two maps?

I have only barely glanced at the paper mind-you, so I couldn't say the details but still.
You seem to be forgetting LineageOS
That's certainly a valid concern! From my perspective, the programming skills in these job descriptions are one requirement among many others, and I'm not sure how much weight it really has in the hiring process for these roles, especially if your other skills are a good enough match.

We do have this note on all job pages, which maybe should be more prominent:

> Avoid the confidence gap; you do not have to match all the listed requirements exactly to apply.

Some amount of general programming experience is definitely required though, since SREs and DBEs frequently have to dig into our codebase and things like Ansible runbooks. And especially regarding SQL, a lot of it is heavily abstracted not only through the Rails ORM but also our own code.

Found some other jobs that focus less on programming, though we don't have current openings for most of these either:

- https://about.gitlab.com/job-families/engineering/cloud-nati...

- https://about.gitlab.com/job-families/engineering/infrastruc...

- https://about.gitlab.com/job-families/engineering/monitoring...

- https://about.gitlab.com/job-families/engineering/security-e...

- https://about.gitlab.com/job-families/engineering/vulnerabil...

We don't seem to have a good overview of all roles, I found these through https://gitlab.com/gitlab-com/www-gitlab-com/tree/master/sou... :)
>It doesn't generally help with big systems design

What do you think helps specifically with that?
It's good for tech that the public market's response to WeWork has brought some well deserved scrutiny to SoftBank. Their investing behavior over the last several years has pushed up VC valuations to unhealthy levels and contributed to this "Unicorn or die" startup culture.

A high private valuation alone is not an accomplishment. While revenue growth, happy customers and a clear path to profitability are accomplishments worth celebrating. Hopefully after this SoftBank fiasco more startups and VCs will focus on fundamentals more than jaw dropping valuations.
Always asking "why".

No one will ever successfully transfer the problem in their head to your head first try. You will need to ask a lot of questions to try and bring your understanding near their understanding.

Equally you need to actually understand why the problem you're solving is a problem. If someone wants the header on their website to be bigger, that's a very easy thing to do but there's always a reason why they want it bigger and knowing that will help you do it properly.

Also, always ask why whatever solution you came up with works. There are very few situations where the actual answer is "Invoke these magic runes in the right order and pray".
Spending the time to find out what the magic runes are and what they do will help you make sure that
a) The problem won't come back
b) Your solution is actually a good one
c) You can solve similar problems in the future.
I don't see where criminal fits in aside from the fact that a sabotage of that sort would rightfully be hideously illegal. What is to gain personally from that destruction?

It might be a pedantic quibble but I can see power as the only "rational" sabotage motive. Which could include some disgruntlement. Either to oust management or rivals to gain control or possibly international politics where one thinks they can gain from the loss of the colony for the sake of their earth nation.

Suicidal can be taken as granted to be irrational and disgruntled relatedly as "so fed up they want to see everything collapse to make them suffer".
Man, what a wasted opportunity. If it had happened on a workday, we could have seen a massive productivity surge to boost the economy.
>You don’t mention any kind of inquiry but you go out of your way to tell me that I shouldn’t be saying anything?

People do that because they hope to god that folks with a psychosis (or to use your other example, cancer) aren't trying to cure themselves by changing to a keto diet, unsupervised, and without the aid of a professional.

Here's the problem : You're reinforcing the uselessness of professional medical care ("they ignored me and did nothing!") while reinforcing the positive idea of being able to 'cure' yourself with diet (a 'cure' that is only sometimes sustainable, and results in a rash, you say.), and spinning the act of rejecting prescribed drugs for your ailment as positive.

No part of you thinks that it is irresponsible to tell potential psychotics to cure themselves with diet and reject their drugs, since the professionals ignored your pleas?

It's irresponsible to offer up unproven 'cures', especially to a group of people, the psychotic, that may have an already tenuous grasp on reality as it is -- if there ever was a group of people that should have someone supervising their self-medical-experimentation, it's the psychotic.

I appreciate your enthusiasm for a treatment that helped you. I implore you to consider that such things are highly specific, and that medical professionals, often times at the expense of seeming aloof, are often 'looking at the forest, not the trees" with regards to your care. Many are unwilling to explore experimental treatments until the (long) list of exhaustive known procedures for your ailment has been checked through.
Fixing bicycles.

all the normal pain points are there: proprietary standards, 16 standards, major tooling fights, bandaid fixes that “we’ll refactor later”, tech debt, etc.

But the architecture is really really visible. And when you’re done you have a bike!
> That internal state is where moral judgment and discernment live, so it’s hard for me to see how that would systematically produce harmful or immoral actions.

I had a therapist who basically told me that mindfulness means accepting harmful and immoral actions (of others). On the one hand this does make it easier to go through the day without getting caught up in q
Start at the bottom, make your bottom layers solid first.

You can't reliably deduced anything about what your current problem is, if the things it depends on are flaky.

Design by Contract. Understand it. Used it. Turn your asserts on always.

Turn on all warnings that don't give false positives that your compiler / tools provide.

Fix them don't mute them.

Run around your code base and find every damn place where some damn fool has discarded an error code and check and report all failures.

You'd be flabberghasted by how many "it's impossible" bugs I have found and fixed by that one simple action alone!
How this should be done was the big roadblock, the actual inlining was a relatively simple patch.
The test on the Boeing 787 broke the load test machine - the composite wing was so strong, they literally couldn't break it.

And let's just put this on record, so people can really shut up about this: The Airbus A380 failed at 145% maximum wing load. That's a full 3.3% below the safety margin. They did not retest, but did subsequently reenforce (just as Boeing is here). The plane was put into service by the FAA.
The modern one is fantastic quality. The quadrivium and trivium. Really incredible.
That sounds like we should just test for IQ.
That email is so vague that it makes me think the situation is far worse and they're just feeding a "nothing to see here" story just before a holiday weekend in the US. A compromised marketplace would be a great means of sprinkling nefarious code into packages during deployment. I hope my suspicious are proven to not be the case, but only because of all the people locked into Magento relying on some dev shop to keep their business going.
This is explained in the book:

“Successful branding stories are often characterized by disruption, which turns an established industry or experience upside down. The MBSR brand is one such disruptive force, with Kabat-Zinn’s talking points including pithy quips such as: “The Buddha wasn’t a Buddhist,” or Buddhists “don’t own mindfulness” because it is “an innate, universal human capacity.” Potential customers are thereby assured that MBSR is a non-religious product, yet still offers the best bits of what the Buddha taught. In Kabat-Zinn’s words, his version of mindfulness is “a place-holder for the entire dharma.”

The Western world has co-opted an aspect of Buddhism, which works to improve productivity, and discarded the part that doesn't fit its worldview; the other pillars of Buddhism. This enables it to be sold as non-religious.
Maybe a part of the mission is to design a society to minimize or eliminate violence, mental illness, crime, etc. What would a society look like that depends on near-perfect harmony and peace for its very survival?
Of course, the previous CEO Brian Cute of PIR (the non-profit) was previously "Vice President of Discovery Services" at Affilias, the for-profit that they are paying to do PIRs job.

Basically, everywhere you look, you see a bunch of blood-leeching ticks on the internets backside.
The group? You mean the common denominator - they ought to grow thicker skin. The CoC is a ridiculously unnecessary and shallow piece of text made to make one transsexual famous.
Speak about yourself. I make good use of my time. So I want more. I don't want joint pains of old age, wrinkled face, or slow brain. I want eternal youth.

Give me immortality or give me death
Back in 2017/2018, not at all surprising. I don’t see that kind of opportunity in the crypto markets anymore though, they’ve gotten a lot more efficient. Used to be able to scalp 1% on big price moves in altcoin futures at least once a week, now the prices move in lockstep with spot.
Yes, exactly! If I gave up on my language's debugger or compiler every time I was troubleshooting something because I didn't trust it, I'd waste an absolute ton of time. I think finding a balance is important, but also not being afraid to consider the possibility that libraries, browsers and tools that you generally don't consider flawed might have their own issues.
a few principles I've found helpful:

There are no coincidences, unless proven otherwise.

If something smells wrong, it probably is. Trust your gut.

Make sure you're building the right thing, before you build the thing right.

Don't be clever. Elegant one-liners that make you feel like a genius when writing it are probably not very maintainable.

The second best piece of code is the one you just deleted. The best one is the one you didn't write in the first place.

Plan to fail, and gracefully degrade.
1. Read a lot.

2. Write a lot.

3. Read more and pay attention to how it differs from your writing. Figure out what you need to improve.

4. Write a lot more.

Repeat.

In all seriousness, that's the base habit of all journalist, non-fiction and creative writers. There's an adage that you become a decent writer after you've written your first 1 million words. It took me about 1.5 million before I put myself in the decent category. My last 100 thousand have been very deliberate practice, which puts me at an almost-good level of writing.

Extra tip, fear not the editing phase. Let your writing ferment alone for a week or two. Then come back to edit. Once you've racked it, let it age just a wee bit more. Edit it again once or twice more. Then you do a typo read through.
The bottom will have to be lined anyway, because the Martian soil contains a high fraction of toxic perchlorates.

This is also bad news for trying to establish any sort of agriculture.
Won't any plastic surface on Mars collect dust and thus become opaque over time?

This was too a problem on a mars rover solar panel, can't remember which one.
The Value of Good Feedback
I am currently looking for a job as a junior frontend developer, I have two years experience in the field and I would like to learn more and more about it.
When a job interview arrives I firmly believe that preparation is the key and I spend hours researching about the company, current projects, company culture, etc.
The first time I get in touch with the company, the first filters are passed without any problem and I always get the second interview, which is normally a code test.
When I prepare to do the code test, I spend hours working on the solution even days and send it properly to the future company.
For now, they have sent me an email saying that I have failed in the solution or that they have chosen another candidate with more experience which leads me to keep searching and learning from the code every day.
What I see in these emails is a predefined response and they are not loaded with any kind of feedback to help me improve as a developer. This frustrates me because even if I answer asking openly for feedback, they simply don’t answer about the points I missed or the points I didn’t get to the next round for.
I think this is a severe mistake on the part of companies like takeaway.com because I think they take advantage of being big to treat the candidates like shit and not giving them good feedback.
I’m tired of working on solutions for free problems and do not explain to me in which points I have failed and why I do not move to the next round, so I openly ask that these companies become aware that behind the typical email we do not hire you, there could be a because, point by point listing the errors by the technical team, because I believe that feedback is important to work in a company throughout the process, whether as a candidate or worker.
That’s why as developers we should demand from companies good feedback or that code tests are paid.
This is a simple thought from a junior developer.
What do you think about it? Give me good feedback!
This sounds mildly interesting, but you make a lot of grand claims and support none of them. I would love to read about your concerns more deeply in a longform, where all these ideas can actually be related to one another, and with support for your claims based in data and real world examples. I would suggest you do this for your own mental health, because it's not at all clear to me why the world of (let's call it) 'socialized investing' is a better world than our current one. And I think you should at least have a well research model to base your concerns in before they "dominate your psyche."
The Value of Good Feedback
So you have no place in the market with this destructive mindset.
There is an associated github repo with code for those who want to reproduce results (https://github.com/trailofbits/sixtyfour). Or if you’d like to contribute an ARM version :).
I find twitter to be quite usable in mobile safari. I have the app too, but usually find myself still browsing in safari.

Quora is just a broken site right now, mobile or not.

reddit OTOH still seems to work okay on desktop. For a plaintext discussion forum that I prefer to read anonymously, theyve reaaaally screwed the pooch on mobile. I aboid reddit links whenever possible now, which is... sad.
IMO I find the regular mobile version of Reddit as bad as the AMP.
I just ended installing an unofficial app (boost) for whenever I wanna browser Reddit on mobile.
Yani doesn't cite Firefox. I think Turkcell is violating the license.