3 ms·
It's a good argument for specialization. If your job is "I design web apps" then it's gonna be new and unpredictable work every time. If your job is "I do softw
by chadash 6y ago
It's a good argument for specialization. If your job is "I design web apps" then it's gonna be new and unpredictable work every time. If your job is "I do software consulting for small businesses to migrate from excel to quickbooks, or quickbooks to an ERP", then you'll probably have a lot of reusable code and making predictions will be easier. Furthermore, you can probably do a better job in 10 hours than what someone else might take 30 hours to do. And the customer wins out too since they have quicker turnaround time and battle tested code/processes.
- tonyedgecombe 6y agoThere is a benefit to specialisation but I think your example of migrations probably isn't a good one. Those projects have a tendency to stretch out because you can rarely get a handle on the data. The customer will tell you they've given you everything then a week later start complaining about something you haven't seen (but is still your problem). Of course you could argue this needs to be tied down before you start work but often this is the bulk of the work. Even if you did get something in writing it's turned into an adversarial relationship once you start refusing work or demanding more money.