101–109 of 109 posts
2021: When programmers still sourced images for their blog from Getty Images rather than just generating whatever they needed.
Generating = using generative models trained on Getty Images and the like.
Earlier quoted context omitted.
Generating = using generative models trained on Getty Images and the like.
I mean, I wasn’t making a value judgement with my post. I’ve just noticed a lot more art (as opposed to diagrams) in blog posts recently and I was surprised that this one actually had licensed images in it. Then I noticed the date. That is all.
Earlier quoted context omitted.
Sometimes a computer is just more accessible than paper.
I remember being laughed at when I cut out coffee filters with a certain angle in order to plan how I would position motion capturing cameras to cover the room optimally. My manager liked the pragmatism though
Earlier quoted context omitted.
I think it’s different for developers. They know that for other people (even for their hierarchy), they are just doing mystical, abstract "work". In my experience, a lot of developers learn to use this to convince themselves and everyone else above them that they HAVE TO do this full refactoring. imo, this all comes down to the fact that management is still not able to assess the quality (or even the real nature) of…
For several bosses, this scenario you describe has fallen under the concept of 'kill your heroes'. Sometimes the person really is brilliant and you should do anything to keep them. But if it's because they're the only one who understands their code, then they are a liability.
Or is the hero deliberately sabotaging such efforts to maintain scarcity, and thus their higher value?
Earlier quoted context omitted.
> people with no output for years canned Often I see this happen, and the result is the company loses out somehow. I think maybe metrics for “output” are wrong in many cases, and you’ve just canned someone who had a useful or even critical role you didn’t know about. A lot of people who are important to company operations are invisible!
output doesn't capture accumulated know-how. If you fire researchers you loose know-how, hence you loose potential.
Also accumulated know-how can be partially visible by writing out docs, patents, guides and the like. Definitely not enough but can increase visibility.
Earlier quoted context omitted.
What does that have to do with implementing a 2D model of a room with movable furniture? How is paper not accessible? Do people not have note paper? What about junk mail? The last few pages of a book? You can make a scale ruler with any uniform markings.
actually using paper for designing objects, especially complicated objects, is an extremely annoying process. lots of erasing lines causing paper to break, areas with internal complexity requiring sub-diagrams, often causing nesting complexity to blueprints on large projects. It makes it so much harder to simply view and talk about the current state of a design when that means sorting through filing cabinets for revi…
Earlier quoted context omitted.
output doesn't capture accumulated know-how. If you fire researchers you loose know-how, hence you loose potential.
lose*. It's not so hard, man. Also accumulated know-how can be partially visible by writing out docs, patents, guides and the like. Definitely not enough but can increase visibility.
Earlier quoted context omitted.
This sounds right up my alley. Any suggestion on roles/titles/companies to keep an eye out for? I’ve been a SWE for 20+ years and have a background in mechanical engineering
Research scientist is one common role I’ve seen, but there are often supplemental engineering roles for these as well. Another way to find these is look for moonshot projects at any major company. Basically divisions that are outside of the core product and business operations. Some risk in these though, since they can be the first cut in a bad economy.