skysight-inc/HackerNews huggingface dataset:
I work in consulting ( more of a manager now but still save myself at least some code to write ). The software we develop is whatever we're assigned to. It could be finance, hi-tech, biomedical, resource (oil/gas), public service, whatever. There certainly seems to be plenty of work as we're always trying to hire and always short on staffing projects.

Software Engineering is probably the widest and deepest career choice out there. For example, Web development is just a tiny piece of it.
Here's the easy test: Add EU, US, and China emissions together. Since ~2011, that number has been going down.
> “unstart” - while a terrifying euphemism - is there is reason “stall”, or similar, is not used?

"stall" has a specific meaning, and it isn't what happened.
> Mathematicians noted that the work is particularly striking because it relies entirely on elementary arguments. “It wasn’t like he was waiting for all this crazy machinery to develop,” Thompson said. “He just had some really clever ideas.”

the proof: https://arxiv.org/pdf/2202.02384.pdf

Last time I saw something so simple that I think I could understand the idea because it has not too many new concepts was Hao Huang Sensitivity Conjecture: http://www.mathcs.emory.edu/~hhuan30/papers/sensitivity_1.pd...
Donald Knuth further simplified it into one page https://www.cs.stanford.edu/~knuth/papers/huang.pdf

These kind of proofs are very creative.
In proof of stake even if it’s a lop sided power distribution they have an incentive to govern the crypto in a way that maintains its value. And that’s really the goal of any decentralization rather than some form of communism or egalitarian distribution of wealth/power. Crypto cannot solve the inherent income inequality in society—it’ll just mirror it eventually.
I have to think there is also a good middle ground here - I also remember a LOT of kids getting pretty seriously injured and if you look at the numbers deaths were definitely higher. Most of that is attributed I believe to vehicle safety (which has obviously improved) but I am not sure we should remember being a complete latch key kid too romantically.

I do feel bad for the youth of today though - I feel like I really got the very last childhood that was not inundated with social media and increased anxiety while still being just young enough to understand all the latest tech.
> but the ruble dropped and then bounced back.

It doesn't mean much. If I remember it right, back in USSR time, the ruble rate was about 1.6 for a dollar. Yet people couldn't buy toilet paper whenever they needed it. There was a severe deficit of pretty much everything. It's not going to be like in the 90s - the economy is very different, but sugar shortages just three-four weeks into the war is not a good sign. It will get tough for Russians, which is not beneficial to anyone - not for them, nor for Europeans, Americans, or Chinese.
Eh - the problem isn't intractable. Consumers do change their behavior when they are communicated with properly, and the technology has reached the correct inflection point. It's possible battery tech never gets to the point where it has mass-market appeal, but I don't see any reason to assume that will be the case in the long term.

The iPhone is a great example. We had PDA's for a long time, but the tech wasn't quite good enough for mass adoption until the iPhone.

On the consumer communication front, Apple pitched the iphone as three different devices that consumers could instantly understand: 1. A better music player 2. A better phone 3. An internet communications device.

Critically, once Apple educated people on how to think of the new product, they were able to drop that messaging and move on.
Yes, but in this case, it's f: Stream<A> -> Stream<B> and g: Stream<B> -> T, and compose them into h: Stream<A> -> T.

Would be nice to be able to write, for example:

T result = streamOfA().apply(f).apply(g);
Musk seeks a way out, claims Twitter violated deal by not providing spam data
If the *only* thing you need is to move along the list then pointers are probably the best answer.

However, in my limited experience with such things I have always found myself needing both walking around and a big-picture list of items. Thus I have always implemented such things as a list of elements and storing indexes rather than pointers.
Mechanical devices don't repair themselves. Living bodies do. I think you underestimate the highly optimized and resilient nature of a meat-sack body.
This is the impression I got as well, and I didn't even have to use the app. I got the sense that all anyone cared about was growing their Clubhouse community, rather than using it because they liked it.

