skysight-inc/HackerNews huggingface dataset:
This sounds scary accurate, what other insights on “points of leverage” did you uncover?
German also has almost deterministic pronounciation rules. Italian too, except for the position of the stress.
https://news.ycombinator.com/item?id=35315130
My company has a very strict no-gpt/no-copilot policy. Check with your legal/security/compliance teams before sending your codebase to another company.
Yes, I believe some careful and informed pondering leads one towards that conclusion. Hume's guillotine is an implacable philosophical device: https://www.youtube.com/watch?v=hEUO6pjwFOo (I warmly recommend all the content on that delightfully frightening channel)
Not sure where it came from, but it's very old. My dad (who was a school teacher) presented it to me 50 years ago.
Toyota, where Lean came from. Doing estimates to put together a car sounds like it would be straight-forward. Doing estimates for R & D, not so much.

I think software development falls somewhere in between those 2 extremes. We have some knowable quantities, but also some unknowns. We can't really estimate the unknowns reliably, but we can do something like a "timebox" to see how much we can figure out. Meaning that we need time up front, just so that we can come up with an estimate.
Democratic liberal political country on the "good" side.

Autocratic dictatorships are the baddies. https://www.youtube.com/watch?v=8JOpPNra4bw

For example, China just went from a "sort of" almost democracy to full on autocratic dictorship the minute the law was passed that Xi Jinping is now life dictator. Same with Putin and Russia.

I don't feel like I have to defend anything I wrote above - it's pretty self-evident.
Ventana: Datacenter High-Performance RISC-V [video]
Try Firefox's, which applies to many more pages IME.
That is such a small user base and governments have already shown they can confiscate crypto of they think it's a priority. The main use I see is in the midst of currency crisis, but that is fairly rare.
> A Ponzi scheme pays profits to earlier investors with funds from more recent investors.

You just described how Social Security in the USA is funded. Its billed as government-run social insurance, but funded as a ponzi.
> It’s just hard to compare industries which are done growing with ones that still feel like they might be exponential forever.

Some industries never evolved too much. I don't see a big functional difference between cars a 100 years ago and cars now. And there were electric cars in 1900s.

A car is constraint by lots of things just like GP comment affirmed. Putting more gadgets in a car won't change what a car is or how it works at a fundamental level.

From the very first microprocessors to today's there is a big leap. If we apply that leap to cars they should be using nuclear fusion and take us to moon and back in seconds. And it's not like trillions of dollars weren't invested in car R&D in more than a century.

Software growth seems exponential only because of hardware and the Moore's Law. Which will come to an end soon.

Thanks to Moore's Law, we programmers, afforded to be careless, not think about performance or use unnecessary abstractions just out of esthetical or ideologic considerations. It allowed businesses to say that time to market trumps everything and customers should simply buy more powerful boxes or more boxes. Now this will come to an end soon and we will have to think about efficiency, speed and performance.

Or maybe chips will move from silicon to some alternative processes where growth is still possible.
Point by point:

Saying men and women have different chromosomes is circular logic. You're saying that XX = woman and XY = man, and then defining "man" and "woman" in terms of the standard you set up for them.

As I responded to in a different reply, skeletal structures exist on a distribution. Those distributions generally overlap, meaning there are some women closer to the "male" average, and some men closer to the "female average. That doesn't determine their gender or even their sex.

Edit to add: you list hormones as a determining factor -- but hormones can be adjusted. Would you agree that a person who achieves "male" hormones through pills or injections qualifies as male? Or vice versa?

Saying they have different averages ignores that distribution, and again would arbitrarily classify some people as the opposite of their chromosomal classification.

"Women can have children" -- even among XX women, that's clearly false. Or are you saying that women who can't bear children aren't women?

And again, "sex" is not "gender": https://www.ons.gov.uk/economy/environmentalaccounts/article...
I do not own any crypto myself. The grown-up opinion is of course to view all crypto ""investments"" with extreme skepticism, which is an absolutely sane and correct position.

