skysight-inc/HackerNews huggingface dataset:
Her discourse is really manipulative, in it you can find your typical attempt to divide people by focusing on the downside of demonstrations (injuries, crime, etc.), on the lie that it is a divisible bill, and on fake low numbers (10,000? more like millions).

This is very concerning. It feels like Hong Kong is doomed to lose more and more of its independence, and freedom of speech, and freedom of press, as the years go on.

I have a lot of friends and family there, and as much as I love China and can understand their politics due to the size of their country, I do not wish Hong Kong citizens to lose any of their rights.
Gay Talese, the writer, is a famous for bringing a new style of journalism (as were a few years later people like Tom Wolfe, H.S Thomspon and so on). His most famous piece is called "Frank Sinatra has a cold".
And your reason for doubting it would be?
Offhand - Spiderman, Red Dead Redemption, Detroit, titanfall 2,Sekiro, monster Hunter world (kind of - the multiplayer I'd pretty much optional) are all AAA games released in 2018/2019.

There's also a glut of indie games like Into the Breach,Celeste, Dead Cells - if that's more you're thing!

There are oodles of great single player games being released still, and the enteryainemtn value of them is massive - games like Red Dead Redemption have o er 40 hours of content just in the main storyline alone!
There was a recent scifi novel about this, I forgot the title. The plot was some anarchists discovered a virus that ate plastic, and released it all over the world, and caused the collapse of civilization.

I don't see any big problem with burying the plastic in a landfill. Just don't dump it in the ocean.
Agreed, I’ve always wondered why this isn’t done more often, it seems like the perfect place for tasks such as those.

That being said, I’ve been a web developer for over 5 years and have never actually decided to move tasks to web workers; it’s about time I change that.

I also find it weird when devs complain about the lack of shared state and how it’s some how a limitation. Messaging passing architectures haven proven key for modelling concurrency in many powerful languages and frameworks like Erlang/Elixir and Go channels to name a few.

Anyways thanks for writing this up. Proper breakdown and grouping will have unseen benefits for sure, and in this case, very seen :)
At my last job all I ever did was rewrite software from scratch. Sometimes the technical debt has led you beyond a point of being able to continue using the solution you have. For example Flash (soon to be ditched by mainstream browsers!) and Silverlight (no longer supported on modern browsers), and heck Java on frontend as well. I rewrote an entire Silverlight application to HTML5 and JS for the frontend and the backend with ASP .NET Core.

Then I also rewrote a Java servlet that I never directly touched the codebase for but I was told you needed a special VM just to get it to compile, I rewrote it in Python using CherryPy. Sometimes the technical debt is not worth keeping around. I sure could of modernized the Java but Pythons a lot more approachable to the rest of the team and anybody can understand what is going on at a simple glance. I can run Python on Ubuntu without a hassle since its out of the box (our main OS in that office).
Not being sarcastic. Had that setup for a while. Humorously despite the 5 minute commute I would still work from home because it was so quiet I was absurdly productive.
Modern debuggers generally support conditional breakpoints, but they often incur a high performance penalty, so this reasoning makes sense to me.
> I understand in the abstract why the US is freaking out about China as their economy is eclipsing the US and they are starting to create a competing international order to the WTO/IMF type deal with the belt and road initiative. However, I don't understand exactly what is triggering the national security establishment's (usually stupid and deadly) sudden paranoia about China.

The previous administrations were directly collaborating with China, which was justified to the public with the wishful thinking that the CCP would liberalize when exposed to the productive free market. This administration doesn't have the same ties with the Chinese state that the previous ones did, and at the same time China is becoming visibly less liberal and more tyrannical. It's not paranoia if you know anything about the CCP.
I'm downmodding your comment. It's very disingenuous to imply that other posters are shilling for Buzzfeed, even if you shield it behind phrases like "Interesting how...".

If you have evidence, then post it. Otherwise don't make such accusations.
A more mundane application of this is found in a lot of older stereo systems, where e.g. the volume buttons on the remote control cause a motor to turn the physical volume knob on the unit itself.
> having an Alexa in your home means you must accept that your (i.e. you, the registered user) voice commands are being stored indefinitely.

is that actually true? That doesn't sound like it's GDPR compliant.

edit: I've just looked into the alexa privacy settings on amazon and it allows me to delete all my recordings from their servers (I'm in Germany, no idea if this is region specific)
Medium writers are also subject to the paywall
"If, as you say, it is no crime to be a panda, then why were we arrested?"
I've been a developer for almost 10 years and during that time, have been involved in small rewrites and major rewrites. None of them have gone well and there wasn't a single one that we didn't regret starting on. What you think is a mess of legacy code is often less messy than you think and a lot of the odd decisions were often made for very good reasons. When you rewrite a codebase, you often tend to over-engineer it for the vague goals of being "scalable" and "clean" but, while clean on the surface, it often comes out far more complicated and with the a similar number of bugs. Another way to look at it is you're taking what was previously an agile approach of iterative development and replacing it with a waterfall approach which sees a grand end goal (parity with legacy code). Software is complicated and there's no silver bullet. Adopting React over jQuery will not reduce complexity as much as you think. Adopting microservices over a monolith will not reduce complexity as much as you think. The only thing that will ever reduce complexity is careful iterative development of good abstractions which are inserted into the codebase one-at-a-time.
Email hn@ycombinator.com and we'll send you a repost invite.
No? I mean, it seems that you are asking me if there's a litmus test that if someone (honestly) is in support of gay marriage therefore they and their actions cannot reasonably be interpreted providing a gateway towards accepting alt-right ideas?

The Wikipedia page points out "On social issues like attitudes to homosexuality and abortion, the alt-right is divided ... Some on the alt-right consider homosexuality to be immoral and a threat to the survival of the white race ... Others adopt a more tolerant stance and have praised gay white nationalists" - https://en.wikipedia.org/wiki/Alt-right

So, if 0.5% of alt-right, and 2% of alt-lite are in favor of gay marriage (numbers I pulled out of my ass), then clearly it's not conclusive evidence.

However, since I believe David Koch supports gay marriage based on his libertarian beliefs, and he supports efforts that unfairly make it harder for black people to vote, and he support 'stand your ground' which have make it easier for white people to kill black people - both efforts which I believe are generally supported by the alt-right - then I've already given an example of how "supports gay marriage" is not clear evidence of not being a gateway.
Simple: ads, trackers and proliferation of node.js all ultimately contribute to increased amount of unnecessary JS I have to download when visiting a page. Node and surrounding ecosystem (Babel, Webpack, etc.) are subject to Jevons paradox[0] - by making it easier to deal with bloat, they allowed and encouraged vast increase of it.

--

[0] - https://en.wikipedia.org/wiki/Jevons_paradox
Rewrites, as opposed to refactors, are warranted when they address fundamental architectural limitations that hinder product success. There is a notable exception for cases where the software architecture effectively is the product and customers rely on observable behaviors good or bad e.g. RDBMS. Poor design is not the only source of architectural problems and it is not always avoidable; maintaining unused flexibility and optionality in architectures is often extremely expensive.

In my experience, few companies rewrite systems with legitimate architecture issues. It is vastly cheaper in the short-term to redefine the business in terms of those limitations, which is what most actually do in these cases. The risk to this strategy, which I've seen manifest many times, is that a competitor without these limitations can change the expectations of the market and thereby render your product obsolete in surprisingly short order.

Rewrites are always extremely expensive, along many dimensions, but they are also sometimes unavoidable and can lead to much greater product success than without. It is much more complex than the mere state of your code base. The calculus for whether or not it is worth it doesn't lend itself to simple analysis.
I've read several articles on this issue. It doesnt appear they are even doing the pick and place. They are just manufacturing the PCB. My opinion is it's a non issue that some politics have arisen.
This looks super interesting, but very difficult to read on mobile with Chrome (Android, Samsung S10e):

https://i.imgur.com/bJw95FB.jpg

Rotating sideways helped to a degree, but in hopes the author sees this thread..

Update:

Sadly, Firefox isn't any better:

https://i.imgur.com/ONswSNb.jpg

I guess this means this instance can't chalked up to "Chrome is becoming the new IE6".

grin
Photos Show What Humans Have Done to the Planet
The solution to "internalizing the externalities", which is the economic jargon for such, is to tax it.

If you want more of something, subsidize it. If you want less, tax it. Governments are good at taxing things.

Taxing it aligns the economic incentives to produce the desired outcome, rather than banning it which leads to all sorts of distorted outcomes.
I would say 90% of the time, there is a failure in design.

Most of the time the designer does not fully understand the problem because the product hasn't been tested yet. Additionally even after the product has been rewritten 90% of the time the new design is wrong.

Often the second design is slightly better or worse than the first design because the second design is also a shot in the dark. Why?

This is because there is no way to theoretically prove a design is the correct solution to the problem. The only way to prove a design is to test it. There is no science or proof behind "design" only "design principles" and anecdotes... all of which can be broken and tend to evolve over time.

This is why designers tend to be artists rather than scientists. Designers are hired for problem spaces where no theoretical solution exist.

If most designs are wrong how do products even exist? Well computers are fast enough to cover up design flaws. Hacks can be made to bridge gaps in designs. Overall designs are wrong but can be patched to make anything work.
Fighting for the independence of these separate pieces and layers of abstraction is one of the most difficult problems I’ve had being a developer.

Management always wants time saving, “well if we just make these parts dependent, the fix will be much quicker”, requiring deep explanations that requires justifying some “hypothetical” scenario in the future (which always ends up being in a few months). Other developers, not familiar with the deeper understanding of the problem being solved, knowingly or unknowingly implement the shortcuts, adding technical debt and hidden complexity.

I don’t know what the balance is, but I find the only way to make a long lived system is to fight hard for the separation of concerns, or slowly fall prey to chaos.
Sure. It's also very useful.
If you are still experimenting .... for my RLS, it turned out that B3=Niacin is very helpful, even after onset; And also sufficient iron.

When I take iron in the morning and B3 whenever (morning/day), I don't get RLS.

And important: if you do experiment, I found that only "real" flush-causing B3 works; Not niacinamide/nicotineamide, which apparently has some of the (many) benefits of niacin, though no RLS relief (or flushing). And especially not inositol-hexanicotinate, which I have not found a single reference describing any useful property of (but still gets sold as B3).
Fortnite almost got canceled, says ex-Epic Games dev
Any test is only effective if it's actually performed during acceptance, and there's no requirement provision for such test in any acceptance qualification that I'm aware of.

In either case, it's kind of a shitty test given defense applications aren't constrained to the same EMC regulations as the rest of the commercial world.
1) Rewriting code is rarely, as the phrase suggests, about doing all the work over. Usually it is about restructuring the architecture and then adapting the old code gradually.

2) Throwing away code is not the same as throwing away knowledge. Provided that you didn’t lose the entire team, the knowledge is still there. The code is just the corpse of knowledge and it is worth just a fraction of what the team that wrote the code is.

A rewrite is a good opportunity to revisit and review that knowledge.

3) With experience you learn to balance two forces: perfection and pragmatism. You should strive for perfection in everything you do, but you have to demand of yourself that you can release in a reasonable amount of time.

4) Every good software project I’ve been on has viewed the code as something temporary. This forces you to think about how you will replace every bit of the code as you write it. From this, workable architecture emerges unless you succumb to perfectionism.

From your description your CTO’s instincts were right, but he might be missing the backbone to put you in your place.

Your team needs a more experienced lead developer to help you guys mature as developers. And you need to pay less attention to articles and blogs, be less worried about what others think and ready to learn from someone more experienced. That’s going to be hard since we programmers tend to have huge egos. Even when we’re inexperienced.
There isn't a problem. Some people just look for reasons to bring out their inner asshole.
However the third iteration is something that you can be proud of. (but in my experience, 1/2 through the second iteration the funding gets cut off)
Yes also selling word has aquired a really bad connotation mainly because of these influencers pushing unnecessary stuff on to their list.

But selling can also be giving your list what they signed up for at a price that they will not get anywhere else. Which is also very important to keep niches and not to try and sell dog training videos to a person who signed up for piano lessons (yes poeple can do that)
In the same vein : why not produce/use less plastics ?
The trick is that by taking every symbol that had positive influence and making it a hate symbol, it's showing that you're a fool for naively associating Symbol A with hate, and are merely acting as a knee jerk reactionary without understanding the underlying context.

If you did understand it, you'd realize trying to stomp out or prevent what is going on is a fool's errand. You can't extinguish the idea; because on each success on your part, a metamorphosis will happen elsewhere, utilizing some other innocuous symbol.

You need to get to the root of the matter; which is apparently a marginalized segment of your population being squeezed to the point violence and hate seems the only way forward.

Which is a rather ugly state of affairs, as it means society as a whole has already lost. It is infrequent that a population pushed to the brink of violence becomes anything more than a bloody footnote in the history books in need of some form of whitewashing for the future.
The coupon typically ranges from ten to fifteen percent which isn't insignificant.

In the US I can typically sell my clothes for a decent return at my family's yearly yard sale. Anything that wouldn't sell such as old towels or items that didn't sell I can just take to h&m since they literally accept anything that is fabric.

It was even better when I was in Japan. My family always did yard sales or donated our old clothes but over there there really isn't a culture of getting things second hand, especially if they aren't in near mint condition like what you would find at BookOff or they have been specifically curated and put in a trendy store in Harajuku. My ex would just throw her old clothes in the trash until I did my research and found she could donate to H&M for that coupon. I think that's an overall net positive.
Personally, start with a high level domain model, then a high level block diagram of the architecture (essentially a system model) and then keep breaking it down to the module level. This way people start with the domain understanding what the problems are and what it is they are trying to solve and move into the high level system model to see how it fits together, which leads them to modules that have contracts. Teams should maintain the documentation for anything they work on, and update any changes in assumptions and input/outputs that lets other teams stay up to date.

