skysight-inc/HackerNews huggingface dataset:
There are so many. Sometimes they're big picture stuff, sometimes they're more detailed.

One of the lessons I learned in my junior years is that I used to write CSS with a lot of nesting and relatively short class names (I used SCSS which made nesting easier) - The CTO kept telling me that I should avoid using more than 2 levels of nesting and to use long descriptive class names. I felt that was against the whole point of "cascading" in CSS. I soon discovered (during the first redesign) that when you have a lot of nesting in the CSS, it becomes extremely difficult to refactor the layout of the application; moving containers around breaks the layout every time. Whereas if you have a relatively flat CSS, you can move around components easily without breaking anything. It seems so obvious in retrospect.

I also learned the importance of having one source of truth and the importance of making sure that each kind of data flows through the system in a single, clear direction (or else you can get glitchy behaviour with certain kinds of realtime data). A common one is to make sure data flows from the source of truth. For example, when you click a component, it should update the URL hashbang, then other components should react to the change in the URL... Don't make the components react to the click directly and only update the URL hashbang as a side effect (because the click event could conflict with the URL change event in some edge cases; e.g. cause the UI to be rendered twice is a common issue). The URL has to be the source of truth.

Another critical lesson was about separation of concerns and the importance of being able to justify all technical decisions using simple non-technical language.

But there are so many lessons. I was fullstack so I learned a lot of backend tricks as well. A different one seems to come up every day when I work with other developers on a complex project. I try to explain the reason as much as possible because sometimes they sound counterintuitive (or I should say counter-narrative) and they're not usually silver bullets so it's important to convey the nuance as well.
This article is controversial and shows a distorted and incomplete point of view. For example, https sites are more vulnerable to some types of censorship. A CA can censor your site by unilaterally revoking your certificate. It routinely happens already. Promises from CAs not to censor you are just that, promises, and those can be broken in an instant.
It's not making it look better, it's making it run faster.
I dunno, I think it would be a big improvement that would be generally appreciated by a lot of people, even if it's an incremental optimization. There are lots of programs that are CPU bound but implemented in python for various good reasons. Doubling execution speed of those programs is like doubling single core CPU speed.

I wrote a simulation of sorts in python a few months ago, and a scenario runner to crank through as many simulations in parallel as possible. I didn't have any particular goal for runtime, but the faster the better. I spent a day replacing an iterative solver with a closed form solution, and that made it about 10x faster alone. I spent another 20 minutes turning classes into slots and got an easy 50% boost on top of that. I run that code for a couple minutes every few days on my 8 core laptop from 2020. On my 5 year old laptop with half the cores, the same task is more like 5 minutes. Doubling the speed of that code would be really nifty, in that it would make the 5 year old laptop take a couple minutes, and the modern laptop take less than a minute. I'd probably double the number of scenarios and get a more statistically significant result for what I'm simulating.

I also like to use Cura for 3D printer slicing. That's pretty much all written in python, and while it's gotten faster over time it's still pretty darn slow. If that doubled in speed, it would be an awesome upgrade.
I understand the insecurity part, I don’t understand the behavior. Or maybe I do, I just consider the person an asshole first, and insecure second.

I don’t enjoy being corrected by my team members either, but that’s more out of frustration that I did something wrong in the first place.

The act of correction may be annoying at times, but you absolutely shouldn’t punish the initiative.
You're basically describing Microsoft OLE[1].

There was also the open-source alternative, OpenDoc[2] that never got anywhere... this has been tried and just doesn't work.

The only thing that seems to work is media-types on the Internet... with the browser as the universal viewer/processor... but as it is currently, it's hard to make it better than what we have.

[1] https://en.wikipedia.org/wiki/Object_Linking_and_Embedding

[2] https://en.wikipedia.org/wiki/OpenDoc
I’ve been meaning to convert my config to Lua. I haven’t tried out the official LSP support; I’ve been using coc.vim (https://github.com/neoclide/coc.nvim) which supports most of the VSCode plug-in API. Have you tried both? Curious how 0.5’s LSP implementation works for Typescript.

(My config is much simpler, a single vim script file: https://github.com/justjake/Dotfiles/blob/new/config/nvim/in...)
The article describes the resulting Chinese text as "nonsensical", but clearly it means "Kang homo sapiens reflect pick up mongoose" (according to Google Translate).
sure you can. You can retrain your brain for lower dopamine, this increases sensitivity, decreases addictive behaviour. And you feel happier
Boards at that price level will have to wait until after the component shortage, but I believe it may be possible to order a higher spec'd D1 board for under $100 within the next few days and receive it possibly before the end of the month.
Was a time that the cache pragma / reload interval could be explicitly set by the client.

As much as ensuring current data is sometimes relevant, having a tab show up empty, with a 404 (linkrot), or with some redirect to utterly unrelated content is ... not serenity-inducing.

Mozilla's operating premise is that the browser serves users, not publishers. That promise rings somewhat hollow these days, though I enthusiastically applaud the concept.
Somewhere I read that Covid deaths are underreported. This is in the chaotic times understandable even if unfortunate. It's said it happened everywhere, even in the USA and in Europe, and the real rates are somewhere between 1.5 times to 10 times the reported rates.

And Japan seems to be an outlier with massively underreported deaths.

Probably because many elderly died alone at home and where interred or incinerated without further testing.
Unless you've been living under a rock, you should have noticed that most news publications are now paywalled. It's annoying but you can't just ban journalism. Blogs are dead, smaller websites are drowned by spam and new search engine "algorithms", and if you want a somewhat authoritative news piece you'll find yourself increasingly having to go behind a paywall.
What would be nice to see is a universal micropayment system instead of ads and subscriptions, but after a decade or so of nobody implementing one, be glad you can still read what you can without having to spend $200 a month on a dozen subscriptions to cover your needs.
What has gotten you so upset about this transition? I don't understand. All your comments are so vicious with no backing.

>You could've just said that you no longer want to invest in mobile talent.

How does this even track? They had to retrain their engineers.

I call complete BS with your app experience. I have a Redmi and the app works flawlessly. They seem to have internal data to prove it. They were under no obligation to make the blog post if they didn't think it was successful. If anything they are going against the grain here so they know there are lots of people watching.
I'm not sure a direct link to the GitHub readme does this project justice if you're not already familiar with it (though the documentation is pretty good for someone who already knows what it is).

On the other hand I'm not sure how to describe it to a newcomer either, but at least I can do the crass "it's like this thing you may be more familiar with" which projects themselves don't like to say on their sites.

So if you use FZF on the command line or in Vim, check this out (there's wrappers for the actual FZF algorithm as well, though not by default), CtrlP is maybe the oldest Vim plugin that does this kind of thing and I think the various IDE implementations (which generally focus more on file or code locations than the Vim ones, which use it to enhance the keyboard interface generally) started with Textmate's Ctrl-T though maybe Sublime version is better known.

I'm very bullish on this being the best UI workflow for programmers, since we're dealing with a lot of textual information.
eBay sex ban June 15
I think the very first you need to know is the market. Talk with colleagues, better if they recently moved, and ask for a little more. I think most of my friends know my salary, some earn more and some less, who cares? I'm not sure about not mentioning your current salary because a lot of interviews have ended at that point without wasting anyone's time. You can give a figure and ask for a 30% raise, it's perfectly reasonable because moving has always some associated risk and HR knows, better than anyone, that it is your better chance at improving your salary.
'the camera on the first iPhone' definitely wasn't a 'world class tool'.

The camera on the first iPhone was terrible! I had a Nokia N95 at the time, and the quality just blew the iPhone out of the water. The iPhone's camera was so bad instagram had to come along with extreme filters to get a decent sort of image out of it, although, look how that turned out...

Also, saying the App Store "is an unavoidable, ubiquitous forum for commerce" really just isn't true. I manage to avoid it fairly successfully.

And crying about a $1000 cap on in app purchases as being harmful? Please, you're killing me.

1st world problems.
> Every 5 or so years there's an "important" transition happening.

Name at least one change in Android SDK that can come close to revolution that is Compose. And same for iOS/Mac and SwiftUI.

Compose and SwiftUI are doing to mobile what React did to web. It arguably single most important change that happened since the inception of mobile platforms.

> There's been many stories written about companies that live on the bleeding edge. I don't remember any of them ending particularly well.

What?
My best colleague: Do not panic (I’d just brought down the production env, it was partially his company). I’m still in awe of how he carefully went through the steps to resolve the problem, not hurrying at any point in time.

And it was solved in one go.
Not the original poster but I think things are just radically different by the sounds of it. Every company I have worked at, once the code is in the main revision everyone is responsible for it. At that stage the code has gone through many people from reviewers to testers, its not one single persons fault.

Easiest thing to do ia not to blame but to just find a solution and see as a team if it was a genuine mistake that is unavoidable or if you can make some adjustment to the process to ensure quality and reliability of your code.

People can specialise in a certain area of the codebase but no one 'owns' anything. Everyone needs to respect that any change to the code is a neccesary one. The 'expert' or original coder is usually a reviewer of the changes proposed anyway so thats when they can voice opinion on whether someone has misunderstood something or not.

Bugs/Features can be worked on by anyone without ego getting in the way.
I don't know about you but I use linux. I was pleasantly surprised to find CSGO running smoothly on it.
I can code well – now what? I made a list of curated learning paths that helped
Hey folks,

I built Tinyschool (https://tiny.school/) - It is a collection of curated learning paths to help developers learn skills to climb up their career path. The skills include more than just coding - things like documentation, collaboration, communication, engineering processes etc.

When I was in the early stage of my career, a question that always bothered me was - I can code well, but what is next? It took years of research and learning at work to figure out what those skills are(and the list is still incomplete).

This is my humble attempt to curate all those skills. Along with a couple of other senior engineering managers, we have curated over 25 skills so far. Will be adding more soon.

And it's all free to use.

Thanks! Hope it helps.
The right is also pro-business. Lowering heat on China in exchange for concessions for Korean business is what I am afraid.
I recently had to upgrade Jira and Confluence at the workplace. It was clear from their configuration methods and how they respond to errors/failures, they are written by different development teams. One needs to be an admin to experience this, ordinary users will see no difference.

Take for example the admin UI. When adding "Application Links" to link Jira and Confluence with each other, Jira has a nice tabbed interface allowing you to configure it easily, whereas in Confluence, you have to scroll down a long sidebar with dozens of options until you chance upon the required link. Had similar experiences configuring various other options at the filesystem level.

Jira configuration was more coherent, fault tolerant and failed gracefully. Confluence configuration on the other hand was messy in comparison.
Official LSP is lightweight, much faster imo. You can try Typescript's tsserver with neovim-lsp .
It wasn't intended to flame anything, the first part was supposed to be humorous, the ending part clearly says there's historical good and rational reasons to use a proven design.
The Economist is particularly easy though - just turn off JavaScript.
I think luck is the true national skill of the UK. We are a nation of gamblers and risk-takers, and often that tends to lead us down paths that make no or little sense, but _sometimes_ we get really, really lucky.
Chrome's response to numerous power-user / user-respect features over the past 15 years has absolutely convinced me that it has no interest in supporting either notion.

Audio/video autoplay, adblock, tabs navigation and retrieval, user state generally, and more.

I still use Chrome on Android in two cases:

1. On an old device in which Firefox/Fennec performance is abysmal. (On a newer device, there's no contest, and Fennec wins out for general browsing.)

2. For print-to-PDF on the newer device (Fennec seems to have lost this functionality, along with a number of other highly useful features).

Otherwise, I avoid it like the plague. As well as Android in general.
It’s not a tooling issue IMHO. It’s about accepting that you do not need to hoard every single piece of information. Once you accept to let go and develop the habit to close your tabs regularly (for example at the end of each day), the problem is solved. No more anxiety related to your browser state!

I was a hardcore hoarder, with 300+ tabs all the time, until I realized I was the source of the issue. Now I open as many tabs as I need during the day, then just know I will close everything at the end of the day and start a fresh session. It’s very relaxing. If I really need something I wrote it down in my notes somewhere but that’s really not often.
Dear DigitalOcean
Your Sign-in button is hard to F*ng find in mobile screens!
> NB: English is my second language.

That makes two of us, which is probably why I didn't get you at first :). Thanks for explaining!
Most ended up with ram expansions including RTC with battery, not to mention leaked capacitor juice dissolved chip pins and pcb vias.

They were build just a tad better than contemporary Atari ST from the point of signal integrity, but Commodore manufacturing plant was a shit show. Multiple models shipped with capacitors mounted in reverse polarity (1200, 4000, CD32).
Not perpendicular, just unaligned.
Don't forget that there's Eclipse as well, which I personally still prefer when dealing with Java codebases, although I have somewhat positive experiences using JetBrains IDEs in other languages, particularly Python with PyCharm.

But generally IDEs are almost a necessity for any complex Java codebase. That's markedly different in other languages. I sometimes work on the chromium codebase (C++ mostly) which I use either VSCode or a simple text editor for. When dealing with smaller scripts, whether in Python, Perl or Bash or whatever, I usually stick to whichever simple editor I happen to have accessible. The same is true for some small C codebases I maintain on an irregular basis.

Generally I consider it a rule of thumb that the more refactoring a codebase requires to be kept in a maintainable state, the more you profit from an IDE. And the necessity for complex refactoring grows with the size of the codebase and the number of developers working on it (especially if a lot of them happen to be rather new to the craft).
China doesn't have any worse (or better) reputation than JPL in cleaning their crafts. This is pure speculation. If anything the US RU space race were much more likely to have spread bugs than modern crafts.
I spotted this trend a long time ago. I see it everywhere: software tools, clothes, cars, you name it. It's called fashion. I decided to opt out. I use timeless tools like emacs and bash. I wear timeless clothes like trousers and shirts. I drive whatever reliable car is available at the time. I haven't got time to keep up with the whims of fashion.
Julian Assange and a couple of others developed a file stem called Rubberhose to avoid this problem. All of the filesystem structures, data, and free space are indistinguishable from noise without the decryption key. The system always sets up some portion of the filesystem as unusable space that's initialized to noise. This space may contain another Rubberhose instance, which would also have some unusable space in it.

If you're tortured to keep revealing keys to deeper and deeper volumes, eventually you're going to hit a point where there are no more volumes, but you can't prove it.

I think the original threat model was someone willing to torture you, but willing to accept plausible deniability once you'd revealed some moderately sensitive information.

In reality, if someone is willing to torture you a couple volumes deep, there's a good chance they're going to just keep torturing you forever. Rubberhose may still work in this model, since in theory the promise of avoiding torture loses most of its power. The downside is that once you format a partition with Rubberhose, you're resigning yourself to being tortured forever.
Joephus Poblem
TLDR, but I think ancestor was talking about games being permitted to execute arbitrary code, as opposed to privileged users being able to inject code into a game process…
Racing Motion Simulator with Galvanic Vestibular Stimulation
Window-based task grouping (where that's possible) is ... somewhat tenable.

It's not available on Android / Mobile, of course, but on any windowing desktop OS it's an option.

Firefox + Tree Style Tabs is still worlds ahead of this.
If you want EU to do something you can call Angela Merkel, and she can beat EU Parliament and other institutions into submission quite quickly.
A very pale shadow of TST.
Yeah, sure, same here. However, at least in Germany, you have „Unterlassungsanspruch“ (injunctive relief). That means if you lawyer up (often free if have legal protection insurance) you can easily get an injunction against the distribution company. An e-mail is usually enough though.

So that’s why I don’t really get any spam, except the occasional flyer from food delivery services or questionable political parties/organizations.
When the voyager was launched, telegram was the dominant mode of long distance communication in my country.
I kept using the most popular telegram API library which is based on async.

I will check out SWF, thanks for the help!
I confess my first thought was mixing oxygen in a methane environment inside the body isn't ideal.

And this isn't a joke..... for example, cyclopropane is an excellent anaesthetic gas but no longer used due to the explosion risk. I believe (?) there was a case of a patients throat catching fire on the operating table.

https://en.wikipedia.org/wiki/Inhalational_anesthetic#Gases
In my experience, Wikipedia covers emerging phenomena incompletely.

It’s also bad at a question like “Is coffee bad for me?”. I’m not saying Wikipedia is good. It’s just not what I’m looking for here.
I agree the current one is a major change but it's not mature yet. It hasn't stood the test of time. Twitter was built on RoR when that was the coolest new thing to build things on and Uber's booking engine was on Node.js when everything was being run on Node. I'm sure there's more I'm missing. .
You can already detect obstacles with your nose if you get close enough.
Damn Dang, you seriously went all out to explain, even after all those years.

Hats off
"Good tools aim to simplify complexity, not complexify simplicity."

Some people don't realise that this is a goal, or that it's even possible.

At Microsoft, this was the philosophy behind the .NET Framework standard library. It is simple, beautiful, and abstracts away reams of complex boilerplate that was necessary with C++ programming.

Now?

I'm using Azure, and... oh... my god. Every internal piece of wiring is exposed, raw, to the end-user. Wear insulating gloves.

You need to know their internal project code names! The undocumented ones are typically the most important.

You need to pass secrets between two agents running on the same VM through your workstation during deployment!

Need to pass an identity around? It's broken up into individual fields, one of which can only have a single valid value. But you have to provide it using a programmatic lookup.

Want Accelerated Networking? There's a convenient Boolean flag for it. Great. Except that it'll break deployments if the VM size you've selected doesn't support it. How do you know if a VM size supports it? Bahaha... you don't. Build a switch statement with 300 entries yourself. That's what the Indian subcontractors writing the rest of Azure's code do! It's good enough for them, so it should be good enough for you. (I wish I was kidding, but I have seen the code and it is literally this.)

Ultra Disks? Switch statement.

Availability Zones? Switch statement.

You get the idea...

I have spoken with several Azure team leads, and they just blink at me slowly with an utter lack of comprehension when I explain that this is just not good enough. That in Visual Studio, I can tab-complete a type and it will compile. That 100% certainty is not comparable to 90% certainty in Azure, where a boolean true value might need to be the string "true" value because fuck you.
The deciders live in big coastal cities.
They want the island as much for the people and technology as they do the land. They have plenty of land. The choke points can be bombed from anywhere on the island and even from cruise missiles.
And both Java and Javascript, an thus any language derived from from them. I'd go as far as saying that a majority of the code being written today uses UTF-16.

With these languages not even providing alternative API's that are easy to use means it'll be some time before we don't have to suffer this.
The Nikkei has a detailed article [0] on the steps that China is taking to compete with TSMC and other western chip factories. I think a lot of commenters would be meaningful if they took time to read the other side of the problem and not just run into nationalist and inflammatory war.

[0] https://asia.nikkei.com/Spotlight/The-Big-Story/US-China-tec...
The upgrade from 8-bit to 16-but was particularly painful.
I doubt the system really is much more transparent than more usual systems that do not blame every potential 'criminal' publicly.

Or in another world, if that openness does anything good how comes the US has one of the biggest issues with police violence from all the developed world?