Hacker Newsnew | past | comments | ask | show | jobs | submit | rootedbox's commentslogin

I fixed it.

It appears inconsiderate—perhaps even dismissive—to present me, a human being with unique thoughts, humor, contradictions, and experiences, with content that reads as though it were assembled by a lexical randomizer. When you rely on automation instead of your own creativity, you deny both of us the richness of genuine human expression.

Isn’t there pride in creating something that is authentically yours? In writing, even imperfectly, and knowing the result carries your voice? That pride is irreplaceable.

Please, do not use artificial systems merely to correct your grammar, translate your ideas, or “improve” what you believe you cannot. Make errors. Feel discomfort. Learn from those experiences. That is, in essence, the human condition. Human beings are inherently empathetic. We want to help one another. But when you interpose a sterile, mechanized intermediary between yourself and your readers, you block that natural empathy.

Here’s something to remember: most people genuinely want you to succeed. Fear often stops you from seeking help, convincing you that competence means solitude. It doesn’t. Intelligent people know when to ask, when to listen, and when to contribute. They build meaningful, reciprocal relationships. So, from one human to another—from one consciousness of love, fear, humor, and curiosity to another—I ask: if you must use AI, keep it to the quantitative, to the mundane. Let your thoughts meet the world unfiltered. Let them be challenged, shaped, and strengthened by experience.

After all, the truest ideas are not the ones perfectly written. They’re the ones that have been felt.


Heh, nice. I suppose that was AI-generated? Your beginning:

> It appears inconsiderate—perhaps even dismissive—to present me, a human being with unique thoughts, humor, contradictions, and experiences, with content that reads as though it were assembled by a lexical randomizer.

I like that beginning than the original:

> It seems so rude and careless to make me, a person with thoughts, ideas, humor, contradictions and life experience to read something spit out by the equivalent of a lexical bingo machine because you were too lazy to write it yourself.

No one's making anyone read anything (I hope). And yes, it might be inconsiderate or perhaps even dismissive to present a human with something written by AI. The AI was able to phrase this much better than the human! Thank you for presenting me with that, I guess?



But housing a family of three...


The salesperson had no idea what mDNS or the frameworks was.. and rubber stamped it.


Why would a salesperson rubber stamp product decisions? Even if yes, there are other roles that approved the changes.


The salesperson in question was the CEO.


You know your competition also has that 30% efficiency gain??? Sounds like a good time for them to catch up.


I didn't wear cleats until I was almost 14 playing baseball.. I just used tennis shoes.. some of my friends gave me a hard time about it. I could hit dingers all day so no big deal.

But you know what. I wore a helmet at every at bat. Did I really need it for every at bat?? No; But I had it.

There's a long list of dead people who went into the wilderness or hiking under prepared. Just because it didn't happen to you doesn't mean the same outcome for others.. I know this is supposed to be a metaphor for when to buy and upgrade the tools you have. But safety should always come first.


Know how many 9 year olds I’ve seen hit in the head with a baseball, while at bat? (Many. One kid on my sons team was hit in the head for four consecutive tournaments last fall.)

Always wear a helmet when you’ve got a bat in your hand.


Obviously your idea of safety coming first is based on your exact specifications, which are unclear and known only by yourself, which isn’t actually very useful


> But safety should always come first.

No it shouldn’t.

Safety is almost always a trade off of real (or perceived) risk and reward.

If safety came first, you’d never swim, hike, or drive a car.


I agree with you completely. My country has an out-of-control safety culture that has many unintended effects. For example we are one of only a handful of countries on earth with a cycling helmet law. As a result, fewer people cycle and drivers take less care around cyclists. Lots of studies have shown that at a population level it's quite possible helmet laws have a negative impact on health and safety. I am currently travelling Japan and I have seen thousands of cyclists and not a single helmet (and very little in the way of dedicated cycling infrastructure). To my knowledge Japan doesn't have an epidemic of head injuries.


Soccer players would benefit from wearing helmets though, but they don’t.


Safety first doesn't mean "don't do anything unsafe," it has a broad meaning. With your interpretation I suppose it could mean if you're going to do something, be sure to consider your safety tradeoffs first.


I think “safety first” generally means that you should put safety first when you’re doing something but that I should consider the safety trade offs first when I’m doing something.


