I think this is true for engineers as well!
I think this is true for engineers as well! I enjoy getting to know the "theme" of my favorite coworkers over the years. There was: * The fellow who always looked for the simplest hack possible. Give him the most annoying problem, he'd pause, go Wait a minute! and redefine it to have a very easy solution. He typed very slowly, but it didn't really matter. * The one who truly loved code itself. He would climb mountains to find the most elegant, idiomatic way to express any program. Used the very best practices for testing, libraries, all that. He typed very fast. * The former physicist who spent all his time reading obscure mailing lists on his favorite topics. His level of understanding of problems in his domains of interest was incredible. I could go on and on! It's such a fun taxonomy to collect. All of these friends were marvelous at solving their particular flavor of problem. As for myself, I like to think that my "trick" is to spend a long time poking at the structure of a problem. Eventually the solution I was looking for doesn't matter anymore, but the tools I developed along the way are pretty useful to everyone!
Posted by tibbar on Nov 29, 2025, 4:32 AM
Tags
Related issues
- The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
- (My comment is about detached houses).
- The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
- > steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
- Why is there no comparison with FLUX 3 Image?
- > our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
hackernews (Other)
The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
(My comment is about detached houses).
The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
> steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
Why is there no comparison with FLUX 3 Image?
> our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Why is there no contact form?
The biggest problem with plugging a generator into an outlet is you need a double ended cord.
I think this is true for engineers as well!
I think this is true for engineers as well! I enjoy getting to know the "theme" of my favorite coworkers over the years. There was: * The fellow who always looked for the simplest hack possible. Give him the most annoying problem, he'd pause, go Wait a minute! and redefine it to have a very easy solution. He typed very slowly, but it didn't really matter. * The one who truly loved code itself. He would climb mountains to find the most elegant, idiomatic way to express any program. Used the very best practices for testing, libraries, all that. He typed very fast. * The former physicist who spent all his time reading obscure mailing lists on his favorite topics. His level of understanding of problems in his domains of interest was incredible. I could go on and on! It's such a fun taxonomy to collect. All of these friends were marvelous at solving their particular flavor of problem. As for myself, I like to think that my "trick" is to spend a long time poking at the structure of a problem. Eventually the solution I was looking for doesn't matter anymore, but the tools I developed along the way are pretty useful to everyone!
Comments (0)
No comments yet. Start the discussion.