skysight-inc/HackerNews huggingface dataset:
This comment got me thinking “What do you notice that is incorrect or important but missing from this page?” I discovered two things: 1) I’m too shallow in Python to identify any such issues and 2) while GPT-4 and Sage struggled with that precise question, in about 3 seconds I got what appears to be a really useful critique from Claude 2 100k. I’ll share that in case anybody is interested:

___

Here are a few things I noticed that could be improved on the Python cheatsheet page:

- The dictionary section is missing explanation of dict comprehensions. Dict comprehensions are an important and useful feature for constructing dictionaries in a concise way.

- In the section on modules, it would be good to mention virtual environments. Virtual environments are an important tool for Python dependency and package management.

- The examples in the Pandas section are useful, but more explanation or details could be provided on some of the core DataFrame operations like merging/joining, groupby, aggregations, etc.

- In the sections on concurrency and parallelism, async/await could be explained and demonstrated. Asyncio is commonly used for asynchronous programming in Python.

- The cheatsheet focuses mainly on built-in modules and functionality. It could be useful to also cover some widely used 3rd party libraries like NumPy, SciPy, Matplotlib, TensorFlow, etc.

- Sections on testing and debugging could be added - things like unittest, pytest, logging, debugging tools. Testing and debugging are key skills for Python developers.

- The cheatsheet is very text heavy. More visuals, diagrams, or tables could help make it more scannable and easier to navigate.

Overall it covers a lot of ground, but filling in some of those gaps would make it more comprehensive and useful as a reference. The content is excellent, just some ways it could be expanded on.
Our government has definitely shows that they can implement complex websites
I assume IBM Message Queue Interface (MQI) is the only supported protocol in this installation. Don't know of any other compatible brokers to support MQI.

Edit: "The FedNow Service will initially leverage IBM® MQ MQi Client for the payment message flows." according to https://www.frbservices.org/financial-services/fednow/blog/a...
> “Mental images fill our daydreams, fuel our fancies, and color our memories. People often experience these images as richly detailed, making the imagination seem like a talented artist quickly painting a lifelike scene before our mind’s eye. Our results suggest that while the imagination may indeed be a good artist, it’s on a deadline, and stingy about paint.”
Not for calls / VC - the quality is trash compared to FaceTime
Hacker News is just r/roastme for programmers
Good infrastructure is too.
I had a colleague deploy the power whip for the last available rack position on his way out the door.

Years later when I desperately needed that rack to keep the site up I was able to roll it in and light it up without waiting 6weeks for an electrician change request.

He saved my bacon by thinking ahead. It was a gift he gave me, never mentioned and was not around to receive thanks for.

I aspire to be more like him in everything I do.
Maybe worth looking into: https://news.ycombinator.com/item?id=36750083
Was hoping it would be about Kierkegaard:

https://en.wikipedia.org/wiki/Either/Or
Can you link an instance of this happening or is this entirely speculation on your part?
Can't stop cash, cash is a fact.
Archaeological evidence suggests the pyramids were built by paid laborers who got free food and housing, rather than slaves. That's a better deal than most workers get today.
Surprised they're using Fargate here rather than an EC2-based cluster.

We use Fargate but we have very spiky traffic and have a very small team.

I would have expected a larger company with a relatively predictable traffic load to use an EC2 cluster to cut down on cost.
Ironically, that anecdote also paints a good reason to sample the data on how long it takes to get there. If you check your own history for how long it takes to get somewhere, it is probably far more predictable than you'd expect.

Of course, this also explains why software estimates are hard. We are all too often estimating things we haven't done before.
No. In my case it'd be same days (15th and 1st) as paydays, or earlier if the payday falls in the weekend or holidays.
My personal experience is that the majority of developers I ever encounter at work (as opposed to within my social network) are usually slow because they're bad engineers who don't understand problems quickly, don't have the knowledge or experience to see solutions quickly, and in general don't think deeply quickly. It's not hard to 3x performance without sacrifices when the baseline is mediocre at best.

"Fast must be cutting corners and not just actually better at programming" is a weird fallacy to hang your hat on.
Yet most US constituents, of all parties and socioeconomic status, seethe at the thought of a government worker of any level making “too much” money.

It doesn’t matter that someone working for the government has the potential to have a much higher impact on a nationwide level than some rank and file worker who works at some blue chip auto insurance company, the moment increased pay for government workers is even brought up, that person imagines it as coming directly out of their paycheck.

See teachers, urban planners, sanitary workers, NASA scientists, etc…

It’s a shame, because I have the unpopular opinion that _more_ government, filled with talented people who actually want to _fix_ the issues they’re passionate about, is the answer to almost all of the USs domestic problems. Right now the highest paid government workers are those on the brink of retirement in administrative positions so far removed from any real work. A bureaucracy of gerontocracy, if you will. I really wish the government (not the political world, but the civil staff) was seen as as a place for passionate young people to aspire to, with the pay to match.
poorly designed web components are so painful because of that
You didn't (nor did I suggest you did); someone else did; that's what started this sub-thread.
The thing that struck me from this book (or maybe it was in "Dark Sun") was how much the soviets were spying. We were giving them detailed plans for chemical factories, tire factories, engines, alloys, anything you can think of. They did not trust us so they would spy on all this stuff anyway. They would fill up a C-47 Skytrains(lend-lease) with stolen documents and fly them out to Moscow through Alaska.

I have to give the soviets the win on this one. Their spying was very effective. All that spying let them get the bomb PDQ.
OMG. Tks
Credit card fees that aren’t passed through to you are a bit tragedy of the commons. Probably good for them to go away. It’s fine if you choose to pay them, and it’s still worth it to you, but otherwise you’re forcing everyone around you to subsidize your credit card rewards. That’s not fair.
Last time, a decade ago, I played with RabbitMQ and similar open source queue system they didn't handle congestion and rate limitation well (crashed). From my little experience with classical IBM systems like MQ they knew about that stuff.
Yeah that’s about 100x more than I can afford exactly.

I think I will go back to my little collection of RPi Compute Module machines. And maybe some day in the very distant future I can buy big boy servers lol
I wonder what % of readers here do programming in their day to day. Definitely a good amount but I don't think it is the majority.
FedNow intends to support aliases such as phone number and email identifiers in the near future.
> The expectation in the industry is that there will eventually be interoperability between these systems

Why? Why would the companies presumably making good money with Zelle interoperate with something that's stealing their customers? It seems like there's no advantage for the entity running Zelle to allow interoperability, and there might even be ToS language preventing any bank or credit union currently in Zelle from so much as moving towards FedNow.
> Evidently, you couldn't easily tell why it was there.

No, they could tell why it was there. It's just that knowing why it was there in the first place doesn't tell you what it's doing now.
> "Every time Software is used to fix a [Electrical/Mechanical] problem, a Gremlin is born"

Gizmo caca.

(...I just watched both Gremlins movies last weekend...)
Good code is not like art, such as good books or paintings.
No matter the quality of your code, if the product or service is not a good market fit. It will be retired. No one will stumble upon it or pick it up after it's gone. Knowing this, the only reason for putting effort into it is to make it easier for myself.
The user and the operator.
> This is a concept I've run into a lot when making changes to complex computer systems. It's useful to look back through the change history, read original design documents, and understand why a component was built the way it was. But you also need to look closely at how the component integrates into the system today, where it can easily have taken on additional roles.