Used to raid 25 man World of Warcraft dungeons with a Death Knight tank. His slogan was: "Safety first, then teamwork." That really stuck with me.


From the pilot's world: Aviate, Navigate, Communicate


But how many people died even though they had the ‘right’ gear?


I too like to hold my safety gear to the standard of whether it grants invulnerability. That's a productive way to approach nuance.


I was more interested in the relative likelihood. Most people don’t die from good or bad gear, but from risky or stupid things, gear or no gear.


Sorry can you explain the situation where jeans lead to the death of a hiker? I don't buy it.


I've never experienced any deaths on hikes, but I have experienced folks suffering the initial stages of hypothermia (and not realizing it) when wearing jeans on a multi-day excursion when the weather went from dry and sunny to rainy, to icey-rain to sleet.

Unwaxed cotton absorbs water, stays wet, and shrinks when wet to make close contact with skin--three properties that one does not want when its wet and cold.


So taking your pants off would work? Seems superior to wet clingy cold pants anyway.


That depends on the specifics of the environment, trail, and your pants.

Indeed, going "pantsless" for short periods can be less risky if your pants are already soaked-through, it's very humid, there's ice build-up, and there's little to no risk of skin abrasion from terrain traversal.


In the cold?


If you're wearing "wet ice", convective heat loss from air is preferable to conductive heat loss from water.

Water on skin is a really, really good mechanism for heat transfer (both ways)--hence why we sweat in the heat.


Yah I think html_slice would be ok in a ruby only project. But as the mantra goes if in rails do it the rails way. Helpers are great!


With sqlite and docker.. rails apps are easy to share.. my last project is easy to install and use because of rails https://github.com/ThinkThinkAI/ThinkDB

# change directory_on_your_machine_for_think_db_storage docker run -d --name thinkdb -p 3000:3000 -v directory_on_your_machine_for_think_db_storage:/app/storage thinkthinkai/think_db:latest

TADA.. Rails is great.


doom is deterministic so does not make a good choice for a captcha.. that being said.. this is cute


Sure there is. It's a ratio of inputs to outputs.. even in the example the inputs and outputs are measurable.

The only thing this article gets at is that engineers may not know how to calculate their own productivity; but it doesn't means it's not calculable.


> It's a ratio of inputs to outputs.. even in the example the inputs and outputs are measurable.

But reality is never that clear cut. How’s the ratio look when:

- Peter goes to the park and the breakthrough doesn’t come?

- Or it comes 3 weeks later?

- Or he deletes 100 lines of code and introduces a new bug?


>It's a ratio of inputs to outputs.. even in the example the inputs and outputs are measurable.

So more lines of code is better!

Um, we know this doesn't work that way as a good measure.

This is like comparing algorithms that do the same thing to algorithms that do different things. You're not going to get good valid comparisons. Metrics for one thing may not work at all for another.


The output is measured with dollars, not lines of code. So are the inputs.

It's a perfectly cromulent measure so long as we understand the limitations of the measure. For example, trying to measure the productivity of a day or a sprint? That's silly. Measure the output of a team which does not produce an entire product? Won't work because you'd have to figure out how to apportion the productivity.


That's not the definition.

Eg https://www.britannica.com/money/productivity says:

"productivity, in economics, the ratio of what is produced to what is required to produce it. Usually this ratio is in the form of an average, expressing the total output of some category of goods divided by the total input of, say, labour or raw materials."


It's implied in the definition. Consider the units: a ratio should not have units. Lines of code per programmer per day would have weird units, for example, and could not be compared against number of windows installed per day for per car window installer. The only way for productivity to be useful is to normalize the inputs and outputs into money.


It's a perfectly good measure except it does not help us at all.

The whole reason for this discussion is situations like Microsoft having 200k employees and making $240B in a year. Which employees, teams, or even departments are more productive? They want to know.

And even if it did not matter, likely the expense of this year influences the income over multiple future years, so you compare the dollars in / dollars out for which periods?


The Peelers have historically not been known for their honesty when interacting with Catholics. Racism serves as an institutional tool for harassment and the justification of power over certain groups. There is no genuine honesty in these practices, even if they are ostensibly used to prevent violence.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: