skysight-inc/HackerNews huggingface dataset:
Do you want to program fast? Then you need to program quickly. Deliberate practice with slowly written / slowly designed code won't make you any faster.

Do you want to program difficult problems? Then you need to solve difficult problems. Writing fast "code jams" won't help you train vs difficult academic, theoretical problems.

Do you want to program Cryptography? Then you need to write correct cryptography code. Practice by writing incorrect / breakable cryptography code (ie: side-channel attacks, timing attacks, etc. etc.) does you no good. You need to actually write the proper cryptocode.

-------

Doing any of these things imperfectly is sadly, less than useful. You end up practicing "bad habits" and making yourself worse as a programmer.

Fortunately, we programmers don't need perfection in most cases. But always remember that while "normal practice" gains a decent level of competence, you don't actually reach the levels of elite skill (in any task, programming included) unless you can execute "perfectly" at least once.

Setting yourself up for perfect execution needs to be a goal in of itself. For students of language, this means practicing the native tongue's accent. For sports, it means practicing the perfect golf swing form, or the perfect strikes in martial arts.

It also means that people of elite skill can "retain" those skills easier than beginners. If you want to practice "10 perfect golf swings", a beginner may have to swing 100 times to do it. But a pro-golfer would execute in just 10 swings (since almost all of their swings are perfect already).
As far back as 2000, our “ops” person wrote Perl scripts using the Win32 module to automate tasks on our 20 windows job servers.

Even in the mid 90s when I worked on backend mainframe systems for lotteries, everything except physically changing out tapes and malfunction hardware was automated.

There has been an API to manage networked servers since networking existed.

The value add of DevOps was suppose to be developers and operations working together. When I develop something. I always do it with a mindset of how will it be deployed, scaled, monitored, etc

If “DevOps” is a role instead of an institutional behavior, you get none of those benefits.

And yes I know “Devops” [sic]. My day job is consulting companies on how to bring modern development and cloud operations, networking, CI/CD, monitoring, aggregate logging, etc together. I work up and down the stack from an empty AWS account to back end development and if you put a big enough gun to my head, I’ll deal a little with the clusterfuck of front end development
If these lawyers wanted to go after the devs the only leg they could possibly stand on under US law would be trademark tarnishment[1].

In any case it could possibly be defended as parody, but only if the fact that the developer didn't use the IKEA name doesn't end the lawsuit sooner - which however would make it a really obvious parody.

[1] 15 U.S.C. § 1125(c) https://www.law.cornell.edu/uscode/text/15/1125#c
I like the colors of Nord, but find the contrast to be way too low for daily usage.
I don't want to stand on any side of the argument since I'm not very informed about KiwiFarm incident, but Wikipedia in general is not really a reliable source of truth.

Skimming the references, almost all of them seem to point to news pages created after the CloudFlare ban, none of which seems to provide sources for their claims themselves.

Obligatory xkcd: https://xkcd.com/978/
Or the library! The GIF spec was published in a magazine IIRC. I wrote a GIF viewer that supported CGA, EGA, VGA, ... displays.
Even though computing resources have grown by leaps and bounds over the past few decades; it seems that the amount of data has grown by even more. I have found that it is much easier to generate twice as much data needed for processing than it is to get the processing of it to run twice as fast.

When you multiply by really big numbers, the problem becomes very apparent. A wasted millisecond in a function doesn't seem like much until you call it a million times.
A third is a “few”?
I heard that astigmatism is the reason some people find reading white-on-black intolerable: the edges shift from their proper places, look doubled, this kind of stuff. Idk if astigmatism-correcting glasses fix the problem, as I'm not that diligent with my prescriptions.

Personally, somehow I'm ok with looking at code and some notes in light-gray-on-black, but reading paragraphs of text is immediately off-putting. The proliferation of ‘dark theme’ sites is not working out for me.
I agree with you. The GP's argument is like saying I mailed a letter addressed to "Crimea, Russia" and the post office delivered it, therefor the US (or NATO as their claim makes a few jumps) recognizes Russia's claim to Crimea.

RIPE doesn't have the authority to make that decision. Just as the friendly person at the post office making sure my letter gets where I meant it to, doesn't either.
It is something you would want though if you are hosting content with audio consumed by people who aren't paying attention to audio quality.
I started my first dev job in early 1997 which is more like 25 than 30 years ago but I think the milieu was similar.

The internet was mostly irrelevant to the line of work I was involved in although it was starting to have impact. We had one ISDN 2x line for the entire office. It was set up to open on demand and time out a few minutes later as it was billed by the minute.

I worked on an OpenGL desktop application for geoscience data visualization running on Irix and Solaris workstations.

The work life balance was great as the hardware limitations prevented any work from home. Once out of the office I was able to go back to my family and my hobbies.

Processes were much lighter with far less security paranoia as cyber attacks weren't a thing. Biggest IT risk was someone installing a virus on a computer from the disk they brought to install Doom shareware.

The small company I worked for did not have the army of product managers, project managers or any similar buffoonery. The geologists told us developers what they needed, we built it and asked if they liked the UI. If they didn't we'd tweak it and run it by them again until they liked it.

In terms of software design, OO and Gang of Four Patterns ruled the day. Everyone had that book on their desks to accompany their copies of Effective C++ and More Effective C++. We took the GoF a little too seriously.

Compensation was worse for me though some of that is a function of my being much more advanced in my career. These days I make about 10x what I made then (not adjusted for inflation). That said, I led a happier life then. Not without anxiety to which I'm very prone but happier.
Well there are a couple of contradictions, though they don't imply that Russia's claim is recognized, just that Ukraine's claim is no longer recognized.

For example, their accounting department is likely accepting money from companies that have no legal basis under Ukrainian law for activities in Crimea. Unless they've waived all fees.
I've done that too, it really sucks. My boss wasn't thrilled about it either but it was a directive from a lot higher up than she was. I took that as cue to look for a new job myself, as did others. Not everyone left but enough such that between the layoffs and the devs/BAs that quit caused a project to slip such that they had to pay "fines" as designated in the contract and a couple senior leaders were let go.
I use nord on basically everything I can these days. Gotta love that ice blue
Mahalo was such a success, I can see why getting put on as a staff engineer makes sense. Calacanis was already a twit long before twitter was around.
> As predicted in the 80s, the result is a country that is poorer and facing increasing social unrest.

There might be greater wealth inequality. And some things might be getting measured better than they ever were, more accurately and truthfully. But today's America is not poorer.
Time to change my Amazon smile recipient!
This is my favorite theme: the colors all look nice and are gentle on the eyes.

However, I find the contrast between background and foreground to be waaaayy too low for my taste. I’ve found that setting the background to #121212 makes everything a lot more readable. I have some screenshots of what this looks like here:

https://lambdaland.org/posts/2022-08-01_a_new_font/

I’m not a graphic designer, but I’ve wanted to extend the color theme a little bit. There are multiple hues of blue, but only one hue of everything else. Does anyone have any good color palette building tools that they like?
Source code control was a known thing.
I had been using PVCS for 6 years by then - and when on Unix RCS.

I got annoyed in the 80s with people who had messed the code base up so we could not compile from a fresh checkout.

Yes communication between people was and still is the most important thing. Note that this usually needs meetings in person
Things that look "good" aren't necessarily ideal for coding. My favorite "bad looking" but very functional theme is the IntelliJ IDEA high contrast theme [0]. Everyone who looks at my screen says it's ugly, but I've yet to find one that is as good for improving readability/

[0]: https://blog.jetbrains.com/wp-content/uploads/2018/10/idea-H...
`sudo /usr/bin/cpuctl` can turn off cores, so for example you can turn off the performance cores.
> Politics still happens outside of democracies.

Nobody is suggesting that a randomly selected legislature shouldn't listen to anyone outside themselves.

The difference is that a randomly selected legislature for fixed single term in office never has to worry about gaining or maintaining power, because they will definitely lose power when their term in office is up.

Whereas both elected politicians and monarchs always have to worry about gaining and maintaining power, the former via elections and the latter via military superiority over rivals. Politicians lose elections, whereas monarchs lose their heads. ;-)
This is 100% true (and different "high performance" machines can operate differently, too).

Some people like to develop on a slower machine (do all their development work on the slow machine) so they catch things, others like to do all the work on the fastest machine they have, and only when nearing completion test things on the slower one. Both have arguments in favor - a decent compromise can be a "build on fast, deploy on slow" where it may be as simple as a shared folder between the two machines with Synergy or even Ventura's built-in equivalent for running the app.
Can you explain? I vaguely recall using it on sparc workstations a couple decades ago, but I wasn't coding for that target. A quick wiki read says it was an API framework that was "endian free" and that it trageted the three architectures that next ran on. Was it doing emulation for software using it? Or was it, itself a single binary? Or both?
No you didn’t. At no point did you attempt to present conflicting numbers.

Instead you sunk to lazy trolling with “is anything true?? question everything!”. Yeah, you can dismiss literally any conversation like that.

You started playing games with meanings of well defined words like “terrorism”. It’s like arguing that the sky being blue is just a matter of opinion, completely pointless.
Serious beta testers for slack alternative with email
Spike for Teams creates a best-in-class team chat platform with the option to add any email account right along side it. Communicate in public channels and private groups while emailing external colleagues and customers just like normal.
I see my background to #121212 and that does the trick for me.
Similar here. Pics for the curious: https://draculatheme.com/visual-studio-code
Has anyone tried one and found it to be unexpectedly dangerous (or safe?)
I agree. The biggest thing I dislike about Tokyo night, though, is the comments are not very well contrasted against the background. Aside from that I like everything else though.
your problem is that you're using PHP
"5.1 Aether properties variations —
Speed of light, electric permittivity and magnetic permeability of vacuum are no longer an universal constant, but are dependent by gravitational potential as show in equation (18,19,20)."

Certainly a provocative comment. I have a bit of a track record for discussing the relationship between c, ε0 and µ0 on HN for the reason that if c^2 = 1/(µ0 ε0) then we have a chicken and egg problem. c is often treated as the fundamental constant but clearly it is related to the physical constants ε0 and µ0 - and its relationship to the constant α. I'm not going to go over what I've posted before about this nor am I going to debate this provocative paper. The only point I would wish to make is that it seems to me that this relationship is probably more important than is generally accepted and needs more attention.
I get the issue with TCP, but I'm not sure about Homa... e.g., why not UDP with some homa-like semantics on top? That might really ease the "Getting there from here" issue.

In fact, what's actually being suggested is for applications to replace calls to TCP-based APIs with calls to gRPC APIs (or other high-level RCP APIs), where the transport layer becomes an implementation detail. Fair enough, but this is a very round-about way to go about it.
>Also, didn't we have airbases in Saudi Arabia and Kuwait?

Yes, I believe Al Jaber Kuwait had already constructed one of the largest post-Vietnam expeditionary airfields* with multiple US squadrons (including F/A-18s) present before the war officially began.

* "Expeditionary Airfields (EAFs) are portable airfields that can be constructed, used, broken down after the completion of a mission and moved to another site for re-use."[1]

[1] http://www.cassholdings.com/AM2.htm
> This largely has to do with 'unknown unknowns'

What has been much, much more worrisome in my practice, is ‘unknown knowns’ which is something developers should know but do not. Poor design and engineering skills, low level of professionalism is what keeps plaguing software industry. (Remarkably, most other industries, those that have to deal with material things, do not suffer from this - not on this scale anyway.)
Depending on how it dies, it's often not worth repairing a $300 laptop - since you can buy another one for $300.

It is often worth selling the dead one for parts to someone else; even if the logic board is dead the screen is likely to be useful.
I was looking at this earlier linked from the thread on Solarized (which is what I've used for years) - I'm looking again now, from laptop instead of phone, and I still can't find any screenshot examples with actual text (not blobs) anywhere?

I just want to see what it looks like. With no demo at all I'll likely forget about it and never try it - perhaps my loss, and I realise it's not like the author's trying to sell it to me, just seems like a real oversight not to show what it looks like in 'real' use vs. swatches.
Firefox has had basic support behind a flag for a good while, but it needs some work -- their code is missing things like transparency and colour profiles. Sadly mozilla have laid off a lot of their dev team and they don't have much capacity right now.

Safari have support as a build-time option, apparently.
Bitcoin isn't going away. More people are putting their trust in it as their monetary standard every day, not less. Bitcoin, the asset and network are neutral. Scams on top of it, shitcoin affinity scams, or whatever "oodles of other great reasons" don't change that. The majority of Bitcoin mining is already renewable, it already incentivises renewables this isn't a hypothetical future.

If somebody proposed a law tomorrow that bans coal plants being reopened to mine Bitcoin I wouldn't be against it, and Bitcoin would carry on happily regardless.

BUt you're then getting into the dangerous territory of telling people what and what isn't an acceptable use of compute power. Bitcoin is a valid and useful consumer of energy.
How to set up SFTP server on Ubuntu(AWS-EC2)
Ah okay, that makes a lot more sense than when I read concurrent as 'together'. Glad you figured yourself out and I can imagine that must be a drag to keep organized at the doc... reform is definitely needed there.
The real question is whether any "filters" are really needed.

Spacetime alone is sufficient to explain the apparent absence of detectable technological civilisations.

There could be a Dyson Swarm in the making right now, but even if it's "just" 100 light years away, we wouldn't be able to notice until 100 years from now. Same with signals. Any alien civilisation monitoring us would need to be closer than 50 or so light years in order to send a message directed at us that we'd be able to detect now (e.g. radio technology ~100 years ago -> 50 years to get that information to "them", and another 50 years until we'd receive a message).
I see a ton of signs saying help wanted in frot of businesses.
Is that what the legislation says? Or are you just guessing that the legislation will be poorly written?

I don't see the consensus by activists in this field as people that are saying "don't use adhesives," "all hardware must be modular," or "compromise design for repairability."

I see right to repair activists asking for things like:

- Making spare parts available to purchase

- Making internal service manuals available with reasonable terms

- Forbidding certain types of digital protection on spare parts and firmware that are in place to enforce a market power imbalance (e.g., to force you to buy OEM spare parts without a defensible safety or security reason)

- Forbidding anti-competitive parts inventory practices that disadvantage independent third party repair providers (e.g., Apple, who makes third-party repair shops wait until a customer brings in a phone before they can order a common part like a screen...imagine if your car mechanic had to wait until you brought your car in before they could buy brakes, you'd always take the car to the official dealer to get it done faster.)

Experienced and even amateur repair technicians have no problems with things like adhesives. Instead, they have problems with companies actively fighting against self-repair.
Agree, after thinking it over, believe it’s very similar to way author Dave Gray describes how people relate with one another in his book Liminal Thinking, which has a brief video on the topic:

https://youtube.com/watch?v=WNAB3V80ZvU

I would go further to even say that frequently people fail to understand the value of sticking to their construction of reality instead of compromising and acknowledging alternative realities, even ones that might in fact be provably false, but in sum produce less negative impact than forcing your reality upon them.

One might even say that’s actually more reasonable than applying rigorous unwavering reasoning to everyone and everything.
Zod gives you a lot more of control on the schema.
To be entirely honest, I think Twitter is serially bad at shipping things and also hired too hard during the pandemic. That said I stand by my earlier point, which is that measuring this via "I see a bunch of people on TikTok drinking lattes" is about the dumbest way to do it, because it's nothing special in this industry. What you really want to look at is "how long is it taking to ship things" and "what does code churn look like" and "what stakeholders are involved in a new product launch", which are generally much harder to see.
You mean the 'bless' keyword? Yeah, that's a bit quirky, but lots of programming language keywords are kinda metaphorical anyway. The heck is a "void"?
I mean, those are clearly cryptocurrency-related projects which fall well within the scope of this policy. The exceptions are not to let the "good" cryptocurrency projects in -- there are no such projects -- but to make sure that projects which are close to this domain get a fair shake, like something which incidentally uses a blockchain-like data structure, GNU Taler, etc.
Don't want to discuss this on my main.

I drank far more than this for almost 15 years. Quit over two years ago and life has never been better. I did decent career-wise prior to quitting, and a bit better afterward. I feel like it didn't affect me too much WRT cognition besides just feeling like shit in general. I was also worried about the neurotoxicity but the brain is pretty elastic in this regard I believe. I'm older than you FWIW.
I had forgotten about PVCS! Thanks for that memory. :-)
Unfortunately, this palette does not pass WCAG[1], which seems a weird thing to not have tested for if you've made a palette intended for web UI.

If you own/manage this project: install the Axe browser extension[2], run it on your site, go "...oh...oh no..." and then unfortunately, take accessibility seriously and get to revising =/

[1] https://www.w3.org/WAI/standards-guidelines/wcag/

[2] https://www.deque.com/axe/browser-extensions/
I feel kind of bad for Perl. I never learned it. I'm no foreigner to "hard" languages. I know Bash, I know Makefiles, I can write a "sed" script with a little effort. Of course I know Python and C and I even put in the effort to learn Rust. But Perl never bubbled up the priority list. We used it a little bit for internal scripts at my previous job, but I rarely had to interact with those, so I never took the time to actually learn it. I'm certain there's a good language in there, but it's so rarely used during my time in the industry (I'm in my mid-30s), that it's just never been worth the effort. I'm sorry, Perl.
I work at medium size school district with 7 building locations and just over 300 employees. I was denied an IPv6 block as I was deemed too small. Continued to be annoyed at the IPv6 rollout. I have 26 static IPv4 addresses that have worked great and continue to do so.
Yeah, arena allocators are a great tool, but they are not a magic bullet either.

Also the author's condescension about automatic memory management is... telling. Remembering to call "free" is only one small part of why tools like RAII are good, and arena allocators do not help with the other parts.

The overall goal is to be able to write correct, reliable, performant software. Arena allocators help prevent missed or double frees, but they don't help with the other memory safety issues. For example, sometimes objects in different arenas need to reference each other and C does not help prevent you from accessing those references after one of the arenas has been freed.

On top of that there are general issues with arena allocators:

1. They can be inefficient for resizable collections where you don't know the total length in advance. The multiple re-allocations results in a lot of wasted space in the arena.

2. In C, it's implicit which objects should belong to which arena.

3. It's not composable. A library doesn't necessarily know which objects should use which arena, or may not even support arena allocation at all.

4. There are other resources than just memory. There's a reason it's called RAII and not MAII - because it allows you to clean up all kinds of resources (eg. file handles) when an arena allocator doesn't typically support any kind of destructor.

5. It requires more thought to structure your program in this way. For some programs that may be effort well spent, but a lot of programs are not bound by allocation performance, and for those programs not thinking about allocation at all leaves more time for thinking about correctness in other aspects.

6. Languages which do automatic memory management can still support arenas, and may offer additional benefits when they do (eg. Rust's explicit lifetimes can tie an object to the arena it came from).

7. The stack and heap are global resources that most code can simply assume exist, and use with no extra ceremony. When you have arenas in play, these need to be passed as additional arguments. Adding a new allocation to a function can require sweeping changes to add a new arena parameter to every function above it in the call stack.
VBAndCs/SVB-Small-Visual-Basic: A Tiny Dynamic Version of VB6
At that point you don't need stasis technology, just put your artificial brain in a robot and send it off at speed with an insert atmosphere.