With that said, I like the idea of cryptocurrencies simply because they are punk as f*ck, and I'd like whatever leadership in charge to know that they do not have absolute power to run anyone else's life.

Apart from magic internet money, I cannot figure out any other way in which to "make myself heard".

With every indirection the gov't adds through decision taken by ombudsman/committee, the more power asymmetry is added which just fuels my sense of a system driven by amoral technocrats.
> The total crypto market cap collapsed because of interest rate hikes.

Let's take a deeper cut, why does something collapse when interest rates rise?
>At that time many young programmers regarded compression […] as very important.

They still do regard it as important, just in a different sense. Shannon formally proved that compression is congruent to statistical inference — an efficient compression algorithm seeks to minimize the statistical entropy of the scheme used to encode a message. Compression is thus loosely congruent to a branch of statistical inference you may have heard a thing or two about called "artificial intelligence" [0], which many young programmers are very much engaged with.

Take the Hutter Prize [1], which awards money for the ability to compress the entire English Wikipedia, or the Large Text Compression Benchmark [2], the latter of which's current top performer is a transformer-based neural network [3]. As the LTCP's rationale says [0],

>Given a probability distribution P over strings s, the Shannon capacity theorem states that the optimal (shortest average) code for s has length log 1/P(s) bits. If the distribution P is known, then such codes are in fact easy to find and compute. The problem is that for natural language, we do not know how to explicitly compute the model P(s) for a given string s.

>However humans must implicitly know P(s) because our speech and writing, by definition, follows this distribution. Now suppose that a compute can compute P(s) for all s. Then for any question q (or dialog ending in a question) and any answer a, the machine can compute P(a|q) = P(q,a)/P(q), and use this distribution to answer any question q posed by the judge. By definition, this distribution would be identical to the distribution of answers given by the human, and the two would be indistinguishable.

[0] http://www.mattmahoney.net/dc/rationale.html

[1] http://prize.hutter1.net/

[2] http://www.mattmahoney.net/dc/text.html

[3] https://bellard.org/nncp/
As long as AI is sand-boxed in a computer and doesn't have physical limbs, hands, legs, etc then it's safe for now. I think the real trouble starts when these things get mobile and can manipulate matter that isn't just electrons flying around a piece of silicon.
If you work within standard POSIX, sure. But there are many things that are not POSIX that are useful and not available on macOS:

- systemd has some inspiration from launchd, but certainly not its documentation strategy
- `du` doesn't have a `-b` flag (repeat for oodles of useful GNU flags baked into my fingers)
- getting a "pristine" environment on macOS is a true PITA and a horror for CI (containers win massively here)
- some things are only available through the UI (e.g., TCC.db edits are SIP-locked to when Preferences deigns to ask you)
- useful window management (macOS is quite a bit behind even Windows' rudimentary tiling and focus management and even Windows has all kinds of sad quirks compared to what XMonad and Awesome provide)
A Study of Practical Deduplication [pdf]
The graphic depiction of underage people engaged in sex acts is against federal law and most likely Texas law as well. It is baffling to me how the media depicts this as "anti trans" or "anti lgbt" book banning while managing to never mention the specifics of the books.

I'm about as liberal as they come on social issues. But I don't think these books are appropriate in an elementary or middle school library.
Just because a manager can be cruel, it does not make them more effective.

A manager relies on their subordinates to get things done. Breaking trust in this relationship happens often unfortunately and will over time inversely impact the actual getting things done part.

Certain high-profile companies can burn through "expendable" labor. That's because everybody wants to work there for certain reasons.
An Impossible Proof Of Pythagoras – Proving pythagora without circular logic
Context : https://www.theguardian.com/us-news/2023/mar/24/new-orleans-...

The proof itself is nowhere to be find on the presentation. Beside the use of law of sines.
I’m a big fan of AMZN’s approach:

- make an operational plan (OP) for the entire year, which sums up all the HC on your team

- figure out your goals for the year

- have some senior engineers estimate those goals in # of HC (usually 0.5 HC is the lowest granularity)

- add up the HC, prioritize the goals and figure out the cut line against your budget for the year

- when the new year rolls around, start execution. Launch dates are usually set by quarter, with the majority launching by Q3

- individual teams have complete leeway to use whatever project estimation techniques they want. It really doesn’t matter at all. Even waterfall is “fine”. All that matters is whether they can deliver the goals they signed up for in their OP.

- if a goal goes off the rails, report a “traffic light status” (red/yellow/green) and path to green, and engage leadership accordingly to reset expectations.

People accuse this process of being too waterfall / unagile, but it’s actually really helpful in centering the deliverables with business value, while giving teams extreme autonomy to achieve those goals. Mature businesses think in terms of quarters and bottom lines, not sprints and story points.
GitHub does not color the squares green for the past though, does it? I thought GitHub colors the squares green on the day you push the commits to them, not the alleged author date.
5 years ago, somewhere on the internet:

>Anyone that's bought in during the past few years isn't early.

>Those that held pre-2012 are the ones that got in early.

>The rest could probably make better returns speculating in the US markets.
NanoT5 (Encoder-Decoder / Pre-Training and Fine-Tuning)
What was 3.5 about?
I still subscribe to text (and images, but no video), no ads, offline reading news sites on my Kindle. Not through the Kindle subscription but through a local downloader (Calibre).
Blue collar vocational training is more mature than software development vocational training. It's typically taught by people who have professional experience, and there may even be an apprenticeship period where people are explicitly learning from an expert in their profession while on the job.

In software, on the other hand, we often have most training being taught by professional academics who do not understand and are not qualified to teach the parts of the job that don't have a straightforward academic analogue. Combine that with a business environment where things like budgets and cost control are often only theoretical, and all but the most gross liability for defects due to poor workmanship has been waved away by EULAs, let it marinate for several decades, and... yeah. Not only do people not know these things, but I'm not entirely clear on how or why they should be expected to learn them, either.
They're "vandalizing" their own book. It's not our book. It's theirs to do with as they please.

You're allowed to rewrite your own books, too--and even leave the same title on them. At least in the US, the government isn't allowed to stop you.

The publisher's reasons are certainly straightforward:

1. Generate controversy/awareness to make more money.

2. Get last-minute books sales of the "old" version to make more money.

3. Get new book sales of the "new" version to make more money.
It is possible that there is no idea in the history of mankind less punk rock than cryptocurrency.
Accusing someone of not energetically attacking their main income source, whether they thought it was shit at the time or not, is not an own.

Maybe I think I suck at painting, so take it up as a joke to bother a friend of mine. I get lucky and start selling paintings by the busload for thousands of dollars each, although I put no more effort into any of them than the first. In fact, since the first took me over an hour to do, I move exclusively to monochromatic drip paintings. When, a decade and tens of millions of dollars later, after my prices crash, I announce publicly that the art market is stupid... is it shrewd not to believe me?
- Controversial: Children who are allowed to scream continuously. Didn't use to be the case

- Leafblowers. And it feels that their users are the kind that like to rev a 250cc constantly. Not to mention the pollution of a 2stroke engine.

- Trucks backing up. (Newer ones have a much less penetrating noise)

- People honking at all hours of the day

- People closing their car and hitting the close button 23 times as they walk to their apartment, which causes the car to honk every time.

- People who remove straighten parts of their exhaust.

- The guy with the super cool looking Mustang who refuses to put the car in Quiet mode: https://www.youtube.com/watch?v=klS4PFaAUk8

- The Amazon van that beeps every time it goes into park, because it passes by reveres (D -> R -> P) so it beeps. And you think he would park once. But no, every house, 10 houses in a row, break to standstill, put in park, BEEP, stop engine, unbuckle seatbelt, get out, deliver package, get back in, seatbelt, start truck, put it in drive, BEEP, drive 30 feet, ...

- My neighbor downstairs who believes the door MUST be slammed for the lock to work.

I'd love to go and live on a remote patch somewhere. But my employer requires me to be within 30 miles of the office.

Edit: more

- People using speakerphone outside while standing in front of houses

- People (maintenance workers especially) leaving their engine idle for no good reason except AC. That big V8 in that F-350 sounds so low that I can hear it 2 blocks away.

- People
I think you're jumping to conclusions
Source? That isn't true.
>Of course. But the article author doesn't appear to be mocking the MAGA movement, just using an ill-advised expression and photo to make an unrelated point.

The author is just using it as a meme-template of "Make X great again", repurposing something considered tacky as a joke, as countless others have done. Obviously ironically, the same way people would use "Just say no" or other slogans ironically. In fact, it's pretty obvious they're anything but sympathetic to the original thing to use it jockingly like this.

It's time to stop being so negative to anything that's not sterile corporate speak, sanitized six ways from Sunday by HR and marketeers.
Estimations are useful for developers and management. It helps developers prioritize their time and propose more efficient approaches. It helps management track projects and make decisions more efficiently.

Even an open-ended problem has to be scoped into a time-boxed "spike" first that would result into concrete stories which would be sized in story points. Nobody likes to give estimates because it feels like an unfair commitment. These are the rules I follow myself based on my own learnings and advise from others.

1. If I can't feel sure about an estimate in story points then I prepend a time-boxed "spike" to solve that first.

2. Always consider "extra" tasks like tests, data migrations, etc. in the estimate.

3. If my estimate looks bigger than what I can do in half of a sprint if you do scrum then I break it down to smaller stories so I have less risk to have the story rolling over.

4. Add about 20% of padding to all estimations.

5. If you take notes in the story/tickets about all the things adding to the estimation besides common discussions about the work, then you'll get more and more comfortable with your estimations over time.
I have used it several times and it’s fantastic. Exports attachments into properly named media folders and everything.
The carpenter rarely discovers a few days in that the screwdriver they have to use on this project only works every other week. Or that literally every measurement on every component is off by 20% because "that's how it's done" with whatever garbage you stuck them with.

Vendors and even open-source libraries are often liars or just missing what seems like it ought to be obvious functionality. Sometimes tools are just broken. I once was assigned a Java AWS Lambda project, which, great, supported, right, says so right on the website? Except half the CLI tool functionality just didn't work, at the time, for Java projects, and I mean the official tools. It was alpha-tier supported at best. Usable, sorta, kinda, but you're gonna lose some time un-fucking the situation, and the whole thing would be slower to develop than it needed to be. You'd not know that unless you went and did a focused search on their issue tracker(s), which isn't really reasonable to do for all the stuff you might use in a typical project (some of which you might not even know you need until you've started work). "Great, so now you know that for estimating next time, if you get assigned a task exactly like that one" well, no, not really, because that was like four years ago and the situation's probably totally different now (maybe better, maybe worse, who knows?)

That's why I think giving 4-8 weeks of development time with some basic t-shirt sizing or pointing for tasks and just seeing how it's going is better, before estimating. I think if you can't afford that, before getting the estimate, you can't afford a half-decent estimate at all and just need to deal with the fact you're going to get a terrible estimate with an absolutely huge range ("six to eighteen months"). Which, fine to ask for that up front then refine it after some dev time! It just needs to be clear and expected that those early estimates are going to have some wild variance—but they can definitely tell you "is this more a 1-year project, or more a 5-year project?" which does have some real value.
3) bring it up to make sure she is aware of this possibly new information, and assume she will use it to inform her decision making? What do you think I meant by providing input to her decision? What on earth made you pull out the straw man that you can’t even influence them?
> The total crypto market cap collapsed because of interest rate hikes.

It's constantly been peaking and collapsing since 2013, when there were no US interest rate increases. The 2017 peak happened in the middle of a US interest rate increase cycle. The 2021 peak happened 6 months before the most recent US interest rate increase cycle. I'm sure interest rates were varying in other countries on different schedules, but blaming a crypto market collapse on interest rate hikes doesn't seem to square with the data.
May I ask how you identified them as silicon bugs? And by silicon bugs do you mean random bit flips, or something else?
Should the action substitute cookiecutter? I see `src/{{cookiecutter.repository}}` after generation
The Lesser-Known History of African-American Cowboys
Whilst it's headlines only, FreshNews.org still exists (and after a scare last year has been updated to function with today's site engineering), and provides a dense presentation of (mostly tech-related) stories from 33 sites (default, customisable with a log-in):

<https://freshnews.org/>
How do you pronounce the name of the town Reading, PA?

https://www.howtopronounce.com/reading-pennsylvania-2
The beauty is that Linux can be as easy or complicated as you want it to be.

Fedora (GNOME/Wayland) is simple to install and use. As a long time Arch user (since 2010) I appreciate the modularity and freedom to customize exactly what I want. A few years ago I switched to Fedora on my main laptop – I learnt a lot tinkering with Arch but had to switch gears and focus on getting other stuff done.

The only caveat is that you have to be picky when choosing a laptop if you want to avoid installing propitiatory wifi-drivers or adding kernel parameters, but these days there are a decent amount of laptops that works without tinkering.
Yes, because our entitlement expands even faster than GPT's capabilities.
Yep! Except lambda limits are 10Gb [0],so this doesn't work.

If you ask ChatGPT to generate a template for a lambda with 16 vCPUs, it will generate a template that allows a max of 16 concurrent invocations, which again is not what you asked it for, and unless you _know_ what reserved concurrenct executions are, you won't know that's what it's generated.

[0] https://docs.aws.amazon.com/lambda/latest/operatorguide/comp....
Why not divert that interest into the world of secure private and/or anonymous chat and networking protocols?

The flow of information and ideas is more valuable than currency, and there is increasing pressure to legislate it out of existence.
Can you expand more? This seems like an important insight to me.
Does your comment also cover not trusting exchanges that back stable coins with pure fraud or pump and dump coins before listing them on their exchanges... Or does this only cover companies and individuals that think crypto has yet to find a good Avenue in society?
I'm sure part of it for me has to be the efistub. I don't understand why anyone would want to bother with a bootloader in modern times because efi will let you pick and choose what to boot just fine without one.

Clobbered bootloader is also why your system goes back to windows after an update (windows has always had issues cohabiting with other operating systems that weren't windows)
> No, the crypto mining industry collapsed because the largest GPU-mined cryptocurrency (Ethereum) removed the ability for people to mine it with GPUs. Crypto obviously does not "need parallel processing" in the way that Nvidia GPUs provide it, because Ethereum removed that requirement entirely.

Absolutely correct.

At least cryptocurrencies like Ethereum found an alternative consensus method that is efficient and environmentally friendly, unlike what I am seeing in AI and deep neural networks for decades which that still has not changed with the way on how models continue to get larger and require more planet incinerating power and will currently require millions and in the future, billions of dollars to train. As long as they stay inefficient, Nvidia will continue smiling knowing that.

The end result is a pseduo-intelligent black box that confidently hallucinates and can get confused by a single bad input - rendering it useless. Once it all goes wrong, then it gets re-trained / fine-tuned again, wasting more energy. Inference requiring tons of GPUs is also wasteful and inefficient.

The moment we switch to better and efficient alternative in training deep neural networks at scale, that I would call a 'breakthrough' in AI rather than throwing more data, more GPUs at the problem.
While that's true when you would like a meaningful learning experience, a lot of times search is aimed to obtain a factual answer (especially if it exists). I'm of the opinion that for a lot of questions with no deep answer required, Google would have to struggle against ChatGPT as per the current state of things.