It's hard to quantify or put your finger on it, but there was all this "hustle culture" around Clubhouse. Everyone talked about how great it was and how it was going to transform social media. But it was clear in that few believed it and just wanted to be the first to pitch their tent on new plot social media.

As a result Clubhouse had a certain "emptyness" to it. Everyone was talking about how great it was and how great it was going to be, but there wasn't any actual content, just people repeating that message over and over again, or adjacent "hustle culture" topics like Stocks, Crypto, GaryVee Worship, etc. Since people in this space are very vocal online, you got the impression right off the bat that Clubhouse was skyrocketing in popularity, but it ended up being that you just had a small group of people in an echo chamber.
I suspect that sometimes the person who uses the acronym doesn't know its meaning. Or the acronym doesn't even have a commonly accepted definition, even. For example, that's my experience from recently reading a number of articles on the "OSR" scene, or movement, or trend, in TTRPGs where "OSR" is variously explained as "Old School Revival" or "Old School Rennaissance" or even "Old School Rules", etc, but without any agreed-upon definition of what the hell it is.

(Btw: TTRPGs = Table-Top RolePlaying Games :P)
There's actually only one problem that businesses care about: how do I turn $1 into $2?
The supersonic shockwave-cone would enter the engine intake, which leads to an un-start. The weird cones that stick out the front of the engines can be manipulated to slow down the incoming air and keep it below supersonic at the intakes, which is normally done automatically with little analog computers that apparently failed somewhat regularly and in this case spectacularly during a banking turn.
I burned out hard towards the end of last year as an engineer. Fortunately, this preceded 4 months of paternity leave during which I was really able to think hard about what I wanted out of my career. I came back to a different position at the same company, as a PM on a new team. I'm enjoying the role for now, but I'm not sure if I'll convert permanently. If I do go back to being a SWE, it will be at a smaller company/on a smaller team where shipping code takes less overhead.

Generally my advice to anyone feeling burned out these days is to take a long break if they can, and use that mental space to strategize your next move. I appreciate that not everyone is in a position to do this, though.
I am mostly thinking about technical team lead role which is not an architect and not managerial role.

Team lead does not have time to code most of the time but does code reviews and attends meetings with architects and others and works on aligning stars so things happen. Then also has to stop stupid ideas or propose how to better solve a problem for a customer.

But as I read GP post again it seems he might mean actual management.
The majority of microprocessors today are <200MHz, single core, single issue, with no cache. The world doesn't run on x64 and GPUs.
An unstart is a specific phenomenon where supersonic flow of air into the engine gets disrupted. It's very different from a compressor stall where the airflow _inside_ the engine is disrupted. Wikipedia has a pretty decent explanation: https://en.wikipedia.org/wiki/Unstart
Iterate to More Complexity
I feel like this is a bad faith argument.

Enthusiast ports are already niche, and therefore not lucrative targets. This project has stated that a long term goal is keeping the many iPads that have fallen out of support in service.

If they’re successful in that goal, it’s no longer niche, and therefore is more worthy of a target for attacking.
I remember Perl 6 (now Raku) used to advertise itself as "the first 100 year programming language". I wonder if actually that could be Python. It seems like the update process has a lot of "taste", in that it adds features that are really useful and yet the syntax still looks clean and intuitive.
True - but is falling back to email really that big of a difference? It just means more work and one more username and protocol to remember. We could have better "offline" modes available on current messengers while still not just completely tossing the message.
Google voice does this for free (aside from what Google normally does with your data). Could forward voicemail there.
Another way to achieve that would be to contribute to Open Source software. Github for example awarded a badge to developers who contributed to libraries which are used by the helicopter on Mars to make such achievements more transparent: https://github.blog/changelog/2021-04-19-new-badge-for-devel...
Such a fascinating read! I particularly enjoyed the part where they are testing the radar cross section of Have Blue, the initial design for the F-117. They had put it up on the test stand, but think the radar is malfunctioning, as they don't see any returns on the scope. Finally, they get a tiny return -- a bird had landed on the test object!
If you're trying to make a version-robust module that won't attempt to compile a syntax error, top-level dispatch through __init__.py is an excellent approach.
I scare the absolute crap out of a lot of Junior developers when I tell them this.

