91–100 of 142 posts
The entire Craftsman movement under Raskin, Morris etc. started up because of the move of craftsmen into factories, where they worked on parts of the whole and could therefore not be craftsmen anymore.
Oftentimes managers will make demands that interfere with ownership of the code. Such as requiring something to be finished in half the time it would take to do it without technical debt. Over and over and over again. I have had a lot of clients like this. It's very common especially for lower budget projects. You can literally cut corners you don't really want to or just get replaced by someone who does. They will o…
Advise them of the issue. If they still want it, their funeral. Anytime I move away from this frame it's not worked out for me.
Earlier quoted context omitted.
A cabinetmaker creates the polished front and the unfinished rear. A software/hardware company needs everyone being part of the polished front at least in spirit. I liken it to people dressing for their job.
I haven't used an Apple product in some time, but to me it always felt like their software was the unfinished rear.
You see it an awful lot with internet routers lol.
Earlier quoted context omitted.
I think that's two very different things - a complete set of features done poorly vs. an incomplete set of features done well. In general it's best to err on the side of the latter, it's going to give the customer a better UX. What exactly was the original iPhone missing? The only thing in the OS I recall was copy/paste. The other things we'd take for granted today likely weren't conceived then, including the App Sto…
> The other things we'd take for granted today likely weren't conceived then, including the App Store. IIRC, one could get apps on other platforms like Blackberry, even over the web. Apple's anti-innovation was a closed-garden storefront.
Earlier quoted context omitted.
It is not about the backs of cabinets. It is about telling your customers how big of a deal the backs of cabinets really are.
The back of Apple cabinets are are actually pretty good even in the Tim Cook era. [1]: https://www.cultofmac.com/320883/why-samsungs-design-sucks-i... [2]: https://ioshacker.com/iphone/image-compares-ugly-samsung-bea...
> If the technical debt is a problem, 1) we shouldn’t have put it in there, and 2) we should include it in our estimates and address it. Yes. Don't tell your boss that you'll need to take time to address technical debt. The boss will always say "No don't do that, just add the feature". Sometimes they add "We'll fix that later." Later never happens and eliminating related technical debt is part of implementing the fea…
Earlier quoted context omitted.
Our profession doesn't always work the way you describe. Some companies want cogs, some want professionals. I can't give you advice beyond that, there are too many different circumstances. But in most of the places I've worked, it's been developers, not managers, cutting corners. Sometimes these are good choices, informed by product context and trade-offs. Sometimes it's a perceived urgency that doesn't actually exis…
> But it's almost never a micromanaging boss asking for something specific. They don’t ask people to cut corners specifically, they just create a culture where speed is paramount above all else. Where the only metric of success is tickets completed per day.
This doesn't mean that there's never a need to hurry, external deadlines exist, but these are the minority in a healthy organization.
Earlier quoted context omitted.
The back of Apple cabinets are are actually pretty good even in the Tim Cook era. [1]: https://www.cultofmac.com/320883/why-samsungs-design-sucks-i... [2]: https://ioshacker.com/iphone/image-compares-ugly-samsung-bea...
I don't understand why someone would even want the ports to all be on the center line.