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

Because you might have architects specifying exactly what needs to be programmed, so the software development part is mostly done.



What’s this like? The architects I work with throw together a shitty flow chart that is very high level, say, “here it is,” and then I need to figure out the other 90% to make it work. I basically ignore everything they give me, because it’s completely useless and lacks all understanding of what we’re trying to do. I then give them something that works, and if they want to update their flowchart to reflect reality, that’s up to them… they never do.

They also tell me, “this is the payload your API needs to accept,” and ignore the fact they half of what they are sending has never and will never be used by anything. It’s just needless complexity I add to get them to stop having meetings about it.

Are architects supposed to actually give me something I can work with and make my life easier? I’ve never experienced this, but I work in a very dysfunctional organization.


In which case you need to get yourself promoted to be an architect in addition to a programmer.


Waterfall is dead.


The idea that you can dream up architectures but not implement them and expect anything worthwhile to come out reeks of inexperience.


no one said said, stop chasing strawmen.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: