skysight-inc/HackerNews huggingface dataset:
I believe Spritz was taken over by one of their funders, as it happens. This is a cautionary tale to founders who are tempted to raise too much for the stage they're at — raising money accelerates your trajectory but also increases your chance of failure.

It also shows that "money raised" is not always a good metric for success.
This Twitter thread is probably one of the best sources: (from John Burn-Murdoch, who does excellent data visualization work for the Financial Times)

https://twitter.com/jburnmurdoch/status/1268450736398098433

The paywall is also easily crossed by, for example, archive.is
Why do you think that has anything to do with culture?

They made business decisions that seemed rational at the time, to grow fast at the expense of good security.

Now they're making business decisions that are rational for the current situation -- they've grown hugely, and now have been fixing their reputation for privacy and security.

Culture has nothing to do with it. It's pure business. I trust their profit motive far more than any "culture". And their profit motive now is: do everything to be a trustworthy product. And their actions over the past couple of months have been demonstrating that.

Do you think it's impossible for companies to change? Because a company makes mistakes, they can't ever be trusted again? That doesn't seem very realistic.
I have honestly no idea. Haven't left the house in 3 months, except for a week or so where I visited my girlfriend without ever coming in contact with anyone (except for maybe the cab driver). I was pleased when I saw everyone wearing masks, but it seems other than that no one's really doing anything.
90 Year old granny may be the oldest player to play Grand Theft Auto
There are pretty compelling reasons to believe that life/physics are strongly tied to computation. See eg the slime molds experiments for some of the more visually impressive cases of that.

The question of how to turn these loose inklings into actionable, falsifiable, reproducible science- rather than Aristotelian armchairing - is a hard one.
Startup code needs to eventually scale and it needs to be flexible. I have no problem with "crap" code as long as it makes sense in the context and works. In a lot of cases, it would be extremely counterproductive to write "perfect" code that then needed to be thrown away a few months later when your product changes.
In my experience, "code quality" vs "features" is simply not a real tradeoff. Writing clean code with tests, function documentation, a good level of modularity, automated deployments... etc will save you time in the short term. It's pretty simple:

1. Writing quality code is not substantially slower in the first place, especially when you factor in debugging time. You just have to have the right habits from the get-go. People avoid writing quality code because they don't have and don't want to build these habits, not because it's inherently harder.

2. After the initial push, code quality makes it much easier to make broad changes, try new things and add quick features. This is exactly what you need when iterating on a product! Without it, you'll be wasting time dealing with production issues and bugs.

The only reason people say startups don't fail because of code quality is that code quality is never the proximate cause—you run out of funding because you couldn't find product-market fit. But would you have found product-market fit if you had been able to iterate faster, try more ideas out and didn't spend 50% of your time fighting fires? Almost definitely.

Pulling all-nighters dealing with production issues, spending weeks quashing bugs in a new feature and duct-taping hacks with more hacks is not heroic, it's self-sabotaging. Writing good code makes your own life easier, even on startup timeframes. (Hell, it makes your life easier even on hackathon timeframes!)
Remember Kazaa? A security researcher once posited that there were almost 70 million Kazaa clients at some point. Surely one of them has a security vulnerability...

I immediately shutoff Kazaa and rethought my approach to secure computing at home
Seems the integralists never went away...
To answer your question:
1. A job/career that pays money.
2. Your morals are not my morals. Why try to fit your morals onto others?
What's the right network buffer size? [pdf]
Just longclick the address bar without clicking it first, it then gives you the choice to copy, and even paste&go in one click.

You could always make it not to hide when scrolling. I btw use gestures to switch tabs via an extension, works great.
Yep, exactly.

The Amish population doubles every 20 years. Simple growth, over time, while everyone else's populations are near flat or shrinking? I give them a great chance.

That's faster than any other group that I could find. The Census Bureau publishes growth rates by race too - the Hispanic population is growing around 2%, the Black population is growing around 1.5%.

(I'm just hoping their attitudes on women and race improve.)
If you are early stage start-up, all your employees including engineers should be onboarded with the idea rather than technology choice. If you have someone joined you for any reason other than the excitement for idea, there is higher chance that you will find them going off track too often and it will drag you back

If you are mid-size company, I will assume that you can afford giving some breathing space for everyone to explore but still focus on the goal. You should ideally retain them with the culture.

These are the suggestions based on my experience. I may be wrong.
Most tech content is bullshit
> Static typing doesn't help much with setting up GraphQL resolvers correctly, and overall feels much less useful than on the frontend where it's absolutely stellar to type check all GraphQL queries, React calls, 3rd party component props, and so on.

We found @nexus/schema to be excellent for this particular problem, but only after you set it up correctly to feed in type information via its typegenAutoconfig options.

I agree it is less frequently helpful at catching type errors, but the errors it does catch tend to be more important to get correct than the frontend errors!
Information, Consciousness, Reality
>"If we stand our ground and choose boring technology because we have limited innovation tokens and can't afford to waste them, there's the flight risk of those devs who really want to work with those new technologies."

That's fine, let them go. There are plenty of great developers out there who just want to come to work, build the product to spec in some 'boring' reliable tech, and go home. The stack doesn't really matter. The "mission" doesn't really matter. Even the product barely matters. I've found that people who are leaving a job for the new shiny thing are either very early career, or the dilettantes who leave behind messes to be cleaned up by professionals.

Massive companies have been built around a Spring/Rails/Zend monolith with a few jQuery plugins on the frontend. Anyone who thinks they need more than that is probably wrong.
All I’m saying is there are levels of bad... I suppose this is covered by your comment! But seriously :-)
Curious why they suggest a reverse proxy. It may be a holdover from a time before Erlang SSL got so many improvements? Heroku moved SSL termination to Erlang from ELB's and saw great improvements, plus they released a useful lib https://github.com/heroku/snit

I suppose it could be related to their use of mochiweb still for the web layer. Maybe they'll add on HTTP/2 eventually and no longer recommend a reverse proxy.

There are alternatives for HTTP/1.1 and HTTP/2 in Erlang, like Elli (http/1) https://github.com/elli-lib/elli and Chatterbox (http/2) library https://github.com/joedevivo/chatterbox
Begun? You have to be tonedeaf or willfully ignoring the amount of IP that Chinese corporate spies have outright stolen from North America over the last few decades.

Let’s be honest - we have strong cyber security considerations because of very few, but very known bad actors. China is near the top of that list and has been for awhile.

Nevermind all the other security considerations.
One million deaths from the virus in Brazil is only .5% of the population. That wouldn't surprise me at all.
do you have 100% control over it? no.

do you have 0% control over it? hell no.

there is rarely a situation where you have 0 agency and if you incentivize certain types of behavior (by providing aid/benefits) you will get that type of behavior.
This is funny because it’s both possibly a joke but could also legitimately work
Bookbinding (1995)
The US could well do the same. Pay reparations to each individual slave and their families, tracing genealogy.

Or, given that slavery may be too far in the past, pay reparations to each individual person that was discriminated against through Jim Crow, and maybe some level of immediate descendants (children? Grand-children? Some reasonable line could be decided).

Of course, direct individual reparations are hard to do, which is why other, less expensive and less targeted measures have been preferred.
> I'd be wondering why people are using an essentially Chinese communications tool.

People use it because it's currently the best product.

For us at our university, ease of use and the fact that it allows the speaker of a talk to see the audience while sharing screen made it the preferable tool.
Could anyone educate me on how to dereference and unsee this article from my brain? I very much love cheeses and never noticed this ... fact.
I believe that the approaches that we designed could be implemented/extended to document-oriented DBMS. Since I don't have any experience with those DBMS, I have no intuition on whether the approaches would uncover any bugs.

Implementation-wise, supporting CouchDB and MongoDB in SQLancer would be feasible. SQLancer shares little infrastructure between the testing implementations for the individual DBMS, and thus imposes only few restrictions on them. We would definitely welcome implementations for any NoSQL DBMS in SQLancer!
I wonder what Mills College’s Center for Contemporary Music (CCM) will make of this.
I don't have kids but I never understood why some parents think that their kids have to learn about their passion, specially at such young ages. I understand this in countries where prospects are poor and your best option is stick to the family business but this is something else with different ramifications.

I'd let my kid learn about coding if he/she asks for it and is curious, otherwise I'd never try to shove it. Let kids be kids and if they become interested then be happy to be their personal teacher.
This is fine advice, but it's really advice for an individual more than an org, and if you are in leadership you need to consider whether your teams and processes are set up in a way that both leaves room for your engineers to do this and also ideally even actively encourages their doing so.

To phrase it another way: Each engineer might have the best of intentions but if success is measured by new feature velocity, adherence to this rule becomes less likely.
> Sure this isn't exactly blockchains or whatever, but it's basically the same idea.

This idea is older than blockchains; it's basically hashcash (https://en.wikipedia.org/wiki/Hashcash), which AFAIK was one of the inspirations for Bitcoin.
How can we be sure there isn't a similar, more subtle version non-removable installation now?

(I briefly had Zoom installed a few months ago, then un-installed it, but I don't know how to verify).
Eliezer Yudkowsky's Knowing About Biases Can Hurt People seems relevant. https://www.lesswrong.com/posts/AdYdLP2sRqPMoe8fb/knowing-ab...

So does the concept of dysrationalia, proposed by Keith Stanovich. Ironically, the Wikipedia article quotes Robert Sternberg as saying:

> I am afraid that Stanovich has fallen into a trap—that of labeling people as 'dysrational' who have beliefs that he does not accept. And therein lies frightening potential for misuse.

https://en.wikipedia.org/wiki/Dysrationalia
“ sell guns in supermarkets with next to no checks on who owns them,“

This is false.

One has to pass a federal background check and some states have additional checks and restrictions as well.
>eventually

Fellow compatriot spotted ;)

Just FYI, “eventually” != “éventuellement”.

Also, do you want to tell them about Corsican cheese, or should I?
Due to decades of Deng Xiaoping's One Child Policy, China is a slow motion demographic car crash that's impossible to stop. China will "get old before it gets rich", and the days of 6% growth aren't coming back.

I recommend anyone interested in geopolitics and the world over the next 30 years to watch this lecture: https://www.youtube.com/watch?v=_AvNT3vyzr0

It's the best overview of the future wealth and strength of brutal Chinese dictatorship that I've come across.
Brazil isn't a western country?
That's not even remotely close to being a source for what you are saying.

You need a source that shows that there is something different about babies, different about the 5G frequencies, and different from the light, infrared, microwave and radio frequencies that are currently being used everywhere.

Instead, you referenced a paper on a military pain ray that uses focused super high power 100Kw 95Ghz waves that says it penetrates 1/64th of an inch. Your microwave is 2.4Ghz, just like your router, but it works at 1kw. There is an enormous gap between saying "what about babies" and what you linked. They have basically nothing to do with each other. I think you realize that, but you keep saying "we don't know", when you really mean "I don't know".

> the burden is usually on the creators to demonstrate its safety

How can anything be deomstrated to someone who ignores what they are being told and repeats "we just don't know" while supporting their predefined beliefs with giants leaps in logic and excessively irrelevant information?

> I was hoping to have an actual discussion here

I don't believe you. You didn't even confront my original question of what frequencies and effects you are specifically worried about. All you have seemed to being up so far is heat from power 100 times what your microwave uses. 100kw is 4,000 times the power of a soldering iron that can melt tin and lead.
Al actually publishes a number of them via his twitter account: https://twitter.com/og_aljaffee
Spree-Liebe Hochzeitsfotografie – Wedding Photographers Berlin
Reading it just makes me hungry for Daiya mac and cheese
I am very sceptical of the claim that EVs will have a higher lifetime than ICEs. The latter reach end of life in the Western world due to a lack of desirability, not because of the maintenance burden.

