skysight-inc/HackerNews huggingface dataset:
i agree with the author in that i personally don't like code reviews much as well, though i agree they are valuable.

to be more specific though, i don't like "remote" or "detached" code reviews much; "over the shoulder" code reviews are a completely different thing. as you can actively communicate with the author or the reviewer, it tends to reduce the bike shedding a lot and the value of positive feedback increases.

i guess, ultimately, it depends on the team; if you're operating well together, classic code reviews might work as well. if the team is new or the members have varying styles or levels of exerience, over-the-shoulder reviews tend to pay off significantly.
Ain't it great to have a choice? Each has their strengths and weaknesses, and have different feels. Just install all three, and see which one suits your style best.
Well, that is the result we got from turning Universities from public knowledge centers into private for profit IP accumulating businesses.
The history went something like this:

jk
</sarcasm>
<sarcasm>...</sarcasm>
</sarcasm>
/sarcasm
/sarc
/s
\s
The biggest problem is most companies hire by ticking boxes. On the other hand, a developer is a developer. Yes, it will take a while for them to adapt if you hire a "Ruby developer" to do, say, embedded systems, so yes, it makes sense to check for patterns, but trying to match a profile is a somewhat unreachable target and useless to begin with.
10++ TypeScript Pro tips/patterns with (or without) React
Me and my collegues like to talk about the "back-end of the frontend". This includes all the client-side logic and scripting. You have a server-side application primarily consisting of validation and data storage concerns, and a back-end of the front-end implementing some business rules etc.
1/2 mv^2 = mgh, so v = sqrt(2gh).

If all potential energy from an altitude of 5000 ft = 1500 m got converted into velocity, we'd talk about 170 m/s or about 330 knots (and a free fall from that altitude would take about 17 seconds, t = sqrt(2h/g)).
A quote about women in technology
It might be true that latency can't be improved much by using an off-the-shelf FPGA but performance in parallel processing tasks can. For instance an FPGA might be cheaper than a GPU (in relative performance/$) in machine learning implementations because the FPGA architecture can allow for higher throughputs/less bottlenecks.
How about a novel concept: there will always be some parts of your job that you don't enjoy. Tedious things, boring things, annoying things. All the different check lists, beurocracy, reports, task tracking - there are a lot of annoying little stuff that we sometimes have to do.

Some of those things can be optimized or automated away. But some of those things can't: turns out, although they're completely irrelevant 98% of the time, they're completely critical in the remaning 2%, and nobody knows what those 2% are, so we're stuck with these practices.
I remember that - _many_ years ago, ten maybe? - when I tried to use D for OS development, I was forced to use GCC because it was the only one who supported custom linker scripts IIRC. Nice to see that all the projects are still doing well!
Montreal doctors write prescriptions for free museum visits
"Abandoning you allowed to think of sharp approaches to incorporate the code behind the interface with your application."

Lack of editing standards will forever limit Medium's credibility as a publisher.
I've worked in teams bad enough to make code reviews a real pain.

I've seen pretty horrible code constructs that actually seemed to work without bugs. What should I say? That the author of that piece of code should completely rewrite it to my taste? It would not only frustrate him/her but also slow down the entire team. So I often accept what is rubbish IMAO. And not me alone, have you ever seen two code-buddies in a team always doing each others code review and(quickly) accepting and merging everything they produce before anyone can make a comment?

I've had numerous pointless discussions about why I wrote a specific piece of code where (a junior dev) the assessor just wanted me to do things by the book as he learned it, not really understanding why I did it that way. But there was no way to convince him, it ended up in an unresolved conflict that I only could solve by messing up my code to his taste.

All these pointless discussions that particularly affect the relationship you have with your co-developers in the team you work in, are not always fruitful and can be quite destructive if you're not careful enough.

I do believe code reviews can be very important and valuable, but at the same time I've seen huge amounts of wasted time and frustration for nothing. It's not always and only a good thing is my conclusion, it depends on the variables.
Not that this applies to your particular situation of course but I have seen places where that duplication was actually warranted - especially in css. E.g. some code was extracted and reused when it was not meant to, just drying the code up, but those things turned out not to be the same thing and it was rather painful when we had to change them independently.

As to your particular case - I’m sure the politics of the situation were pretty bad but I’ve solved situations like this by having two separate commits/prs one that uses the old style to fix a problem so the change is obvios, the other to change all the old style to the new style of code. Helps the reviewer understand what’s happening and move the PRs along. Though this was in a much more liberal code review environment of course ...
Pretty sure malwarebytes would catch this. Or any AV.

Malware like this targets the lowest hanging fruit I guess.
This is not a novel, but it's a traditional oral tale (from Tao Tö King apparently). I've heard it several times from different storytellers. It usually lasts about 2-3 mins, no more.

