87 karma · joined October 7, 2011
Is there any way I can get feedback on my application?
There is a lot of solid reasoning (and examples) leading up to this point, but one notable point was this conclusion:
``` [London-school TDD] sits at the extreme end of the trade-off between coupling and design feedback: incredibly rich feedback about the design of the system, typically resulting in small, hyper-focused units with carefully-chosen naming and easy-to-use APIs. They come at the cost, however, of significantly decreased freedom to refactor the implementation aggressively, which is why Discovery Testing recommends developers default to deleting-and-redeveloping local sub-trees of dependencies when requirements change significantly. This can result in reliably comprehensible designs, but with an increased base cost to requirement changes. ```
I really agree with this. I spent a few years working with a consulting company which preaches London-school TDD. We did a lot of work in dynamic languages, and refactoring was particularly difficult because we had to make sure that all of our mocks (and other test code) lined up with the refactored APIs.
I hate to take the discussion here, but I wonder how Static Typing changes the experience of London-school TDD. Does it become easier and less-frustrating to refactor your test-code?
This doesn't give you the full picture, since the Twitter accounts are intended to be consumed by foreigners. Nonetheless, it's really easy way to get some idea of the typical tone/topics.
I wonder if most people realize that the "innovation" involved has to do with franchising and finances, rather than the fact that it's a cart that sells coffee.
It's expected that the employer is going to fuck over the employee when it's convenient (you're naive to think otherwise).
You're putting yourself in an unfair (one-sided) position by deciding that you have to behave nicely towards the company.
I lack the karma
https://github.com/skatenerd/buses/blob/master/artifacts/hea...
The results were largely depressing, but unsurprising.
Meaning, taking comfortable estimates (on the order of 1-2 weeks) and just, by default, sliding them earlier by one or two days?
It's a subtle way for management to cope with the anxiety that is trickling downhill, without engaging in or admitting a period of Crunch Time.
I used to work at a consulting company, and I'd be in an open plan office with 5 other teams, working on 5 other projects. Everyone was working through engineering decisions that were unrelated to my own.
If everyone's on the same team, at least, there is some saving grace to the open plan office - you overhear stuff that you might be able to contribute to.
Found the job by writing cold emails to people in Beijing through meetup.com