111–120 of 180 posts
The essence of this post is about craftsmanship, value, and caring about what you're doing. It's really hard to put this into words. There's certainly a gradient and trade-offs to be made. In most businesses, the priority is to make money. This is not bad. Business owners deserve to make money for their efforts. It's always been the case that "bean counters" will optimize to increase profits. If you want a superior p…
The essence of this post is about craftsmanship, value, and caring about what you're doing. It's really hard to put this into words. There's certainly a gradient and trade-offs to be made. In most businesses, the priority is to make money. This is not bad. Business owners deserve to make money for their efforts. It's always been the case that "bean counters" will optimize to increase profits. If you want a superior p…
From what I recall, David Cutler was quoted in "Showstoppers" about DEC having an engineering culture when he joined but he got discontented after a few years (when his team shipped VMS) because it was too bloated.
Microsoft could be a bit different though. I remember reading from a book that Bill Gates wanted to have PMs control projects, which caused a lot of conflict. I do not remember the timeline, but it must be before Win NT.
So the best bet is to go in early, stay for 5-10 years until the environment starts to rot and you can exercise all of your options, profit, and then jump to the next. The more senior you are, the more control you have, the happier you are. David Cutler is a great example. He did stay in Microsoft but he managed to be a hand-on.
Earlier quoted context omitted.
I am baffled why you are inserting good and evil into this. He just seems to want to work at companies that value craft and attention to detail. It just like the jobs quote about the back of the furniture also being attractive.
I was honestly expecting the link to be somebody's quixotic rant about software that does "good" in the world rather than serves ads and I was pleasantly surprised to see something I can actually relate to.
Earlier quoted context omitted.
Sure, not every edge case deserves top billing, but when the little things stack up, they subtly signal whether anyone cared. It's a vibe thing
Death by a thousand paper cuts Proverbs become eerie the longer you live. Almost like, woah, that one sentence was actually universally true? Well hot damn! Keep neglecting these small things and you’ll see the level of unconstrained shit you will have unleashed onto the world. With enough of us doing so, we can take part in the great collective festival of mass garbage accumulation (aggregate all the paper cuts). Th…
This is going on a t-shirt
Not for me. Exccessive customer obsession puts me off as customer. Don't try to read too much into me. Don't try to sell too much. Don't try to please me too much. Don't think about me too much. Instead, think about the stuff you are offering. Treat it as if you are building it for yourself, and not for selling. Build it the way your like most. Sound as if you don't care about selling. Be proud of it. Get off of the…
I feel like I'd agree with your comment if it was in reply to an entirely different article. As in: I agree with your sentiment and ideas. Out of context, you're bang on correct. But I don't think paying attention to details (like pluralization) is an indication of obsession with the customer, at least not for me. It's about caring about the craft. When I'm building something for my own use, I care about every aspect…
I don't consider than pandering. It's respect: Respect for the craft, for the craftsperson, and for the end recipient/customer."
This was my intention. Thank you!
Number "two" in Polish (depending on context): dwa, dwoje, dwie, dwóch, dwiema, dwom, dwojga, dwojgu, dwójka, dwójki, dwójkę, dwójką, dwójce, dwójko So that's just my mother tongue. It think your problem is a bit more complex than (s).
Earlier quoted context omitted.
Satan is very underappreciated as an employer.
I'm sure he pays well too!
”Nontheistic Satanism, as exemplified by LaVeyan Satanism (practiced by the Church of Satan and First Satanic Church) and The Satanic Temple, holds that Satan does not exist as a literal anthropomorphic entity, but rather as a symbol of a cosmos which Satanists perceive to be permeated and motivated by a force that has been given many names by humans over the course of time. In this religion, "Satan" is not viewed or depicted as a hubristic, irrational, and fraudulent creature, but rather is revered with Prometheus-like attributes, symbolizing liberty and individual empowerment. To adherents, he also serves as a conceptual framework and an external metaphorical projection of the Satanist's highest personal potential.”
You see, Satan is not just a biblical figure, but also the average IT company.
Man I'm so far away from being concerned about this...just like, we still need to fix duplicate icons that mean different things, phrases like "Are you sure to delete?", mis-aligned text/inputs EVERYWHERE... If this is your biggest concern at a company (regarding the UI at least), you are miles ahead of us. Congrats
Earlier quoted context omitted.
Holy moly, and I thought French (my mother tongue) was complicated due to conjugation. I'm fascinated by what possible context could call for this many variations on how you spell/pronounce a number. Any chance you know of a good article on this? (I could ask ChatGPT, but I'm trying to let go of that crutch.)
I'm not a linguist so I can't send any articles that explain the origins of this mess. But here are actual examples of usage: dwa ptaki (two birds) dwoje ludzi (two persons) dwie dziewczyny (two girls) idę z dwiema dziewczynami (I'm walking with two girls) dałem kwiaty dwom dziewczynom (I gave flowers to two girls) kanapa dla dwojga (a sofa for two - gender unspecified) dałem śniadanie dwojgu (I served breakfast for…
The article makes sense for me. I see it like the broken windows policy of software development. If you allow sloppiness in the small places, the places where you allow it will grow, until your code base is riddled with it. The fight for code quality is also a fight against damaging bugs and against exploitable vulnerabilities. One big problem with the fight is that industry is incentivized to cut corners. '(Fast, Ch…