A 20 year old EV will still smell bad, have gunk you can't clean all over the surfaces, not communicate with your phone etc.

Maybe it will be true, but I don't think you should count your chickens just yet, certainly not by a factor of 2.
Heuristics for Learning Tools
I miss MSN messenger's doodle tool
No, it's not too late. Plenty of people have started successful channels in the last few years, and plenty more are going to become successful in the years to come.

For instance, while Oddheader joined 9 years ago, he only seemingly started making videos in the last 2. Since then, his channel has blasted past 500,000 subscribers and is well on route to a million+.

https://www.youtube.com/user/oddheader/videos

Others I've talked to who've started in the last few years and done well for themselves include Mety333 (nearly 200k subscribers since 2017), Skip the Tutorial (460k+ since 2017), Ceave Gaming (450k+ since 2016) and various others.

So there's definitely room to succeed there, even if your channel is only starting out today.

But I think you need to keep a few things in mind here:

Firstly, as people say, it's very unlikely your channel will blow up within the first channel. It occasionally does happen (especially if someone's video happens to go viral for whatever reason or a large YouTuber keeps giving them shout outs), but it's not the norm.

So take it slowly, accept your first few videos will probably do pretty bad stats wise (and to be honest, that's probably not a bad thing given their likely low quality) and the chances of making money early on are very slim.

Secondly, you need consistency. As people have said, YouTube is a grind, and you'll almost certainly need to pump out new videos on a regular basis for a year or three before your audience properly discovers your channel. So yeah, pick a schedule, stick to it and try to make sure you have stuff lined up for when burnout/real life issues inevitably interfere.

Thirdly, you really want to have a good niche for your channel overall. Web development in itself is too broad a topic for a new channel in my opinion, and you'll really struggle to gain traction given how crowded the space is right now.

So narrow things down. Think of a particular programming or scripting language you're good at, or a CMS you know how to work with, or a sub topic (like say, usability/accessibility/browser game development/CSS image drawing) that you have some experience with instead.

Finally, remember that having good content and knowing how to market it matters a lot more than your videos' production quality. If you're not saying something people find interesting or that hasn't been said by a million people in the last, even the best microphone, camera or video editing program in the world won't make a difference.

So come up with something interesting, make sure your videos look at least half decent, then invest in building relationships with other content creators, getting an audience on social media sites, etc.

Do that, and you can definitely do well on YouTube, even in 2020.
I remember that building well!

Our team in Clifton Park was the engine that built the VPx line of codecs. Many of the engineers who worked there are now at Google in Mountain View.
Taking the shine off the Apple (and FB and Google)
It is already a blue-collar skill for 3/4 of people who code.
Fellow millennial at apparently the same age. I agree with your sentiment. I remind myself that what goes around comes around. Boomers and GenXers bid housing prices up to absurd levels and stayed working longer than past generations (mainly because they failed to save when they could have and have to service debt that is unheard of in past generations). Eventually these assets will be poured back into the market and it will be a buyer’s market. Eventually they will retire and upper ranks will be ours for the taking. They won’t live forever - that wealth will disperse. Our best times are ahead. Theirs are behind. Stay strong and don’t play their game by overleveraging.
Agreed. I find "boring" to be an unreliable metric for decision-making in software. A boring tool could result in damage to the long term development of software if it is inflexible, for example. Migrations between tools are easily some of the most expensive technical debt costs any software organization may face.

I also agree that the better measurement of good software is that which is unsurprising. Code should be easy to follow, and the decisions for the software tools that are used should be given the same treatment. You should be able to explain your code or infra to most developers without any raised eyebrows. That doesn't make it boring. In fact, it's very interesting when a problem that looks complex on the surface can be solved by relatable means.
Cool Consumer Startups Newsletter
I was saying Tier 3, where Tier 1 ist GCP, AWS, Azure, Tier 2 Oracle, IBM and Co. and Tier 3 everyone else who is so small that he can't compete with his own API for the breadcrumbs.
It's somewhat pointless without a female voice though. I don't think most players will assume you are anything but male unless you speak...
I like most of the ideas. But unsure which are pragmatic. Like avoiding competition. I don't get it. ELI5 anyone?
If you’re willing to lose almost all portability, I think you could read a value from an I/O port, pass that to printf, use that as the field width for a string to print, count the character length of the resulting string using %n to move it into a variable, and then backspace over that to prevent the output from dirtying your output. You could only use the results in a subsequent call to printf, though.

Of course, just hiding an assignment in a printf argument would be much easier, but wouldn’t be fun.

Of course, that would lose lots and lots of portability, and you could, likely, only get it to work on systems that don’t do memory protection between processes, and then, not all of them.

I guess it would not be very hard to use this trick to have printf read joysticks on many micro’s from the 1980’s.
Well, I never heard of Dax before and knowing (thanks to the parent comment) that it is formed by only 30 firms adds context to the "prestigious" in the article.
There is luck sure, but there is no luck without the work first.
Charles Babbage (of Analytical Engine fame) wrote an entire chapter of his sort-of-autobiography where he imagines life from the perspective of a cheesemite philosopher: https://www.gutenberg.org/files/57532/57532-h/57532-h.htm#p4...

(I did a production of this book as a nice epub for Standard Ebooks: https://standardebooks.org/ebooks/charles-babbage/passages-f... if you want something for your reader.)
My mistake! Thanks for catching the error
>Starting from 1930, we went from 2B to 6B humans in 69 years[1]. We added tripled the world population in a few generations.

Along with huge technological changes. Nowadays the technological advances are more or less plateaued themselves compared to getting from no factories to factories, no electricity to electricity, no computers to computers, no telecommunications to telecommunications, etc, no cars to cars.

Today we already have problems all around the world with the economy...
Location: I'm a Nomad, but I'll be in Curitiba, Brazil, for a while, due to the COVID Pandemic
Remote: Yes
Willing to relocate: Yes
Technologies: After Effects, Premiere, Photoshop, Illustrator, Audition
Résumé/CV: https://www.linkedin.com/in/yodebs/
Email: diariodadebs@gmail.com
Dribbble: https://dribbble.com/yodebs
I bought Reaper a few months ago and use it on an old MacBook where it performs quickly and flawlessly. Very happy to see the journey it has made!
if you're doing your job as a startup coder you shouldn't have to balance btwn insecurity bugs + spaghetti

that's a false choice. in reality you can have all three

'get things done pretty fast' is the only red flag in your story -- if you want your life to be truly worthwhile you must make this codebase unproductive as well
Just for fun I started answering all of the Google captchas incorrectly - I’d select every image except the ones matching the challenge and then go to DuckDuckGo when I got tired of doing that. A few things I noticed was that if you select an incorrect image it will probably show up again later to see if you answer it incorrectly again, you can exhaust the number of replacement images that pop up when you answer one incorrectly, and after a week of doing this I stopped seeing the captchas.
So just because some people find it offensive, it's a reason to change the terminology?
Probably so that the author can learn whatever JS framework they used. Overkill tech to learn on a personal site before a production site.
Ikigai: A Japanese concept to improve work and life (2017)
I've never worked on a project o bad I could add features fix bugs to it.

And I worked on a project that literally saved the HTML on the page into a varchar, had 15,000 lines of JavaScript, and all the business logic was written in awful stored procedures.

Whatever speed quality trade-offs a good engineer is making will be worth it when a startup is still in the "I don't know if this company will exist in 6 months" phase.
Isn’t that cheese forbidden? It’s more a meat product than diary at this point.
Article from 2014.

See past discussions:

from 2014 https://news.ycombinator.com/item?id=8573992

from 2016 https://news.ycombinator.com/item?id=12885435