We're probably at a stage where doing this in an automated fashion might be reasonable. The context for why something works a particular way (say in some github repo) is the commit message and change detail, the PR, related issues, related chats in <chat tool of choice>, and then things temporally related to those. Feeding an LLM with the context and generating ADRs for an entire project automatically could be a feasible approach.
I’m annoyed too, because I love C and back in the 90s languages like Turbo C and Microsoft C were quite intuitive to use from the command line and using whatever old editor you wanted. I would still very happily be using modern C if the overall experience were like Go.
This is what nix lets you do basically
https://github.com/Cloudef/nixos-flake/blob/master/flake.nix...
as well as this
https://github.com/Cloudef/nixos-flake/blob/master/modules/d...

Also here I'm referring to specific version of zig for this particular LSP's config file, but it never goes to my PATH https://github.com/Cloudef/nixos-flake/blob/master/modules/n...
It is a step, a big one, to their "dream" of a "cashless society" that we have been on for decades.
> It's interesting how Nix's selling point is that its non-standard file system structure allows multiple versions/flavors of the same package to be installed at the same time, yet if I understand correctly, it often has one version per package per Nix version?

You're talking about Nixpkgs, and it's a cultural choice. In the past there used to be more of this, where e.g. the Haskell community had lots of variants of the same library all at once, because users and other libraries wanted them. But it became untenable to maintain and you in practice have to do tons of effort to vendor things. And once many of the subcommunities began moving to auto-generated packages (e.g. generating Nix packages from Haskell packages), it becomes much easier to have a single globally consistent repository of versions that all are known to work together, generated by the host-language dependency resolver, with minor fixes applied on demand.

There are some things that do have multiple versions in the main repository, e.g. LLVM. But in practice having like 10 versions of everything is a huge chore and only done on demand in practice if users want it, and it has real overhead cognitively and in build time and in maintainer time.

You can define your own Nix flake with every version of every Python library in it if you want. But in practice people sort of pick versions of things that make QA a real chore.

EDIT: Also, for like 99% of cases, what users think is cool but hardly do is to run both pieces of software at the exact same time concurrently. They typically just want atomic upgrades and rollbacks. For example, you change your git revision at work and get whole new tools, your old tools still work if you go back to the old git revision at no loss. So the need to only have one version "globally" under one name isn't a big deal in practice, because people often are only dealing with one global name. They just don't want their packages to get corrupted during an upgrade or switchover or something otherwise breaks.
Encapsulation might be overkill for a single developer, but it very much matters for teams and using third-party components.

If you want to drop in a calendar component into your page from npm, it helps if that component's styles don't leak into the page, and if page scripts don't accidentally mess with component internals.
Because OP is not critically thinking.

They have a very simple idea of market mechanics with very simple ideas of market manipulation.

If our market isn't working, it's just not "pure" enough, right?

https://en.wikipedia.org/wiki/Anti-competitive_practices

https://en.wikipedia.org/wiki/History_of_competition_law

https://en.wikipedia.org/wiki/Natural_monopoly

https://en.wikipedia.org/wiki/Tacit_collusion

https://en.wikipedia.org/wiki/Regulatory_capture

https://en.wikipedia.org/wiki/Tragedy_of_the_commons

I don't think OP has read very many books and I would be surprised if they have a bachelors degree. OP reminds me of myself during Ron Paul's "the free market solves all problems" period on Reddit. Ron Paul presented a very simple idea of how things work, but once you start to think about how those ideas don't work, it's obvious that ignorance is being taken advantage of.