But the original article is not especially about novels, it's about stories in general. Cinderella is mentioned in the article, as a story archetype, and although longer, it is not a novel either (and would be pretty boring as a full-length novel).

So, sure, it's not a novel, but is it a story? My point is, it's very debatable. Most people, me included, would say "I heard a story yesterday, about a poor man who bought a horse, and..." But it does not fit the usual, ultra-simplified structure of a story (a conflict, and then a resolution of the conflict).
Do you mean for individuals or for countries?
Search HN for similar questions
> Frameworks like Angular or libraries like React require developers to have a much deeper understanding of programming concepts; concepts that might have historically been associated only with the back-end. MVC, functional programming, high-order functions, hoisting... hard concepts to grasp if your background is in HTML, CSS and basic interactive JavaScript.

Well that's the difference between a frontend developer and a designer... I don't think fronted dev has changed that much. frameworks have, but the core of the role is the same: understanding/organize ui states, understanding threading models, events, interact with backend apis, know some design, etc.
FTA :

>>> - VLAs within structures is not supported by the LLVM Clang compiler and thus an issue for those wanting to build the kernel outside of GCC, Clang only supports the C99-style VLAs.

one less vendor lock in (but since it's GCC, it makes me sad).
Of course having access to the private key, need to be the most basic way to access funds. It's the only thing that's guaranteed to be uncensorable, while minimizing the requirement of trust. It is a big responsibility though, and should not be taken lightly. The crypto-currency community is partly at fault here, for blaring memes like "If you don't control your private keys, it's not your Bitcoin", without any regard for whether or not people are ready for that responsibility.

That being said, there are number of ways you can store your crypto-currency, with varying degrees of trust-minimization:

- Use a multi-signature smart contract wallet, where a master key has power to move the money. If the master key is lost, the money can be moved by X out of Y keys signing off on the transaction. You can then distribute the Y keys to your trusted associates, preferably without telling them who the other key-holders are.

- Use a dead-hand smart contract wallet, where the money can be retrieved by a trusted associate, if the dead-hand switch hasn't been activated within Z amount of time. Can be combined with the above, in case further trust minimization is needed.

- Store your crypto-currency at a FDIC exchange. Pretty much the same model as the banking world. This really should be the go to way for the average Joe, as it mirrors what you currently can expect from online-banking.
The Inspection Paradox Is Everywhere (2015)
no, it would not have worked in this situation. the problem was really the reviewer who could not be gotten around.
Well, ICAO rules establish who runs the investigation, namely the civil aviation authority of the state of occurrence. Other states (state of registry, operator, manufacture) might participate, or the state of occurrence might choose to delegate to them. But the official responsibility for the investigation lies with Indonesia for now.

https://www.icao.int/about-icao/FAQ/Pages/icao-frequently-as...
Which one is it then? Oedipus? Cinderella? Man in the hole? That story looks like a perfect sine wave, and has no defined ending (I heard it with more or less steps). It does not fit any of those 6 predefined patterns.
AWS On-Demand Capacity Reservation
I'm going to suggest that it's on the universities to find a way around that problem. It's a real problem, but everything being publicly available online is how the world is now. Just varying assignments every year should be enough. If reasonable variations don't make the assignments challenging enough? Well the students are always going to be able to find some reasonable variation online. Starting from absolute scratch is just not a thing anymore in most fields.
Silicon Valley’s sovereign wealth problem
> I've had numerous pointless discussions about why I wrote a specific piece of code where (a junior dev) the assessor just wanted me to do things by the book as he learned it, not really understanding why I did it that way. But there was no way to convince him, it ended up in an unresolved conflict that I only could solve by messing up my code to his taste.

I've left the place I worked at for over 3.5 years over stuff like this adding up. Starting at my new job in a few weeks, getting paid more than I did at my previous job and will be working with people more senior than in my previous team. All in exchange of the rapport I've built over 3.5 years.
my jaw literally dropped at 3:12. https://youtu.be/laApNiNpnvI?t=192
I still can't figure out how they managed to get the camera quality/resolution in '91. I'm guessing that it's just an image rather than conversion to text if it's a paragraph.
[edit] what happens is copy and paste from a book on the desk to the computer clipboard. where the opposite corners of the physical screenshot are defined by two fingers creating a rectangle screenshot area
Does it JS really have that much traction on the backend? Maybe outside of Denmark, but our little department is actually one of the few places which uses Node for serious backend application in the entire country. At least that I know of.

I mean, I can go on job databases or LinkedIn right now, and there isn’t a single full stack JS job available in my entire country. There is a lot of JS including jobs of course but they all require you to also/mainly do C#, JAVA, PHP or Python because JS is almost exclusive used on the frontend.

Don’t get me wrong, I actually really like the JS environment. There’s a reason we moved to it, but it’s not like it doesn’t have its flaws either.

I think WASM will absolutely change web development, but I think it’s already made it to the is, I mean, we’re launching our first minor Blazor app this week, and it’s something we typically would’ve build with vue and graphql Apollo, but now it’s all C#.

The world of enterprise typically moves slow though. We’ve recently bought an on boarding system that’s made with web forms for instance. You may laugh at that, but the truth is, at least in my part of the world, that JS hasn’t seen that much adoption outside of hobbyists. Eventually these companies are going to upgrade their client sides, but would you pick modern JS or full stack C# if you were coming from web forms? Hell even if they go vue, react or angular chances are they’ll still use .Net on the backend, as that seems to be the trend pretty much everywhere except for us.
Excellent rejoinder. FWIW, GP reflects this tendency I've seen more than once to assume that specific US aviation rules or conventions apply everywhere.
IBM has such a large portfolio that you are probably hard pressed finding an OSS project that doesn't compete with an IBM solution.
> 3) If I'm in a hurry and the author is available I grab them and do an over the shoulder review. You might be surprised how much time this saves.

One concern here is you may ask questions whose answers are then given to you, and you alone. If it's likely someone else in the future will have the same questions, the "answers" should be in the form of improved code.

> 4) Don't struggle with difficult sections of other people's code unless you have a vested interest in remembering this specific section of code. Ask about unclear areas.

I'm not clear on the distinction between "difficult sections" and "unclear areas"? Either way, one of the outcomes of the review should be to make life easier for the folks that follow us.
I Might Be Spartacus: a differential privacy marketplace
>The worst code review comments are “this isn’t performant/idiomatic/maintainable, fix it” or other statements of opinion presented as facts.

This behavior is usually symptomatic of an excessively dogmatic outlook. That is, I don't think it's the review style per se that's the problem - it's the person.

I find developers like this nearly impossible to work with. They won't just unknowingly write poor code themselves (dogmatism typically leads to bad decisions which leads to really poor code) they will likely try and force you to do the same.
A person cannot go bankrupt in some EU countries. You will be placed under supervision and your income will be managed by a third party (usually government). This is also the reason why there are agencies which (by law) monitor debt so you cannot acquire more than you can afford. This includes everything from mortgages to pay-day loans.
right. I said that to him and to the frontend lead for the whole organization (very big place) - codebases this big you can't have that requirement, do it with a small codebase/team who all sit in the same room and know what's going on sure. 10-11 teams spread around with lots of different programmers, many also remote, it can't be done. But no dice.

In fact I had people specifically recommend me at times, don't do that because when it hits review with reviewer X it will be a problem. Sometimes you had to butter them up asking their opinion before (and that wouldn't always work because sometimes they would change their mind) anyway I better shut up and get to work, I can feel the bitterness returning!
While you wait for code review you work on another ticket. What kind of screwy engineering process assumes that code review is instantaneous and doesn’t give you something else to do in parallel?
Mikrotik RouterOS 6.43.4 is now available on Cloud Routers
(i^i)^i is pretty easy to do with Euler's formula: it's just i^(i*i)=i^(-1)=1/i=-i.
> Red Hat shareholders just sold out.

Might be going out on a limb here, but maybe that’s why they bought the stock, so they could sell out at a profit?
Here's one great idea: write blog on how to earn money and then sell the visitors your books/videos - contrary to common sense, it seems to be working over and over again, even after so many have already did exactly the same and none of their customers earned any money thanks to them...
> What GREATLY concerns me is the thought of what happens when one of these companies gets down on their luck and sells all this data to an insurance company.

What reasons are there that a company has to go down on their luck to do this?
> If I spend a day doing nothing but reading code reviews, I'll end up feeling unsatisfied and unproductive. Because code review feels fundamentally optional -- even though I believe it's beneficial, it's something we've chosen to do, not something that we absolutely have to do in order for the project or business to keep operating -- it's more frustrating to find myself spending a large amount of time on.

This is where you need to change your mindset from writing code to delivering business value. At my first job we realized that tickets were actually spending longer in code review than in development - and therefore our primary bottleneck on delivering functionality was code review. So as a developer code review is actually your main job, and writing code is something you do in your downtime when you don't have any reviews available.

Once everyone in the team is making reviewing code their top priority (or at least, a higher priority than writing their own code), waiting for review becomes much less of a problem.
That's a very humble thing to say for a founder.
em is relative to the font size of the nearest parent thus you can have situations where your font size of an element node is radically different due to the parent it is placed in. This can of course be powerful if used correctly, but it takes someone really good to use it correctly and perhaps it shouldn't be done in big teams because big teams imply some people not very good in some particular discipline.

on edit: adding this link https://j.eremy.net/confused-about-rem-and-em/
Consumer's habits are changing, how to adapt and survive in the biz wilderness?
The Mona Lisa Doesn’t Tweet
No one is going to sue anyone for selling scammy so-called self-help techniques.

Which is a shame, because this stuff is actually another example of something that should be a serious crime - knowingly misleading the public.

There's no actual teaching involved. A lot of marketing is manipulative, but when your primary product is manipulation, you're over the ethical line.
How one-sided objects like a Mobius strip work
And I'm one among the suckers who paid ~300 USD. I'm just stupid.
In the end it was a tie in the Debian technical committee. The chairman’s vote was counted twice so systemd won. Then the people who had voted for systemd resigned rather than actually implement their choice.

Not as cut and dry as you make it seem.
I would say that this switch hack is lightyears more "clever" (that is, opaque and confusing) than a simple function pointer.
Dozens of Isis brides flocking back to the UK
A developer is not just a developer. I've been in the industry for quite a while and life for quite a bit longer and I have just never found this sort of pluggability in developers or people in general.

If you want someone to write an etl script from SAP to salesforce you could probably trip over one in the street. But if you want someone to define a well thought out data model in 3rd normal form with versioned entities, property based testing coverage and full CICD pipeline you will have to search hard.
> I am quite sure that there's a balance that reduces annoyances by 80% while having far less of an impact on revenue.

It would be exponentially more difficult to convince every user not to block all ads, I don't think this is doable.

Instead we should think of how information and misinformation propagates in the era of www as opposed to the era of newspaper and tv. What we need is to keep the public informed, not to prop up a failing business sector.

For one, the www makes it much cheaper to spread targeted misinformation. That didn't happen before.
That's more a Red Hat legal failure than a IBM legal failure.
> Ain't it great to have a choice?

Not if it means that every choice is sub-par
Bitcoin for sure doesn’t fulfill this requirement given that it is de facto controlled by China.
The natural conclusion to draw from these observations is that you’re almost certainly better off taking the 135 minutes per day the average social media user spends on these services and instead dedicate them to deliberately improving your ability to do valuable things.
What's not clear here is that why would one company, which is dong pretty well, better every year, would want to be sold to another company, which doesn't look well (from your own description), instead of just continuing growing and eventually "winning" the cloud market by themselves? Is that just because top Red Hat people wanted to cash out more quickly?
And a related counterintuitive fact (again, assuming 10 minutes):

1. If you pick a block randomly (uniformly), its average length is 10 minutes.

2. If you pick a point t0 in time randomly (uniformly), the average length of the block you're in is 20 mins (and the average length from t0 to next block is 10 mins, and the average length from previous block to t0 is also 10 mins (and, needless to say, 10+10=20...)).
They prey on the "I want to be a millionaire CEO but don't have any real skills and don't know what I actually want to do with my life" crowd. Usually the message is that you can get there without doing any actual real work (kind of says all you need to know about their target audience). I wonder how many truly successful businesses actually started from that point?

The "entrepreneurs" I know had business that grew organically out of fulfilling a genuine need that either they had or that they could satisfy for someone else with their skillset and knowledge. Saying they got where they are by accident is probably a bit too dismissive but I don't think any of them set out with the end goal in mind - it just happened organically. I include myself in that of course.
That's amazing, and it is a lifestyle business. Peoples life, and income affect their lifestyle.

What do you do?
> Then how on earth are you supposed to compile it? You write the definitions verbatim on your code?

what I mean is that an user might download your source archive, run `make`, and have hard-to-understand failures because of this.
"Pair with people you like, code review people you don't like" Me, some years ago.

Not black and white, but less code review is needed if a task was paired on, if at all.
Funnily enough, one of the most praised points in Red Hat's code of conduct is the fact that it specifically says that you can work on open source projects _even if it is to the detriment to Red Hat_. Guess that's going to change now.

Disclaimer: Red Hat employee (at the moment)
Hi Chris, great project! If you're generally interested in all sorts of ideas on how to make programming better, I can recommend to check out https://futureofcoding.org/ and the slack group that's linked on the website. There are a lot of people thinking about, sharing and discussing great ideas in the slack, and your project perfectly fits into the "future of programming" category.
Hi there, first HN post. It seems to me that FPGA can be simpler to use in conjuction with CPU i. E. Run main program on cpu and complex algorithms on FPGA. Arduino released a small board with Arm and FPGA, might be a good place to start. https://www.arduino.cc/en/Guide/MKRVidor4000
When was this posted? I think i read exactly that explanation like 7-8 years ago and it really made it click for me. It was a wonderful insight!
Climate Engineering
Malaysia Largest mobile esports online tournaments – up to 128 teams
4-6 per meal, plus whatever you filled pockets with and drank in betwee

How many is that per day? Like 20??
I definitely think I know "a bit of math" (including group theory and topology) and the first page was beyond my grasp, although not by a large margin.
3 blue 1 brown @YouTube