wilkosez

6 ms·

1.
by wilkosez 8y ago
If they want to learn, yes it's great. Some turn up in the morning, however, work on their task for the day and go home. If they reimplement a chunk of the codebase somewhere else, because they feel they need to be writing more code to
2.
by wilkosez 8y ago
> If you really have a fleet of web servers burning CPU and you aren't tracking the costs, then I guess "it works" until someone figures out there isn't any money left in the coffer. What if the costs are fixed? (own
3.
by wilkosez 8y ago
This was almost cathartic to read!
4.
by wilkosez 8y ago
"The code in production works" This might be what I have the biggest problem with. To a customer, it works. The customer is happy, they pay their money, which makes management happy, and we all get paid. So the site takes 10 secon
5.
by wilkosez 8y ago
Personally, I dont, I escaped into server admin. Part of that was trying to get the crap to actually run well on the systems we had! But the organisation is slowly carving our monolith into microservices (Because buzzwords will save the day
6.
by wilkosez 8y ago
I agree, which is why I pushed for it. But it does depend on the quality of the peers, and should go beyond whether the story met the criteria or not. Feeding that back through the process is pointless when it inflates the complexity of fut
7.
by wilkosez 8y ago
I agree 100%. Thankfully I dont do agile any more, but I'm close to several teams that do. My fondest memories are: No over-arching design (Implement feature after feature however the hell anyone likes) Once said features are implement