2 ms·
I'm not sure about this. It might be best for some but not for others. The most I ever learned was on a train wreck of a project where management decided to d
by jayd16 7y ago
I'm not sure about this. It might be best for some but not for others. The most I ever learned was on a train wreck of a project where management decided to do a large rewrite compounded with redesigns and growing scope. I was the sole Android dev replacing a team of contractors. The only good thing about the turmoil was how many chances I had to iterate on things and redo them from scratch trying new patterns. I was the only dev but the product, design and QA teams reviewed the results of my work. It meant I could be courageous in my engineering changes but still grounded by product reality.
I wouldn't recommend this as a way to do business but being paid to crank out feature verticals only to throw them away and start over was a big learning experience.
I've also had experiences more inline with the article as well but it's not the only way to learn and might not be the best even if it's a common, low risk way to learn.