Recent submissions

Comment · 9 months ago
Comment · 10 months ago
Comment · 2 years ago
Comment · 2 years ago
TIL: Spanish has a sort of written contractions. I speak conversational Spanish so I’ve heard people talk this way, like Puerto Rico or Dominican Republic speakers shortening things, just hadn’t seen it written before. tó = todo ná = nada

https://www.spanishdict.com/guide/shortening-of-words > There are a few apocopes of very common words that are pronounced and written in informal Spanish as monosyllabic words. These popular apocopes include na, pa, and to, that stand for nada (nothing), para (for), and todo (all). You may find these words written with an apostrophe at the end, but spelling experts advise against it.

Comment · 3 years ago
Worked at AOL tech support back in the day and I also still have the occasional flashback to the pain these so called modems caused us all.
Comment · 3 years ago
I have this exact problem and (mostly) fixed it by swapping the sensor and transmitter. I just cut the wires and spliced with electrical tape. Now the problem still happens but only sometimes in the fall and spring when the sun's angle is just right. This is with a west facing garage about 41°N latitude USA.

But yeah, why this isn't laser based, or using a light frequency that is less affected by sunlight? Probably cost, or ignorance.

Comment · 4 years ago
why aren't these fines percent of revenue, or a multiple of the number of people affected?
Comment · 4 years ago
You can't "catch up" on sleep. The only way to get enough sleep is to have a schedule that you stick to.

It's ok to think about work off hours. Write down your thoughts, do some meditation practice to learn to let the work thoughts flow by and notice them, but let them go.

Comment · 4 years ago
One place I worked, the rule was "always have two pairs of eyes on code". Each team got to decide whether that rule was met with some mix of mob or pair programming, or just code reviews/pull requests. We could change depending on the needs of the project and team members. If management forces any of these options on teams it is a huge mistake. The point of pair programming is to share knowledge, reduce bugs, etc. and making it into a metric to measure teams by doesn't work.

It's a lot like setting a minimum code coverage rule like 80 or 90%, people end up cursing the rule as it makes them do stupid things to satisfy the rule. Code coverage is one great tool to explore where your code needs more tests, but it's not the only one, and it's not the point. The point is writing code that's easily maintained, safely changed, and can be delivered to meet customer needs.

You hired really smart people (hopefully) and you should let them decide how to work.

Comment · 5 years ago
Comment · 5 years ago
Comment · 5 years ago
Why don't excel and all the things that can read excel kill the old xls (2^16 limit) format? I mean still let excel read the file, but don't allow changing the file. Only allow saving the old file to the new format.
Comment · 5 years ago
Adding on to the thoughts about everyone writing terrible code sometimes, there is also “terrible code makes lots of money”.

Source: over 20 years doing software dev at various companies with terrible code that makes millions. Happily my current job has really great code (imho).

Comment · 5 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton