Hacker News new | past | comments | ask | show | jobs | submit login

Ah. If so I still think we don't understand each other.

It's not "we don't know what to do with you go read some books". It's "we have 80,000 time and labour business rules that are unique to our public sector organization and you should not code any business rules into our payroll system until you have a vague understanding of how we operate". That IS a serious client and a serious project and that study time IS serious. It's important. It's a success predictor. If you ignore it or are coxky and go "meh I've seen it all before " you'll make an expensive business error. Not necessarily a technical error, not a memory leak or suboptimal sql. But people will get paid wrong or your ledger will be wrong or another business impact.

Again, I may live in different it world than average active HN participant. But developers on my projects speak business to functional analysts. They understand payroll or Financials or hr or whatever in general, and also understand them in particular as it pertains to client. It's not wasted time or inefficiency. Not sure if I'm presenting my case well or persuading anybody - but I'm used to paying people to learn when they join projects, including senior niche experts :-)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: