hcarvalhoalves

E. Musk son’s name will be fun. Hyphen, number and uncommon unicode character.

This is a Turing test, not a comparative of efficacy.

> I also think that now that LLMs are on the rage, how much context do you think they have for bespoke config language vs Scala vs Python? I think we know the answer to that one.

Nothing against Python, but of all the reasons to choose a technology, whatever is more represented on the dataset of some LLM is the worst reason.

This is a death spiral. There's no hope for the future of this industry if newcomers are thinking like this.

Sorry, but if you're suggesting any AC control different than simple knobs [1], you're failing miserably.

This [1] type of control doesn't require taking eyes out the road to adjust temp, fan speed and fan direction. Since it's a simple fscking knob, it can be adjusted by feel alone, and both the clicks and the angle give feedback on what setting it is.

The suggested solution is bad, for these reasons:

It tries to be clever by providing the lost "clickness" with haptic feedback, but it still misses the most important feedback, which is the angle of the knob. So it still requires you take eyes out of the road to see the setting you're in.

It also commits one of the cardinal sins of good UI, which is being a modal control. So, again, you need to take eyes out of the road and keep clicking to put in the right setting.

[1] https://i0.wp.com/weberbrothersauto.s3.amazonaws.com/2022/12...

Also 5400rpm HDDs were common – that would be 1,5x factor.

That's hilarious. A comedy script couldn't beat real life in 2025.

You people really managed to sprinkle JS everywhere, even on PDF. Shame on you.

My dog used to get really worked up and bite me when she wanted something, so I started teaching to answer my questions. So, when she wants something, she sits in front of me and I start asking: What do you want? Food? <pause> Water? <pause> Poop? When I reach the word, she bumps on me with the front paws.

I guess this is the equivalent of the soundboard.

That’s hilarious. It could be straight out of the “Idiocracy” movie script.

To be fair, you have to compare credit portfolios by product and customer size. That is how the Central Bank reports and tracks these numbers.

Nubank offers consumer credit (credit card, personal loans), but you're comparing portfolios that include mortgages, large companies, industry, agriculture, etc.

Similarly, the default rate of the entire portfolio varies according to the product mix, so you can't compare that way.

You can always "redact" previous data. You can treat the sensible entries themselves as mutable, without it breaking the system design around immutable data.

I have also seen a scheme where you store the hash, and have a separate lookup table for sensible data, that you can redact more easily without messing with the log.

You can simplify things significantly if you can maintain a 1:1 mapping of log entry to transaction (in the business sense). This way you advance the state of your system in discrete steps by advancing in the log, and can make rewind easier too.

In a double-entry ledger the order of transactions doesn't matter, the balance is the sum of entries.

Depending on the data model of your log, if calculating the current state is a commutative operation, I think it's fair to call it a "ledger".

I believe "ledger" implies commutative property (order does not matter).

I believe you want "one log" in the logical sense. In theory, you could have "one log" per user or group of users, or whatever sharding technique makes sense for multi tenancy model. It can also be "one log" per bounded context - e.g. the entire payment pipeline in one log.

The best programmers eventually become experts in a problem domain they’ve worked on, because to teach a computer to automate a process well requires thinking like an expert and resolving incoherences. Weak programmers complain stakeholders don’t know what they want or that there’s no spec; I have a hunch these are going to be replaced by AI.

My favorites are PT Mono (Mac native), Commit Mono and GNU Unifont (works well on smaller screens).

I guess this varies largely with project, stakeholder, etc. The kinds of projects I have been involved, showing a PR would’ve been either useless to communicate anything, or have to explain why it’s “throw away” and why we can’t ship the prototype.

That’s why I stressed it’s an opinion piece but no data. Unfortunately in this industry we have a lot of experience reports, but lack actual data on what is or isn’t more effective way to work.

Another opinion piece, but no data, not even a concrete example.

I get it, every software engineer has strong opinions, but that’s a weak one. If you think writing a lot of code to see what sticks is the job description, you’ll be replaced by GPT in no time - it can do it faster and cheaper. The challenge is always in getting alignment on what should be built, you won’t code your way out of that.

My issue with this kind of piece: a lot of words like "sometimes", "often", "really", "exact", and zero data.

You seem to believe plastic containers are used due to being a more affordable and technically superior solution. That’s a common mistake.

The true reason it’s so cheap and available, is subsidies. $7 trillion as of 2023, to be exact.

Without subsidies, using a non-renewable, expensive to harvest resource, to produce single-use plastic would be an absolutely irrational decision.

https://www.imf.org/en/Blogs/Articles/2023/08/24/fossil-fuel...

Check this out

https://www.archdaily.com/1006779/timber-skyscrapers-a-low-c...

I’m probably alone in this, but I dislike naming tables in plural.

IMO, reading “SELECT employee.first_name” makes much more sense than “SELECT staff.first_name”.

A garden actually isn't that great, it has limited CO2 storage capacity once it's in balance.

Productive land, specially timber, is a good way of capturing CO2, because it will end up stored in products.

We tend to naively think we should reforest land and leave it there, and it can be good for other reasons, but is a poor strategy for carbon capture. We need to _aggressively_ go back to using timber and vegetable fibers as construction material, instead of concrete and steel that have an enormous carbon footprint.

It shows the main focus is not the technology, but the fact spreadsheets are important and deserve a robust open source alternative.

It may be now a sign of wealth in a specific geographic and demographic strata. Having an orchard or at least growing herbs is a worldwide practice.

I'm from South America, and my grandma's house had: mango, peach, lime, orange, grapevine, berries, coconut, jaboticaba, pitanga, acerola, atemoia (native fruits), and many types of spices (including a bay laurel tree). All that in a lot that barely parked 3 cars.

That's the whole point of double-entry. You don't split the entries.

Lawns are an upper-class, 18th century invention, because of course growing food on land is for peasants. The larger the lawn, the more expensive the maintenance, so a well kept lawn was a display of status.

Then, 19th century middle-class, in an attempt to look wealthier and having no personality whatsoever, replicated the trend on their tiny lots, even though they owned much less land, and keeping a lawn is a financial burden.

Nowadays, there's so much profit in this space (equipment, herbicides, etc) that there's an immense marketing budget to keep the status quo.

That's why it's important to learn your history. Good to see this trend reversing.

It should be an atomic transaction, double-entry style, so it can’t fail between commas.

The important thing is not having money go missing.

I've worked with a codebase in the past that would handle this transparently with some sort of middleware for consumer/producer.