Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think the work flow that we have adapted is not something that encourages the long term general solutions. We all have feature to deliver every two weeks. We are being monitored every day in terms of tickets being moved and commits being done. (Thank you jellyfish)

It seems like the actual value is measured wrong in corporate environment and it does not enable focused long term plans and solutions.

I have a friend who negated 8 full Java classes with 50 lines of SQL. But, he did it without telling the management cause if did, then he would have to answer to them everyday. And he was learning his way and experimenting and changing all over the place. I don't thinking deeply about problems for creating better solutions is appreciated or even recognized. And it takes time to learn solving problems that way.

Not attributing this to the corporate environment completely, but if you only care about features and its delivery ASAP, well... you will get them ASAP inspite of what horrors lurks under the hood.



> I have a friend who negated 8 full Java classes with 50 lines of SQL

I wouldn't brag about that. It's trading one headache for another.


I think this is the right design for the scenario. It is for a dashboard and so many queries were fired for a read only operation.

But, generally, I agree, it all depends on context.




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

Search: