I'd guess it's the inheriting project's lazy styling (and to your point, subsequent QA) that's making it break.

Ah yes. It's not criticism of base ui; more criticism of published, branded stuff... that don't work, haha.

If writing the code is easy, why would I bother continuing to do other hard stuff?

I see that too. I'm of the unpopular opinion however that writing "code", without any other qualification to it, has always been easy. Writing clean, working, robust, maintainable, defensive code has always been a lot harder, not in the least because it requires discipline, and teamwork: I don't know anyone that writes super-awesome code without having a couple extra eyes on it.

I hate lazy code in my production apps (and I hate it in Android source code even more, and in my opinion it is full of it) but I expect to see it more and more. More verbose pull requests, more lines on 

 diffs... I really need to start automating me some diff reviewing haha.

Design

AskSN

devs

What do you use for your frontend stack?

k00b

> I'd guess it's the inheriting project's lazy styling (and to your point, subsequent QA) that's making it break.

Ah yes. It's not criticism of base ui; more criticism of published, branded stuff... that don't work, haha.

> If writing the code is easy, why would I bother continuing to do other hard stuff?

I see that too. I'm of the unpopular opinion however that writing "code", without any other qualification to it, has always been easy. Writing clean, working, robust, maintainable, defensive code has always been a lot harder, not in the least because it requires discipline, and teamwork: I don't know anyone that writes super-awesome code without having a couple extra eyes on it.

I hate lazy code in my production apps (and I hate it in Android source code even more, and in my opinion it is full of it) but I expect to see it more and more. More verbose pull requests, more lines on `tag..tag` diffs... I really need to start automating me some diff reviewing haha.