I once said, jokingly, that "Actually, abstractions in code are bad" to a Junior and I'm pretty sure he considered quitting on the spot.

But I do think a lot of this stuff, designed to give everyone a common code philosophy, is actually just resulting in a lot of unnecessarily overcomplicated code.
"Starting a Spin-out Company: ParcPlace Systems" ?

https://ethw.org/Oral-History:Adele_Goldberg#Starting_a_Spin...
This thread is really good, some key points I took:

> But clubhouse is LIVE. So you need something INTERESTING that's ALSO happening RIGHT NOW.

> Your engineers [..] warn you: multiplying "content is interesting" and "content is live" doesn't just make the problem 2x harder..it makes it 200x harder.

> You rebuttle: "Well - Twitch figured out how to do this! Twitch is live content - so clearly it's possible!"

> 1 - twitch creators are live ~40 hours a week. Our best creators do weekly shows. ~3-4 hrs a week max. The game makes content creation easier

> 2 -Twitch is vertically focused (gaming). Clubhouse is horizontal. You need "great content" across EVERY category.

...

> Creators with big audience (proven good content) don't want to switch platforms. Spend an hour "live" on clubhouse reaching 2,000 people... or do a podcast and reach 200,000?
I'm not really gonna continue, feel free to have the last word if that's so important to you emotionally to the point of completely ignoring your interlocutor.
Postgres docs are really good.
It's not needed, but as you can read in the article, Fedora takes half an hour to boot without virtualization or JIT. You cannot mark memory executable in iOS apps, preventing you from actually letting the host CPU execute any guest code.
I gained a lot of clarity when I differentiated "programming" from "shipping code". I still enjoy the former, but the latter is becoming harder and harder to do at large corporations.
I watched this movie just a couple of nights ago, and I have to admit that this looks very plausible. At the same time, this very SR-71 breakup story may be the inspiration for the Darkstar breakup, considering that Lockheed Martin was involved in the production.
The semantics is start/unstart are definitely more interesting in this context and seem less dramatic in the context of wind tunnel tests
Perl's popularity was already in a nosedive by that point. I was programming in Perl much prior, was on numerous mailing lists, etc. The dropoff was startling.

Frankly, I believe the terrible state of affairs on CPAN was part of the problem, but it was initiated by the "there's more than one way to do it" mentality. If I wanted to do something where it would be a good idea to have a library for that task, I would have to search many candidates, each of which did sixty to eighty percent of whatever, then see which were long-abandoned, did what they actually managed to write match what I needed, etc.
And similarly, very few algorithms are better than O(n), because something as simple as adding 2 numbers can be O(n) where n is the size of the number in bits :)
> I've always thought deep underwater would make sense, provided the containment was very good. You would never have to worry about a meltdown

Until you have to. ;)
Sure, that's certainly possible. And if he did, then he deserves to be prosecuted and punished for it.
In https://chemrxiv.org/engage/chemrxiv/article-details/60c7588..., they find the common nucleobases are found earlier in enumeration, so you might expect most life use it
Yes. The pay cut would be obscene. The only way I could justify it would be to think of it as a soft retirement.

(Because I suppose we're here to trauma dump I'm moving my stream of consciousness about wanting to be a nurse to this comment where it seems more appropriate.)

My daydreaming about being a nurse started again when I was taking care of a friend in the hospital after she had a serious blood clot. I was spending 15-20 hours a week there feeding her and stuff because she could barely move and thinking that it was the happiest I'd felt in ages. I should have been stressed out because I was coordinating with her out of town family, and taking care of errands for her, and coordinating with her job, and talking with her doctors and nurses and such but I would leave the hospital feeling so happy and recharched. Meanwhile I feel so drained after spending a few hours "coding" or reviewing design documents or, worse, writing design documents. I think I just don't like technology even though I learned a lot about it to make money.
> I'm sure that we haven't found the limit yet.

I agree with that.

> A free labour market ensures that skilled people get allocated to the highest value work, which is a great outcome for everyone.

Value in terms of dollars is not really correlated with productive value to society. I think a lot of the software that's being built, shouldn't be built.
But that begs the question: why would anyone of note use Clubhouse, if not as an continuation of the mostly "one-way megaphone" strategy that made them big on Twitter or elsewhere?
I agree 100% (I come from a "use all the cores with threads and shared memory to get linear speedups on many workloads" world). But I think at this point the python leadership has committed to the "every time the GIL-removal looks plausible, find some more single-core speedups to stave off the change". Put another way: I've given up on the hope that python will ever multicore the way I think it should multicore.
> At present, the U.S. has no program to develop a geologic repository, after spending decades and billions of dollars on the Yucca Mountain site in Nevada. As a result, spent nuclear fuel is currently stored in pools or in dry casks at reactor sites, accumulating at a rate of about 2,000 metric tonnes per year.

Yucca Mountain would have been the solution, but it was blocked and then defunded. Then, the absence of a permanent storage facility got used as an argument against expanding nuclear, in some cases by the same people.
I’m directly addressing it. If I wasn’t clear: there are, for example, large companies that buy leads or exclusive product rights from small players and have an asymmetric power over them.
I believe that’s ICQ :)
This one hits so hard. I often get told I'm blaming others for failures but its hard when you are an expert on a subject (programmer) and you are surrounded by non-technical people (PMs) who want cheap, quick, easy solutions.

No fucking joke I had a PM who would ask that we "just sprinkle some PHP on it" when a complex topic came up she couldn't be bothered to mentally engage in. Cannot put into words how arrogantly disrespectful this behavior was, yet it was casually laughed off as "oh that's just how she is!" Yeah... she's that way because you have no accountability and let PMs treat your devs like shit. That's your company culture. This is a choice.

It's super counter-intuitive but sometimes trying to advocate for best practices or just improving the status quo can be HUGELY CAREER LIMITING and I cannot warn people enough against doing so. It has literally destroyed my career. You've been warned.
Im thinking about the didactic possibilities of interactive animations / graphs...
Having math questions / lessons on a tablet including these could make understanding abstract concepts much easier by providing much more sensory input & intuition
The sim also struck me as very interesting, especially for 1960's technology! How much do you want to bet that they ran every test flight through the simulator first after this accident?
There's an amusing paradox I've seen many times amongst GIS managers - their complaints about how dreadful OSM data is are pretty much the direct opposite of their enthusiasm to use it!
This is usually the product of not having to worry about costs combined with elastic platforms. Bad or inefficient methodology will still work but cost more which may result in surprisingly slower feedback loops before their work comes back to bite them.
I totally agree. I've been working with Rust since before 1.0, and I love the language, and I never want to work on async code in Rust. The mental model is too hard for the payoff. I've also found debugging async code to be more nightmarish.

Most Rust applications I've worked on which have used some kind of parallelism/concurrency would be fine with a thread pool of workers and good old sync channels.
Bye Bye Semantic Versioning, Say Hello to GitDate
Senior developer at 21 is part of the problem with software now. Companies only want to hire young people but those hires have very little life skill or knowledge outside of their field.

They arrive with vim for the latest and greatest shunning the tried and true. Yes architectures need to evolve, of course, but it isn't evolution. It is flavour of the generation with new trumping functionality and usability in many cases.

The author does mention the importance of a mentor and I completely agree with that. I think mentor should be a job title with extra perks, rather than someone who is 4 years older than you who knows where the best espresso machine is.

Grump.
Convergent evolution has been observed many times on Earth. I think it's plausible that a similar process of evolution may be possible for DNA.

https://en.wikipedia.org/wiki/Convergent_evolution
There is this philosophy about software that it needs to be redesigned if the workload scales by 10x.

The same applies here. When we are studying a topic, context (scale in particular in this case) matters a lot. Just like our physical world, and how classic mechanics and quantum mechanics are so different.
https://en.wikipedia.org/wiki/Republicanism_in_the_United_Ki...
> Irrespective of anything regarding Musk, Shouldn't transparency and Truth be sought from Twitter. Full Stop.

No. Twitter is not the press, nor is Twitter a public utility. Twitter is under no obligation to provide "Truth" or "transparency" to the public. It's a microblogging service, not the BBC.

Full Stop.
Theory: Top Gun: Maverick Is (Mostly) a Death Dream (Spoiler Alert)
Axon halts plans for Taser drone as 9 on ethics board resign
My understanding is masonry generally has less give and wood buildings can flex in the case of an earthquake. In fact it’s not to code in California to build with masonry without significant steel rebar reinforcement. It’s not necessarily due to the weight although I’m sure it plays a factor
During the peak of the original lockdowns I liked setting my "away" message to something comedic - the trend caught on with a few people I worked with.

This was inspired by an email signature I saw years ago from a coworker who is a super successful writer for a well known comedic TV show - it was a riff on the standard iOS email signature - instead hers said at the very end of every email:

"Sent from YOUR iPhone!"
In the real world it's almost certain that somebody else already paid the traversal cost in making the decision of what to act on. The only common cases where that doesn't apply are removing the head (think queue) and adding the tail. The latter case can be handled by keeping a pointer to the tail in your control structure.

A queue very well might be best implemented as a linked list rather than an array.
I think that's actually "actual parallelism", not concurrency. Concurrency is multiple processes making forward progress using a single processor and some form of blocking/switching, while parallelism takes advantage of multiple cores. Personally, I consider concurrency a degenerate form of parallelism limited to multiplexing processes on a single core.
lcsync: Librecast Multicast Sync Tool
It's a good question. It seems there are meany sources, including production on earth[1] and in space. It seems a lot of commonly available chemicals in space if hit with light or electricity will generate them. The open question has been what does it take to generate RNA/DNA. There has been suggestion that RNA would be unlikely to form in open, active water like found on early Earth. However, Mars would have had shallow oceans with large amount of shore area for chemicals to combine in quiet.

The Panspermia theory is that RNA/DNA formed there and was ejected by asteroid hits to Earth. Support for that theory is that life appears to have formed within a few hundred million years of it being possible on Earth, which seems far too short of a time for RNA/DNA to form spontaneously in an ocean Earth.

If this is all true, life may be a fluke and requiring a rather stable set of environments to work. All of this is hard to know with a sample size of one, though.

[1] https://en.wikipedia.org/wiki/Miller%E2%80%93Urey_experiment
I didn’t start using Twitter until 2013. Is this true? People even tweeted these kind of statuses?
Ask HN: How do you strategize personal growth as an engineering manager?
I would like to hear how EMs consider personal growth is and how they plan towards that. I see myself ready to take on a larger team and manage managers myself. Of course, that itself is not enough, I need my manager to also feel that way. Generally speaking, there are two strategies, grow the team organically and then promote within or ask and have sister teams re-org and report to me. I am looking to primarily discuss the second option. I see a new manager created and they are hiring for themselves. I feel that that team really belongs under me as there is a large overlap with my team's functionality. Did anyone go about doing that? In general though, I would like to hear how EMs consider personal growth is and how they plan towards that.
While I agree with the overall thesis:

> Nothing like this exists in our modern messaging apps.

Teams for Business for sure has this function. I just checked Slack desktop - there too.

People definitely use them in different ways - much more reliance on the status icon which is set by calendar/activity. Lots of folks just set status message to "nohello.com"
That thread is awesome. Prescient too.