skysight-inc/HackerNews huggingface dataset:
The Bad Code advice is for people who have the tendency for perfectionism (apparently like the author 15y ago).

My advice to me: write simple, dumb, repetitive code, but make an effort to be consistent.

Consistent, dumb code is really easy to visually parse. The repetitions slide into the background and the differences stick out. The more code there is, the easier to see what goes together (data aggregates/structures), what the overall flow should be (control, conditionals, order etc.). Then it's easier to factor things out or how to express more clearly what the code does.

But again, consistency is key. The code can be "bad", but it's very beneficial to do simple edits like renaming and reordering of things, grouping them under succinct comments so the structure stays clear.

Younger me would do the opposite: inconsistent code that is complex. I think its impatience that gets in the way, rushing to build abstractions and factoring out things way too early or trying out competing ways to express the same kinds of things (playing around with code).

Every programmer has their own tendencies and their own journey, so they need to hear different advice, in order to ignore it for now, but to have an AHA moment at some point when they realize why the advice was given.
If the interpretation of the law is too vague the court determines its unenforceable then congress has to make a better law. It doesn't shift the power to the courts.
It always depends on the team. And by team, I mean the people working on a somewhat independent part of the project (they don’t need to care about the minutia of some other parts). Issue tracking is a tool, but project managers always wants the tool to become the process. And that’s when you got daily standups, story points, epics, and fixed sprints (aka fake deadlines).

Use the tool as a tool. As the devs, add issue and tasks that needs the attention of the team, comments on a ticket for knowledge retention. As the manager, schedule the ticket if its completion matters in a particular timeframe, use assignments and other fields to manage workload. Do all of these to help the team get things done. Anything else is a hindrance.
OpenAI/Microsoft are building a business around stuff they got for free. That is the whole point of the above comment.
Reduced physical activity in old age will accelerate sarcopenia. If you're hospitalized, especially for long period of time, that will also accelerate muscle loss.
Study Finds Today's Adolescents Are More Satisfied with Being Single
The UI is built using Imgui (hence the Im prefix) which is a Ui framework for computer graphics programs.

Though, a couple nits:

1. An OpenGL requirement doesn’t necessitate a GPU. There are software implementations of OpenGL but they tend to be rather mediocre at best for performance.

2. Many platforms now assume some kind of GPU. It’s fairly rare to need a GUI tool without also having a GPU available. Of course there are niches for it, but those aren’t also likely to be running a hex editor and tooling locally.
saying "download from fdroid" and pointing to your private repo is the shittiest thing anyone can do.

it's the same as linking to your .exe or .img and saying "get it from microsoft/apple". no it's not. you are just using those platforms ability to handle links and extension of functionality.

it is in no way the validation from those platforms that wording like they do imply
Seems like some good advice here! The points about digging deeper into the cause of a bug and looking at the history of the codebase for more info are really good points to keep in mind for sure.

And remembering to ask questions hits home pretty well too. There's always the worry that you're bothering people too much, and the balancing act between thinking whether you need to be asking for help early enough to make sure you're not going down the wrong path and not asking about every little thing without attempting to fix it yourself...
At a previous job in IT we got ~200 Dell Latitude 5440 laptops, several of them gave us bluescreens during setup or during normal (Office 365 and web browsing) use, other laptops (ThinkPads and low to mid-range Acers) and desktops (HP) used by the same users and set up in the same way had none of these issues

So some laptops defintely get random bluescreens more than others, I wouldn't blame the user as a first option, although it is possible the user is at fault
"Developerocracy" – A New Challenge for Scandinavia?
Over the past decade, I've observed a shift in many Scandinavian companies towards what I would call a "developerocracy." This represents a considerable departure from earlier times, where business needs drove most decisions. Today, developers often prioritize their personal interests over the business's desires.

This trend manifests in several ways:

1. Resistance to Business Requests:
Developers often resist implementing features or solutions that don’t align with their personal interests or preferences. These requests get pushed to the bottom of the backlog. If the business insists, developers cite vague issues such as "incorrect requirements" or other questionable reasons. Tasks that diverge from their favorite tools or frameworks, or lack supporting tutorials, tend to be deprioritized further.

2. Inefficient Development Practices:
The cost of developing features seems irrelevant to many developers. They frequently introduce unnecessary layers of abstraction, resulting in buggy, slow, and inflexible solutions.

3. Obstruction of External Solutions:
When businesses seek to resolve issues by purchasing external products, developers often present a laundry list of reasons why these solutions are unfeasible. These objections are usually weak or fabricated, stemming from a perceived threat to their control. As a result, even if the Head of IT wishes to implement a solution, it gets stalled by developers who refuse to cooperate and face no repercussions for their obstruction.

I believe the following factors contribute to this situation:

1. A prolonged economic boom
2. Excessive job security
3. Diminished average competency as more individuals enter the field

What are your thoughts and experiences on this? Have you observed similar trends in your own environment?
I'm finding it hard to believe that BlackRock doesn't understand Goodhart's Law. Surely they wouldn't be where they are without being able to rationally optimize for the objective of profit.

Presuming competence, it seems that one of the following must be true: either (1) external coercion plausibly threatened profits enough that a more controlled sacrifice of profit (call it a tribute or blood money) was objectively preferable, or (2) profit is no longer the objective.

One doesn't have to presume competence, but I don't know enough about BlackRock's leadership structure to meaningfully comment on that.
really depends on the scale of your platform, data & transaction volume - such ACID distributed dbs would be handy for big fintech corporations. In my case, I just need a simple managed postgres for my launch platform (https://microlaunch.net), it's still transactional, but the platform isn't write intensive
Count me in. There's apartments all around my nearest Costco but I'd prefer to live above it.
Not to be confused with Rule 34, unless there’s a Rule 34 for Rule 30.
I like to use a metaphor.

You're at a party. You politely say goodbye to everyone and start heading for the exit.

You are restrained and drugged.

Nice party, bro...
On that note, you can just do it for the good of the world. A lot of us have high-paying day jobs that can support us and good writing can be done on the side.

Benefits include not needing to hit some page count (so you can be concise), and bug reports from the community.

I don't look down at people who make money from books at all. I admire all writers and editors. (Some publishers can go f themselves, though. :)

But there is another path available to many of us, one that isn't driven by money. Remember the old hacker ethic!
I’m on the fence. When I obsessed more about Flow State, I really did see dividends from spending spare cycles reading the docs (especially release notes) and keyboard shortcut mappings to find faster ways to do things I did often.

Maybe I hit the point of diminishing returns. Maybe it’s because I don’t Code Like Hell much anymore, but it’s a habit I got out of. I keep resolving to getting back to it, but the fact I don’t maybe telling me something. Like maybe I’ve filled that spare time with other things that are more valuable.
https://www.sciencealert.com/study-more-patients-could-survi...

> Yet families are often asked to make the call within 72 hours of someone sustaining a severe brain injury. Unless patients make a rapid recovery in the first few days, it's thought they are unlikely to survive or recover much at all.

> The data Sanders and colleagues analyzed tentatively suggest otherwise.

> The data revealed that 31 of the 56 brain trauma patients who stayed on life support died within six months; and 45 percent survived. Of the 25 patients who survived, more than 30 percent recovered enough in that same six-month period to have at least some independence in daily activities.

> Just four patients recovered 'fully' to how they functioned before their injury.
True, but most stuff I bought from gumroad, url never expires. Guess, we tech folks are conditioned to think too much into basics that non-tech folks don’t think about.
I can see that. I find it telling to have found an example out there. Hadn't seen one so far ...
No, it's a coding error that lead to a wacky subsample being used for their treatment variable.

The blog post list this as the original Stata code:

> replace event`i’ = 1 if delta_mct`i’ != 0 | spouse_delta_mct`i’ != 0

and this as the correct one:

> replace event`i’ = 1 if (delta_mct`i’ != 0 | spouse_delta_mct`i’ != 0) & delta_mct`i’ != . & spouse_delta_mct`i’ != .

It looks like the authors didn't properly handle missing values in Stata, leading to marking people with missing health information being marked as being "severely ill" instead of being excluded from the analysis.

It's an unfortunate mistake, but it happens.
How does precedent about how commercial is interpeted here apply? If I use this to fire off a work email, is that commercial? Or does this only apply if I'm selling a product built around this?
Someone I know acquired potassium cyanide for this reason. She's getting up there in age and wanted some insurance against a horrible death.
It's an error they were happy to run with because it gave them a punchy conclusion and widespread publicity.
Yeah, I wasn't "swapping" PSU cables; the cable was part of the PSU. I replaced a Dell PSU with a standard one, and <smoke!> No more motherboard.

Manufacturers who pull this type of incompatibility shit risk their reputation. I never went near anything with a Dell label again until last year, when I bought a second-hand laptop (I don't attempt laptop upgrades and repairs).
Of course this can vary wildly, but I've never felt afraid to defy management on that one. Half the time, they don't even need to know. And the other half of the time... what are they going to do? Fire me? Fine, then their project will be filled with nothing but wallpaper-patchers and I'll be somewhere else doing good work.

(And of course, sometimes just patching the wallpaper is the right course of action, but it's rare to find management capable of accurately assessing this trade-off.)
If nobody pays they won't introduce ads; they'll more likely just go out of business.
Part of being senior is figuring out how to work in those constraints. In that situation I would push back my manager and tell them why root causing bugs will save us time in the long run and if they still don’t relent I would sandbag some of my time doing sprint tasks to root cause the bugs.
It might not be applicable for you, but just in case -- take a look at myofascial release, similar to trigger point therapy. Basically foam rolling on your legs, using a lacrosse ball and progressively smaller rubber balls across your back and shoulders and pecs, and a TheraCane on shoulders, neck, sides, etc. Also Alexander Technique lessons, which retrains you to use your muscles without the tension habits you've accumulated over your lifetime.

The two of them together have changed my life. A lot of acute injuries of mine had healed, but had left my muscles extremely tight and essentially kind of frozen, which then creates problems with movement and posture and which then generates other kinds of pain. I too thought I'd never get back to "normal", and then was shocked to discover that I basically could, after a couple of years of undoing all the muscular tightness and "frozenness" through myofascial release and Alexander Technique. (Basically, the myofascial release gets rid of it, while Alexander teaches you how to prevent immediately re-forming it.)

It's funny that myofascial release is only just starting to gain awareness among the medical community, while Alexander Technique still mainly only has awareness in the acting and musical performance communities.
The dirtiest fuel is a disturbingly safe investment
https://archive.ph/ZNMcc
Typing fast is an interesting metric.

Shipping the same code will happen sooner if you have tooling and typing setup to allow for quick iterations, and being quick in making those iterations. Selecting a language/framework that might take more work can slow you down too.

Typing faster does seem to look towards thinking faster, trouble shooting faster.

One place where it can get someone into trouble is typing too fast, faster than it might take to think through and not over look something which might invalidate what you're doing.

I have all hires do typeracer.com. Not for a high or a low score, but seeing the development of the score and understanding the importance of typing fast relating to thinking fast.

Typing code inherently is slower than writing sentences, so if you can type faster sentences in written communication, typing code will be faster, even if it's not at the full typing speed.
Why are we so afraid of code as a commodity?
> Tax gaps are currently estimated at 39.8 billions [2].

And guess what the Tories chose to do instead of increasing taxes on the richer cohort of the population? Cut budgets for welfare programs, increasing poverty, making society less productive: more sick, less educated, individuals in poverty stay in poverty for longer further reducing economic output and straining public services, staying in poverty longer also mean a smaller tax contribution, so on and so forth.
Would it need more than https://en.wikipedia.org/wiki/Shinkansen ?
That it's not even close to FOSS, and that you're not allowed to make it stop harassing you for money.
Their job is to make laws.

It is not possible except in some simple cases to make those laws completely specify every detail and cover every case when dealing with large complex topics, so there will almost always be cases where those executing the law will need to have some gaps filled in order to carry the law.

That was true long before Chevron, true during Chevron, and is still true.
One more: Make developer velocity one of your top priorities.

You should be able to give anyone in your team the repo URL and have them running unit and local integration tests in five minutes without prior knowledge.
> It's a race between turning into venus and turning into mad max's thunderdome.

It is hard to tell how serious you are in that comment, but just in case, worrying about runaway greenhouse gas effect turning Earth into another Venus is climate hysteria.

Poorly thought out energy policies due to climate hysteria have a good chance at creating considerable political unrest though (not sure about "thunderdome" level of unrest).

Turns out when you restrict access to energy (e.g., by increasing its cost), people get upset.
Congress did their job. They granted authority to regulatory agencies who are much better equipped to make these sorts of decisions. Regulatory agencies employ scientists and subject matter experts in their relevant fields.

Our congresspeople are a mixture of serious people and clowns who are very good at saying outrageous things to get on television. Even the serious people cannot possibly be well-rounded enough to have the kind of expertise necessary to write perfectly detailed regulations for every possible field.

Could I come up with some regulations related to tech? Sure. But it would be a terrible idea to ask me to write financial, medical, or environmental regulations.

Like I said, Congress did their jobs. Sometimes delegating to experts is the smartest move.
My reading of the license is that if you use it to type any text for work, you're in violation.
For sounds like the right word not from.
I think you both provide some kind of generational advice, like parent serving kid with life advice. Unfortunatelly, or fortunatelly, they will have to learn it by experiencing own failures first.
>I can make better food faster with better ingredients for a cheaper price at my own house for my own family, as long as we did some thi king ahead and planning. On top of that, when I make a new recipe, I learn how to make something new with new ingredients that helps me do more exotic dishes in the future.

Can you? Are you accounting for your labor cost?

I do a lot of cooking for my family too, but when I account for the time it takes to shop for groceries, prep, cook, and clean up, I doubt I'm making even half of what I make in my job. It would be more economically efficient for me to cook only very simple things, work more hours, and have more food delivered.

There are a lot of reasons I don't do that! I agree with all your points about self-sufficiency, and health, and personal development. But I disagree that those are "efficient". Efficient is labor specialization: I spend more time writing code and hire someone to do the cooking and cleaning and transporting.
Maybe create an issue saying as much?

https://github.com/WerWolv/ImHex/issues
That may be true — it may be the only Haskell program that people regularly use — but I'm not sure how that counts against Haskell. I'm no fan of Haskell (I used to be a huge pure functional programming fan, but over time the shine has worn off and I've realized it's just another dogmatic paradigm) but having even one widely used and liked tool is actually exemplary for a highly idiosyncratic non-mainstream language like Haskell, to be honest. I think it's doing pretty well for itself.
> What we find in the corrected analysis is we still see evidence that when wives become sick marriages are at an elevated risk of divorce, whereas we don’t see any relationship between divorce and husbands’ illness. We see this in a very specific case, which is in the onset of heart problems. So basically its a more nuanced finding. The finding is not quite as strong.

I take issue with this framing. Starting with saying that when women get sick, risk of divorce elevates, immediately followed by saying this happens only in one type of sickness is still very misleading. The entire first sentence is misrepresenting the actual findings.
A hobby project does not necessarily have to be needed or valuable to everyone. The learning experience of the author is much more valuable.
I'd definitely agree that reading others' code can be a good way of learning, especially if you take the time to disassemble it line by line and look up things like what language features and functions they're using, how it's structured, etc.
Embedded systems or tack-on? This seems like the internal accelerometer would be adequate?
I usually say "No, death is not the solution, death just removes the problem.".
I don't think I'd have the stomach to spend a year writing something that I think is really good only for it to end up on libgen a couple days later.
I managed to get around it with litespeed Cache which does cache 404 pages. I was previously using WP Super Cache which does not. Note I also wasn’t running a CDN so there’s no reverse proxy cache either.

Over time, I found that BetterLinks was slowing down my site significantly (600ms) . It wasn’t like this when I first investigated. It became slow over the course of a year or so. I ended up replacing it with Simple 301 Redirects. I think this is a separate issue though, unrelated to my original overload, but looked very similar to when Firefox DOSed my site.

I experimented with CDNs to cache things reverse proxy style as a catch all. Eventually I caved and enabled Cloudflare CDN because QUIC.cloud kept having problems where a POP node kept hitting 403 Forbidden. I’d say the site is pretty functionally performant now.

I think most sites that claim Wordpress handles high loads really well have at least two layers of caching in front of it and are running on dedicated boxes. Remove both of those and suddenly it’s super easy to DOS.

Another common DOS exploit is to repeatedly spam the Forgot Password form, since there’s a lot of guaranteed processing with that and it’s not cacheable. I hid mine behind a captcha which helps a lot.
“Once is happenstance. Twice is coincidence. Three times is enemy action”
― Ian Fleming, Goldfinger

P-hacking is so endemic and so essential to modern academia, especially in the 'softer' sciences, that the whole thing is beyond saving. It's so bad that anyone who understands statistics well enough to know that most of their peers works are bogus are much more likely to be shunned than embraced because of this knowledge which is an incredible disincentive to acquiring it.

Edit: as I can’t reply to the now dead account, the first quote explains why academia cannot keep claiming innocence on such matters. The rest of my comment was my explanation as to why nothing is being done about it. Sure, we can ask them to do better but they should already know that.
If the Hysatas electrolyzer[1] is for real and scales up, making hydrogen is going to get way more efficient. They can make then make synfuels out of hydrogen for about a 40% loss. Eventually, they could put these electrolyzers at major airports and refuel hydrogen planes without having to move the hydrogen much. That's the big weakness of hydrogen is that it can't be moved around easily in pipelines. It can be stored in underground caverns under low pressure for cheap though.

[1]https://hysata.com/news/hysatas-electrolyser-breaks-efficien...
I built a home server and can just add drives as needed. Right now I have something like 90TB available, with 30 of that free. Every year I probably add another drive. Soon I’ll have to get a disk shelf for further expansion, but that’s part of the hobby!
If you run for fun, and you have the cash, go ahead and buy the shoes and see if it makes you any faster.

Why not? You only live once. Might as well try all the things you can try and do all the things you can do. Who knows? Maybe the psychological impact of having supershoes will make you a faster, better runner.
i think it was being married to an idiot that was the actual cause of the divorce.
I haven't used mathematica but look forward to learning it one day as an indulgence. I code mostly in R, and it's renowned for having some hurdles to jump through in order to get a package published on its primary repository (CRAN), but what that high standard means is you can download almost any library and expect to find extremely well documented functions with examples that can be run with minimal (usually zero) additional data/dependencies. It's a real treat, and I miss it massively when using languages with less rigorous and less uniform approaches to documentation.
Depends on your referential. Within humanity, addiction takes very different form. Compared to mosquitos, our addictions are probably still very similar, yes.

I think I fail to see your point though.

Are you saying people tend to exaggerate how different addictions are, for example to better sell some new addiction overcoming books or courses?