skysight-inc/HackerNews huggingface dataset:
47 CFR § 97.403: Safety of life and protection of property.

> No provision of these rules prevents the use by an amateur station of any means of radiocommunication at its disposal to provide essential communication needs in connection with the immediate safety of human life and immediate protection of property when normal communication systems are not available.
Is that slide deck publicly available?
Can’t you do that today though? ie. Circumvent your meter? It’s illegal though.
FWIW, the OP repo uses a Terraform config to deploy the server on a 4GBRAM server on DigitalOcean.[1] Which costs $20/mon and has 4TB/mon bandwidth allowance.[2]

To give a sense of what a 4TB bandwidth could cover: 320 people watching a 3hr stream at 1080p or 70mb per minute.

[1] https://github.com/benwilber/boltstream/blob/master/terrafor...
[2] https://www.digitalocean.com/community/tools/bandwidth?activ...
Most problems are multi causal and if you have blame culture will degenerate into a litany of finger pointing.
The more I read about legacy (and actively maintained) project refactoring, the more firmly I find myself agreeing that the gradual replacement is the right way to go about things in nearly every case.

Whether we like it or not, the old system is a source of truth about how things are done, so the only way to preserve this knowledge fully is to copy the whole thing as-is and then "restate" parts of that knowledge in a more organised/modern way by refactoring, leaving the rest in place.
My experience is the same as the author's. If one defines top performer as you did, those who are "more focused on big ideas such as the structurally important parts of the architecture", and you run the numbers, you'll find most of these people will also be outliers in commit count.

This is true in just about every team I've worked in. And it makes sense too. The person who best understands the design would be the fastest to implement it. They can both do the design and implement 2/3 of it in the time it takes the other engineer to grok the design and fumble through the other third.

Frankly, I think the role of "design architect" is make-believe. A project only has so much "design work" to be done, so the top dev isn't going to be sitting around twiddling their thumbs through the implementation phase. Even people like Jeff Dean still write a ton of code, to my understanding.

