This is a classic piece, and I love the contradictions in the text. It encapsulates my feelings on good software and code that it almost becomes an art than a science.

PSA for Debian Testing users: read the wiki

https://wiki.debian.org/DebianTesting

Control-F security returns 18 results. This is well known and there’s even instructions on how to get faster updates in testing if you want.

So cool!! Mercury is definitely the most mysterious inner planet due to its difficulty to get a space probe there even though it’s the closest planet.

The spacecraft will arrive next year, and I can’t wait for all the Science it will uncover!

TIL this exists

I also like the POSIX “seconds since 1970” standard, but I feel that should only be used in RAM when performing operations (time differences in timers etc.). It irks me when it’s used for serialising to text/JSON/XML/CSV.

I’ve seen bugs where programmers tried to represent date in epoch time in seconds or milliseconds in json. So something like “pay date” would be presented by a timestamp, and would get off-by-one errors because whatever time library the programmer was using would do time zone conversions on a timestamp then truncate the date portion.

If the programmer used ISO 8601 style formatting, I don’t think they would have included the timepart and the bug could have been avoided.

Use dates when you need dates and timestamps when you need timestamps!

Do you use it? When?

Parquet is really used for big data batch data processing. It’s columnar-based file format and is optimized for large, aggregation queries. It’s non-human readable so you need a library like apache arrow to read/write to it.

I would use parquet in the following circumstances (or combination of circumstances):

• The data is very large
• I’m integrating this into an analytical query engine (Presto, etc.)
• I’m transporting data that needs to land in an analytical data warehouse (Snowflake, BigQuery, etc.)
• Consumed by data scientists, machine learning engineers, or other data engineers

Since the data is columnar-based, doing queries like select sum(sales) from revenue is much cheaper and faster if the underlying data is in parquet than csv.

The big advantage of csv is that it’s more portable. csv as a data file format has been around forever, so it is used in a lot of places where parquet can’t be used.

The autocomplete is nice but I don’t find it a game-changer. The comment about writing tests is on point though, but that’s the only place I found out useful.

Password managers support passkeys.

If you are being intentional about its use, then you can get a lot out of it. But for some, maybe even most, YouTube is a distraction.

I disagree. I think the default option should be what users expect, and users expect “copy” to do exactly that: copy without modifying the text.

Just because you can get part of your education remotely or through self-learning didn’t mean “anything can be learned online”.

And if you were hiring a math tutor for your kid, would you prefer a self-proclaimed expert from watching YouTube videos or would you want someone who got a degree from a credentialed university? And even if you don’t care, why are you surprised that others would be skeptical of the YouTube expert?

Remote learning can be fine for some things, and self learning through informal channels are also fine, but it’s not a full on replacement for formal education in all cases.

No sorry, that’s just fundamentally false. You can’t just learn titration techniques from watching a video. You can’t learn phlebotomy without an instructor watching you do it to a patient. Hell, you aren’t learning how to drive a car from playing a video game.

And I’m not sure where you are pulling the “if you are that powerful” from. You really have an ax to grind don’t you.

Ah yes, I’m sure the formal training received by doctors, nurses, lawyers, teachers, and engineers is just an over-hyped “education” that can all be replaced by online MOOCs.

There are real problems with education, especially with the costs, but “anything can be learned online” is the worst take I’ve heard in a long while.

I feel the opposite. We should have mandatory voting for all federal general elections. Treat it like jury duty or taxes - voting is a civic duty. You should be compelled to cast a ballot even if you leave it blank because you have no preference.

Of course, this can only workwith automatic voter registration and 100% mail-in ballots.

Yes but karma makes it worse. It incentivizes getting getting upvotes because you don’t want to “ruin” your karma. Expressing controversial opinions, even if they don’t generate downvotes, are discouraged with karma. Even OP says he gets a dopamine hit by seeing the karma number go up.

I don’t like karma. It incentivizes short, meme-y posts since those are things that get gets a lot of karma.

Yeah that’s a good point. It’s telling that inheritance is by design difficult to change unless you follow very specific rules of good OO design patterns.

I guess it’s easy to write bad code in any programming paradkgm but inheritance makes it easy to screw up.

Most of us have bad memories of over-complex hierarchies we regret seeing, but this is probably due to the dominance of OOP in recent decades.

This sentence here is why inheritance gets a bad reputation, rightly or wrongly. Inheritance sounds intuitive when you’re inheriting Vehicle in your Bicycle class, but it falls apart when dealing with more abstract ideas. Thus, it’s not immediately clear when and why you should use inheritance, and it soon becomes a tangled mess.

Thus, OO programs can easily fall into a trap of organizing code into false hierarchies. And those hierarchies may not make sense from developer to developer who is reading the code.

I’m not a fan of OO programming, but I do think it can occasionally be a useful tool.

If the work I’m doing is on a feature branch on remote or locally, why does it matter to the rest of the team? My integration steps can be done on a server instead of locally. TBD forces teams to collaborate synchronously since changes are pushed straight to trunk. Rebase or squashes are irrelevant here.

Another poster put it great: TBD is trying to solve a culture problem. Feature branches and pull requests into main is much more flexible. The only time TBD make sense is for small teams - like 2 or maybe 3. And even at 2, I’d much rather create feature branches that merge into main.

Precisely. In practice, trunk based development just means your branch is local instead of on remote.