Alternatively he did not respond to the best most charitable interpretation of the post. Simply put: OP's ideas wouldn't last (and aren't lasting) long outside of an ideological echo chamber.

I think a strong obvious argument against a "less regulation" panacea is that we couldn't make our own masks because the free market sent all the production to China. Sending all of our manufacturing to China because they offered the best deal gives china incredible leverage over us. Clearly the "free market" must be analyzed not just in terms of supply and demand, but also in terms of power and coercion. There is no supply/demand curve for power.
Security consultant.
> i'm not performing censorship by selecting which files i download from the internet, am i?

Yes, because that's an irrelevant activity to this topic.

> yes, this is very important, which is exactly why a library like this selecting which works to include is not censorship.

At least in contemporary liberal culture, words like "censorship" and "ban" are frequently used to label "criteria for inclusion" that the speaker disagrees with.

> now if people intentionally submitted their own works and the library tried to hide or deny the existence of those requests, now that would be censorship

That's one kind of censorship, but not the only kind (see above).
Who do you think that's going to be? Certainly no plumber or bricklayer is worried.
Nothing beats the feeling of having a coworker suggest what might be a substantial change to a codebase you haven't touched in months, only for you to look at the code and realize that the way you wrote it makes it a one- or two-line change.
maybe worth looking into: https://news.ycombinator.com/item?id=36750083
This might be a better cite for the "oil shock" thesis:

https://www.jstor.org/stable/24808741

Assuming JSTOR still works for anyone.

Regardless, my thesis wasn't that the USSR collapsed entirely because of an oil shock. It was that the USSR had severe structural problems and couldn't weather adversities such as the oil shock.
I hope your meaning of "glib" was "I'm describing a bunch of technologies that should not exist".
Fair, but there are ready-to-go Linux configurations for RPi that assume you'll do "normal" things like talk to USB devices and the network.

Additionally, Linux has available a multitude of very rich in-band debugging and logging capabilities that help you understand and mitigate common problems— whereas a bad interrupt or peripheral configuration on some microcontroller could have you banging your head again a GDB frontend or shelling out thousands for a tool like Tracealyzer to tell you what on earth is going on with it.
Passive voice, better title is Kevin Mitnick died, or passed away, sugar coat it like he never did if you want, we all know what it means. I suddenly feel bad for him, though. He deserved the black ribbon.
So prompt engineers could be promptsmiths?
Is this supposed to be ironic? Your first sentence was a metaphor.
I totally get it. I’m quite familiar with logo. But on the surface, it simply doesn’t look like what most managers are going to see these days.
> You are persistently surveilled in London and Shanghai and New York City - yet people act just as unhinged in ways they did before cameras were installed.

Unhinged people do, but ordinary people? I'd be willing to bet that normal people who are in areas where they are aware they're on camera don't behave as their normal selves. It's hard to see how it could be otherwise.
The US doesn't see Poland as US territory, and cares rather less for Polish citizens than American ones.
There is always a cost to everything.
Continued US intervention in Honduras for over a century has turned it into a wasteland. We've been involved in setting up puppet governments there and knocking them down when they seemed inconvenient since the US fought wars over fruit instead of oil. We're "spreading democracy" by denying the results of democratic elections (which we do abroad more than we do at home!). And then we turned Honduras into a CIA-backed narco-state.

If Hondurans happen to do the same to admittedly sketchy parts of the US, it's reciprocity at worst.

Want to keep that from happening? Maybe reign in foreign policy. And maybe start supporting local people's choices and helping them toward liberty and prosperity instead of treating them like others to be exploited for yankee dollar.
> The beauty of our creations, however, is not judged solely by the elegance of our algorithms or the efficiency of our code, but by the joy and ease with which others can build upon our work.

Often this is not true. Our creations are judged by the user. They don't care how good it is under the hood. They care that it works correctly, that it's easy to use and that it's as fast as they need it to be.

Your boss should care that it's well written because that should mean it's cheaper to maintain. But, they don't look that far into the future when evaluating your performance. So, often they only care about how fast you did it and how happy the customer is with it.

Our industries incentives don't often align with good code.
Ah! Well. Nevertheless.
Companies are made up of people, who absolutely have stances.
Why can’t good code be all of the above?

Thinking about code this way takes nothing away from appropriately deep explorations of nuance.

They coexist without issue.
"Address" would be have a serious discussion about the priorities - both fiscally and socially - of the United States.

In a sense you're right that the US Space Program is a drop in the bucket compared to other spending but Gil Scott-Heron's poem was never a financial proposal. It was trying to express a sentiment that the US government's priorities were messed up, something that still resonates today.
I have no idea how to code, yet have boiler plate GPT code in production. No interest in learning, it's not for me. I like this site for the diversity of topics and information.
What I make is irrelevant. I do not care for your victim blaming, either. I see that we cannot continue this conversation in good faith. You take care.
> There is always a cost to everything.

There's a huge cost to having engineers who are bad at understanding and solving problems. The cost of having people who are good at understanding and solving problems is supposed to be that you pay them more, but that's not how employment incentive structures work in practice because information asymmetry and stigma around talking about salaries.
OO was already invented and Simula 67 is even referenced in the paper, but not yet recognized or understood in its significance; the claim about Algol 60 ("an improvement .. on nearly all its successors") is pretty bold.
You can pry CarPlay from my cold dying hands.
I used to think that it was biased towards profit, but after the last 5 or so years, I think that's just a side effect. American society believes strict and long punishment for wrongdoing is the solution to crime. We had a wave of progressive AD's elected into office and they barely lasted 3 years, they're all getting booted.
Hell of a day to quit sniffing glue.
The fact that you are explaining this to me reinforces my point.

One of my primary criteria in choosing a technology to work with its how accessible is community support, documentation, third party articles and writing.

It had better be a compelling technology that names its main things exactly the same as the biggest concepts in web development, thereby making it a battle to resolve questions and issues and adding unnecessary confusion.

I do use a nodejs library called "Postgres" which provides a Postgres SQL driver but I really hate the fact that searching for documentation/issues is essentially impossible. I use it because I feel I had no choice, it's the best possible technical solution.

Names matter.

Searchability matters a huge amount.
Apple has already built its own ChatGPT-like chatbot
Agreed. This seems to almost rationalize being a sociopath. You can't change the past. The world has no shortage of extremely shitty people who have no regard for others.
It’s essentially prompt engineering as a service with some basic quality-control features thrown in.

Sure, your engineers could implement it themselves, but don’t they have better things to do?
Once the service provider is connected to the Fed (a somewhat complex process), it's normal software development. The client uses either MQI or JMS to send and receive messages; the messages are essentially ISO20022 XML. The development environment could be anything (any OS, any IDE). You interface those messages with your system of accounts. The Fed also provides a simple web UI and a testing network where you can test with other participants and run regression tests.

From a software development perspective, it's really quite normal.
I really don't quite understand what is up with either of these stocks.
70% of Russian Gamers Are Pirates Following Western Publisher Exodus
https://www.motherjones.com/politics/2023/02/kiwi-farms-die-...

https://fortune.com/2022/09/05/kiwi-farms-so-bad-cloudflare-...

It is anything but false. They bragged about their kill count. Do you have any source for your claim?
If v3 is "not released" then having it accessible with the other 2 releases is contradictory - this "prerelease" is still a form of release; no claim was made that the entirety of the v2 documentation was deprecated.
When I do personal projects for myself, I try to comment them really well for this exact reason.

Just today in fact I was trying to update some code I wrote two years ago because one of the underlying tools broke. I was very happy with past me for commenting the workflow of that tool so I could easily work around it.
If you say "just" then you're trying to justify it without effort. Most of the people I interact with have ADHD and yes it's annoying as fuck but I don't fault them or blame them when they communicate in good faith. Using "just" to justify it means it's bad faith.

You choose to open tabs. Don't open tabs if you know you cannot handle that.
It does, including at least a shell, a C++ compiler, make, and a bunch of other UNIX/GNU tools to run the whole thing. And where do you get those programs from, and can you trust them? If you look really seriously, a scary problem emerges. (See: Trusting Trust Attack)

The Guix project recently hit a massive milestone in untangling this, by creating a package set which starts by building a 357-byte program and works its way up to the utilities you'd expect: https://guix.gnu.org/blog/2023/the-full-source-bootstrap-bui...