What you describe in the second paragraph sounds like something that would occur only in a dysfunctional workplace with dysfunctional manager and dysfunctional colleagues. (And even then I have a hard time seeing it happen for long -- someone is going to get annoyed doing all those code reviews of pointless changes and put a stop to it).
OP mentions three things: staging their work, velocity, and sense of agency/ownership. All three are problematic. Often those who have worked with a component the longest and/or wrote significant parts of it become its maintainers, either formally or de facto. As a maintainer (I've been one myself) it's simply easier to get commits in, not necessarily because you're better at the work but because of the role itself. You never have to re-work your commits to conform to someone else's idea of how things should work. People trust you, so reviews are often cursory. Many maintainers return that courtesy by subjecting others' work to excruciating review, slowing them down. Sometimes it's intentional, sometimes not, but the result's the same. Also, a maintainer often has many commits that started off as someone else's idea but that person didn't have the time or knowledge to complete them, so those are kind of low-hanging fruit that inflate the numbers. A mediocre maintainer will usually still have more commits than even the most talented non-maintainer. Calling them "top performers" because of something that's part of the role seems a bit circular.

So much for velocity and ownership. As for the part about staging commits, I'd like to see some evidence. In my experience there's no difference, or sometimes the maintainers are even less likely to break up commits. This can be because maintainers are often charged with making commits with lots of internal dependencies that make them harder to break up, or because it's easy to get a stamp even on a questionable commit from people who are dependent on their goodwill to get their own commits in.
If all that comes along then great, take advantage of it. But right now there are no hydrogen planes rolling off the production line in Seattle. Carbon capture has been hyped for a long time now but we aren't seeing anything substantial happening.

Which leaves us in the situation that if you get on a plane to cross the Atlantic today you will add another ton of CO2 to the atmosphere.

Carrying on as we are right now is like spending next years pay rise before you have got the promotion, it will bankrupt us.
a "track record" is biased toward those who inflate their resume

Could you explain this a bit? I'd have thought this is the only real way to judge someone. People will lie but figuring that out is part of the process.
Oh, buddy. Time to get out of your bubble.
The two top performers in my organization definitely don't have a lot of commits. Instead, I would say their strongest skill is written communication; in emails, log messages, code review comments, and chat messages.
I like Wikipedia as it is now. I presume Jimmy is responsible for this. I feel it’s going to be 5 years before Wikipedia is plastered in ads with selective editing rights going to paid sponsors if he’s gone.
Kubernetes or Serverless? Why not both?
Imagine thinking your 90W boat anchor is a "mobile device".
Interesting how at this point in history it was thought that the Egyptians knew alchemical secrets that were lost in time.

Fun little bit of etymological history: chemistry comes from alchemy which is a translation from an arabic phrase to mean 'from Egypt'. https://www.etymonline.com/word/alchemy
Continuous Organizations (2018)
You sign a contract with a shipping company, and you can choose not to sign it. Can you choose not to use a country's road system?
Channel 3 (or 4) was also commonly the channel used by various peripherals like VCRs and composite adapters.

I have fond memories of tuning the TV to channel 3 to play Nintendo as a kid. This would make for an interesting retro gaming experience.

I wonder if it is easily adapted to use coax cable instead of an antenna.
Which is one of the reasons why coding standards like MISRA forbid using strlen (at least in C++, I guess even MISRA doesn't want to force you to write safer C with sane string types).
There are loads of amazing devices out there. My home security system runs on a Jetson Nano and a bespoke solution, with image processing using Tensorflow, fed via GStreamer. I'm going to replace it at some point with a Xavier NX.

Amazon has Gravitron 2. Microsoft is doing something with "their" SQ2, though at this point they're mostly faking it by putting a badge on an uncompetitive Qualcomm part, but I'm sure they'll get there.

The M1 is a wonderful chip, and it has done loads to push the industry to really adopt ARM -- possibly the greatest fat-computing transition to ARM yet -- and it should help across every market, and loads of hardware from competitors.
Who will be the target market for these cores?

Is apple going after gamers? A good gaming core is different than a good general purpose cpu. And apple has many more fundamental problems re gaming than a lack of horsepower.

If apple going after server market? I don't think so. Apple products may be efficient but they simply cost too much and I don't see the apple premium going away. A cpu with a mix of cores is also not as directly scalable.

I think apple is still going after that "core" apple user, the one that appears in all the commercials. They work at a graphics design office in the village. They have a phone/tablet for email and a desktop PC for serious photoshop work. That's the target market: The desktop PC that needs to on occasion push through a few minutes of photoshop rendering, not gamers or others who will run these CPUs at full throttle for hours. The cpu needs to be power-efficient (ie quiet) 95% of the time, but remain able to ramp up on occasion to complete a task. Rather than solid power it has a mix of cores to address whatever is thrown at it as elegantly/quietly as possible.
Design is very important in the hardware industry.

By your definition, fabless companies like AMD or NVIDIA aren't HW giants, which is absurd.
Lots of respect for such small country to set an example for the “bigger” countries to try follow, commendable and bravo !
Well then just use a hardcoded one by default but allow the user to set one manually and then use that.
Would this work on a Raspberry Pi? It also has a GPIO3 interface.

https://pinout.xyz/pinout/pin5_gpio3
PseudoTex – Pseudocode to LaTex
This is a pseudocode to latex "translator" written in Rust.
I realised that writing pseudocode in the algorithm2e syntax was awful and so error prone that I decided to build this tool as a side project. It is by no means as optimised or clean as I would like, but it is at a state I now consider usable. If you ever had to write pseudocode in LaTex I think you can understand the pain.
The pseudocode syntax described in the paper is simple and powerful enough to contemplate pretty much any use case. I'm interested in reading your opinions and observations and who knows even contributions. Thank you.

Link: https://github.com/bruno-anjos/PseudoTex
It depends how aggressively your reformatter changes your code. For example, Prettier will take this JavaScript line:

document.addEventListener('keydown', e => { console.log(e) });

and convert it to this, which changes both whitespace and syntax:

document.addEventListener("keydown", (e) => {
console.log(e);
});

I don't think there are any diff tools that can hide the differences there, even though they're superficial.

[0] https://prettier.io/
It might be nonsense if you believe that making energy more expensive is virtuous. I am unconvinced that's the case.
But in this case the blockchain implementation will provide irrefutable evidence to support any investigation. It's not some magical hand-wavy substitute for investigation, but recording this in a tamper-resistent manner can be useful (although blockchains are far from the only way to do this).
The Efficiency Metric Every Recurring Revenue Startup Should Be Tracking
> There were no LCD screen for laptops either in 2010.

I remember using laptops with LCD screens in 2010, and even before. They weren't even Apple laptops.
The US digged itself in pretty well.
> Have I missed something?

The first chapter of the whitepaper? [1] There's two sides entering a contractual agreement around energy consumption.

[1] Section 1.2 - https://efforce.io/WP_ENG_V1.pdf
Metal Monolith Appears in UK
Obviously these are people problems. If my next team suffers from your first problem, I might try to ease it by introducing a code formatting tool like prettier. I don't always love the choices those tools make, but I do love eliminating that class of PR comment.

It doesn't eliminate the people problem, but it does limit its scope.
Not exactly what you're looking for, but I talked to a developer of a solution that integrates with online banking and recognizes subscriptions and allow you to cancel them directly from your online banking thingy.

Only downside is that it's the banks that has to do the integration. I can't really figure out how they deal with the actual unsubscribing bit. The subscriptions people are most likely to want to cancel has to be those who with the worst unsubscribe process.
squashing commits make history important actually. The history how you reached the solution in your branch is not important, I am not interested in a wip commit which could indeed have a valid commit message, but still not final. Only the committed is interested into that.

So I think just before merging squashing the commits makes completely sense. Before that the committer is free to do whatever he/she likes.

Of course in the case the diff of files is so big that make multiple commits sensible, means that the PR is not broken correctly. Then, it's fine to have multiple commits, but the problem is elsewhere not in squashing them.
Sure. There are lots of risks. But does the insurance policy actually cover those risks? Scaring people into buying insurance is a fun time, but it feels like half the time the things they scare you with aren't even covered.
>Although, I can't help but read your comment as satire! "What if PC components were modular!" I also enjoy building sets from LEGO bricks, and putting together my computer from parts!

Huh? They're saying you won't be able to do that with an Apple CPU.
Please keep cheap political gimmicks off this site.
Just as a note. I think this needs better SEO.
I closed this tab and later searched on Google for Cymbol and then Cymbols and nothing came up.
I found it only when searching for the full domain Cymbols.io
Personally I'm aware of three that I'd count as good use-cases. Only one of those is a cryptocurrency.
For those unfamiliar, Knuth's versioning scheme approaches pi and therefore never reaches 4.0 [0]

> In his seminal text layout system, TeX, and his equally brilliant typeface design system, METAFONT, Donald uses a versioning number system that asymptotically approaches perfection. The version numbers of TeX approach π (the current version is 3.14159265) and the version numbers of METAFONT approach e.

[0] http://sentimentalversioning.org/
I don't think they will ever be interested in the datacenter again. Making consumer products is in their DNA, servers isn't.
I’d be happy with a 16 core M2, extremely happy!
I'm just reading this before work, but it must warrant more follow up. Wales doesn't want to step down until Wikipedia is safe from "outside interests who do not understand our values". It's easy to imagine the sort of folks who'd want control of Wikipedia.

Was it earlier this year that we narrowly avoided the .org sale to a vague corporation? It'd be tragic to see Wikipedia meet that fate as well!
I agree CO2 has become a red herring. But I believe a lot of intelligent people supported its use for a long time not out of malice, but because it was a single metric that, while not a very good proxy for the various pollutants that are emitted by large polluters, was probably the best single proxy available.
Yup, it's amazing how intelligence sources get passes 100% of the time. "High ranking CIA source says..." is assumed to be 100% true.

That's a pretty big assumption that is no doubt abused.

I love Matt Taibbi's example where the FBI got a search warrant, based on a news article that they were the source on. Talk about compromised incentives.
If the only way to cheat is illegal and can be done on the Blockchain anyway then why use a Blockchain rather than a database?
“I think the next leap forward in programming is going to offend the sensibilities of current programmers.”

Honestly, programmers have been railing against progress ever since the first machine coders shook their canes at those ghastly upstart programming languages now tearing up their lawns.

Meanwhile, what often does pass for “progress” amounts to anything but:

https://fermatslibrary.com/s/the-emperors-old-clothes

--

“It’s a curious thing about our industry: not only do we not learn from our mistakes, we also don’t learn from our successes.” – Keith Braithwaite
> If they find an issue along the way, they make a note of it and come back to fix it. Or they might fix in as they go.

One consistent tension is that the old-hand developers have a "mental issue queue" that is enormous, but without fail, every time, they just can't be transferred.

These can't be made into issues and farmed out to other people. Inconsistencies in the data model, for instance, might exist, but a better solution isn't obvious. You can hand it to someone fresh, and after significant effort (on both of your parts) they agree with the inconsistency, but they won't propose a solution that's any better.

Once you've contributed enough of the main functions of a code base, you just never lack for something to do. All code is bad, because the business focus is on expansion of responsibilities over refinement of the existing ones.

Those ghost issues are best communicated with a code change, at which all observers say WOW WHY DID WE NOT SEE THIS?! But the issue without the code change gets gawking blank stares.

EDIT: but fixing unrelated issues as you go is bad, don't do it!
Advertisers can make accounts on Reddit and other forums and do product placement there or contact people on Instagram or Tiktok to do product placement.

I assume almost all commercial media is chock full of product placement.

I saw a pretty genius idea recently. I logged into a Bank of America cash rewards credit card account, and under a recent transaction at a pizza place, there was a link to a competing pizza place offering 10% cash back, double my usual cash back if I ate there by a certain date.
Does this mean that at some point maybe it'll be possible to just drop it into webassembly?
AI blockchains? Encryption that calls home? Wut?
I'm interested in hearing more about why defensive programming is bad. Do you have some links for me?
I see if differently, the EU governments have made it possible that such kind of help exists, and is actually empowered to protect us.

In US, as far as I am aware it isn't even possible to have such kind of help, and those organizations that do try to help, just go through the same endless court sessions as hiring a random lawyer would do, plus having to pay them way beyond the almost symbolic "Gebühren" that you pay here.

So while the situation isn't perfect, it could be much worse.
The Five Dysfunctions of a high growth technology leadership team
No. I do not see the irony. I am not posting a researched theory here. Also since this is a forum, anybody can point out the smoking gun/honest interpretation whatever. A little burden of proof is on the alternative theories (and I do not go that far to say 'extraordinary claims need extraodinary evidence', I am fine with normal evidence).
>Only if: 1. You are somewhere where using a speaker phone won't annoy other people (or leak secrets to them)

Isn't that an issue even if you're not using speakerphone? Companies regularly ask you for your name/address/birthday/secret question/credit card number, so you'll be leaking that info regardless of whether you're using speakerphone or not.

>2. You have another device to hand, and you have audio recording software set up on that device

that doesn't seem too hard. most people have a old phone or a laptop/tablet, failing that they can borrow one from their SO.

>3. The amount of background noise is low enough that the call is intelligible.

I'm struggling to think of situations where this would be an issue, that isn't already covered by the first point. Are you canceling services on the side of a road or something?
I don't think we even need a citation to refute that.

Have a developer create something modern with technology from 1990. It would be close to impossible. Compared to what was available then, our building blocks are more akin to entire neighborhoods being delivered pre-assembled in order to create instant cities.
My config is sitting at 2046 lines or so. Not as tidy as one of these published configs, but also not a mess either.
> plastered in ads

Besides Jimmy's lovely face?
No, your parent is describing sending two leaf certificates, which won't work.

You can send multiple intermediates, and some clients are intelligent enough to ignore the ones they don't trust. But unfortunately not all clients get this right, and the ones least likely to do so are also the older ones that likely will cease working when Identrust's DST Root CA X3 expires.

A smart modern client (e.g. most current web browsers) will just use anything else you send as a hint that can help it find a way to trust the leaf certificate. You can send irrelevant garbage and it won't count against you, but because other dumber clients exist, you are recommended not to send anything that doesn't form a logical chain of certificates back to a trusted root.

Old versions of OpenSSL for example provide a trust decision framework that assumes any chain you show it is the only valid chain, if that chain is nonsense or untrusted, it gives up and fails immediately, even if it would be obvious to a human shown the same certificates that there's a simple and correct trust path.

This is harder than it might seem because it's a graph problem and the Web PKI graph contains multiple cycles, a naive algorithm may spin uselessly forever or miss "obvious" answers.
Walmart readies for $10 bn Flipkart IPO
Apple will likely have HBM on the 32 core packages, which should provide a significant IPC uplift over the LPDDR4 used in the M1 Macs. I'm pretty certain a 32-core Apple Silicon machine will handily beat a 64 core Zen3, likely at half the power, especially since the AMD's chiplet designs runs into significant memory bandwidth and communication issues.
I was wondering about this with the OP. I wonder what the power level is?
And on mobile the top black bar navigation is broken. Several links are permanently hidden unless you are using desktop mode.
Beliefs About Public Debt and the Demand for Government Spending [pdf]
No, it isn't a misunderstanding, just a statement of fact. If you want the highest price/performance ratio branded products are usually not the place to go, especially not products from companies which produce "luxury" goods. You pay for the branding, the marketing, the right to be part of the community of users just like you pay for the hardware. Those who built 'Hackintosh' style systems spend less money but more time getting their systems up and running.
Sounds like they need to get a backbone.
Experts are sounding the alarm about the hidden dangers of gas stoves
Won't the market just correct them here? If others are willing to pay more for the RCE 0-day, and are more reliable, they'll stop getting the reports and end up scrambling a few times trying to catch up to the curve until they get the message.
I thought it was an EU regulation, but perhaps not. In Denmark you can't bind customers to a mobile contract for more than six month. You can sell them a phone and have them pay that off for 24 months, but that different, you can pay that off at anytime, for a fee.

That's also why you're not getting a new phone from your carrier every two years like most Americans seems to do.
Thanks. People should use that naming technique more often.
The article discusses GPUs in addition to the CPUs.

For example:

> While the current M1 chip comes with either seven or eight GPU cores, Apple is currently testing models with 16 and 32-cores, and is working on chips with as many as 128 for late 2021 or 2022.

I do believe that developer support will be crucial for "serious" gamers, though.
Cyberpunk 2077 Global Release Times
Outputting a TV signal isn’t inherently a problem, surely? Every VCR and 1980s home computer has a circuit that does the same thing. Would only be an issue if you run it through an amp and antenna, rather than just running a wire to a TV, right?
Yes, but that's better than even chances that their load will be preserved. This is part and parcel of the risk of ordering stuff from far away.
If you’re interested in this topic, you should read “How to work effectively with legacy code” by Michael Feathers.
Depending on the workload, that's not as impressive as it sounds at first. Single threaded M1 performance is around 50-60% better than the 18-core Xeon in the iMac (which is impressive). But high-core CPUs are typically slower per core. I have plenty of programs that run faster on my dual core laptop than on the 16 and 24 core Xeon servers at work.
> However, I've never seen anything to suggest a huge difference between the number of programmers who know C++ and the number who know Python

Anecdotal evidence here but, I hire for both and it’s definitely easier to find developers that actually know Python and what Pythonic code looks like.