3 ms·
My take on X is a professional job is this: it depends. If you have 20 developers in your team, one or two better be good at UX, one or two better be good at lo
by chime 16y ago
My take on X is a professional job is this: it depends. If you have 20 developers in your team, one or two better be good at UX, one or two better be good at low-level coding, one or two better be good at SEO and so on. If you only have two developers, they better be good at the core product and be mindful of everything else. The third developer is never going to be a tester, QA, or UX if your first two developers can't keep up with the core.
In a large pharmaceutical company with 10,000 employees, you have people with job titles like "Quality Assurance Lead II (Wound Management)". In a startup with 3 people, people call themselves CEO, CTO, and CFO. As the startup grows, it will need people. Eventually you'll hire a "QA Lead II" or "UI Editor (Web-Apps Division)". The main question is who do you hire next? Do you need a graphic designer more than a helpdesk person? Do you need a project manager more than an AP assistant?
- bluishgreen 16y agoWhat I took away from the post is this. There is a certain quality metric that one needs to be aware of to do a good job at X. Programmers all do Sysadmin work from time to time. And founders always double as Sysadmins. But just because its not your primary role doesnt mean you can leave random ports open and do a really bad sysadmin job. The same is true of UX design. But the problem is while the distance from programmer to sysadmin seems to be a short walk, the distance from programmer to UI/UX from my experience is a long one. Sure, we cannot/should not afford another guy with a title, but Graham is pointing out a valid blindspot for all of us and it should be taken into account when making decisions.