Key things (especially on modules) to document are any special behavior, inputs, outputs, data needs and any assumptions. I personally like to do it in block diagram because then you can also do flow diagrams as well. This also is nice because you can do a template document to help people. Of course, as a system gets more and more complex this gets tougher sometimes, e.g. microservice architectures with more than 100 services can be tough if you try to go too deep, but if you keep it at the module level and above it is easier to manage and is usable.

Overall to me it isn't really that hard when you are starting fresh, much harder to go back and figure it out later unless you have someone on the team that has the full understanding which gets less and less likely the larger the team/product gets. So then it becomes a major undertaking to get all the people that have knowledge together and figure it out. The advantage is a lot of times you find things that were bad assumptions that changed at some point and are likely causing some unknown issues, so it is still worth all the effort.

As for how to manage it, documents in revision control is one way, tools like Quip are another, just kinda depends on the team etc.
For anyone curious, same with Kroger in the midwest. I generally choose Meijer...they do digital coupons, but nothing dramatic. And they don't inflate their prices for 'nonmembers.'
I had a rental with CarPlay a few months back. First time I've had one of the infotainment systems that wasn't a massive exercise in frustration to use. It also wasn't all hot to trot to download various contacts, etc. from my phone like most of them seem to be.
> Models are a good, helpful tool. They are just not explaining everything, and that on purpose, and as a human we always need to be aware of that models are just models and not reality.

Do we have anything else but models?
I agree with the part about the number of people being managed, however usually there's a huge difference in management structure. For instance we have some standard big corp and its tech department. So you'd have a developer,senior developer,tech lead, some sort of team manager.Then the team manager would be reporting to the person that runs the particular division or department. The head of the department would report to some VP who would eventually report to the CTO. In a small company that'd be like developer=> CTO. That "Chief",in which case it loses the purpose.
A lot of people might disagree, and this is just my opinion, but if you are using object oriented programming than in 99% of all cases you are not being as flexible as possible. Tying methods to data is an inflexibility.

With sufficient complexity under OOP you will always be writing code that feels like it is poorly designed because the paradigm promotes poor design and lack of flexibility.
yes Assblaster, I do believe so. The Mueller report was clear but not to you. You should try reading it again to understand what it says.
Well, actually, it isn't orbiting just around the center of mass of the solar system (solar system barycenter), but that is just one of the two foci of the earth's elliptical orbit. The error is of a similar magnitude as assuming the center of the sun vs barycenter of the solar system.

If you're going to be pedantic, get it right.

This article is a much better technical explanation of the orbit, including both the moving center of mass and the elliptical orbit: https://socratic.org/questions/is-the-sun-directly-in-the-ce...

Oh, and the earth's orbit is also distorted by proximity to other gravitational masses, most notably the moon, but we're not going to be /that/ pedantic.

Side note: the phrase "Well, actually," was banned at my house. Not sure why...
Ugh, that seems very biased given the extensive cases of money laundering that led to UWOs coming into law in the first place.

"Walter Olson is a senior fellow at the Cato Institute"

Ah, the Cato institute who would like states to have no power to speak of, on anything much.

This seems a more balanced brief overview of UWOs, which notes they're not being used often enough yet:

https://www.forbes.com/sites/vishalmarria/2018/10/25/how-the...
Number go up! That's the terrain. Easy.
Yes I think browserless.io is a very good site if you want to avoid those headaches with puppeteer.

But it may dilute your profits though since you'll need to buy a commercial license for it even though the project itself is open source. Depends on the money vs time you want to invest in doing it.
Have you heard much from the Discordians lately? You seem like someone who might have intersection with their circles.

Not a bad thing at all, I've just not run into them in so long.
They also don't cook evenly. You can have a TV dinner that is half molten and half frozen if you nuke it without the plastic lid.

Microwave sterilizers depend on steam to sterilize, not radiation. They just get the water to that temperature quicker than boiling in a pot.

Results also vary by organism being eradicated. Hamster in a microwave will end sadly. Cockroaches and ants will survive. Insects have less fatty tissue to absorb radiation I believe. Bacteria has none, so you do the math.
I used to visualize basic whisps of the scenes, what each character looked and sounded like, I guess I've always liked to visualize while reading... in fact I can still very lucidly recall tons of visualizations from more than a decade and a half ago as if they were scenes in a movie, a real testament to the storytelling ability of those authors.

But now I try to spend more time than before. I try to really soak in every paragraph. Whereas in school I took pride in being the most prolific reader around, there isn't much room in my adult life for such competitive, external motivations. Now the stimulation I receive from art and literature stems from my appreciation of the artist's prowess.
Carbon is The great filter