jfabre

22 ms·

91.
by jfabre 13y ago
I used to think that way, then I realized that I should worry about building a product people will pay for before worrying too much about technical debt. It's almost a Maserati problem when you think about it.
92.
by jfabre 13y ago
Can you explain what you find more expressive in c# compared to ruby? I've been a c# developer for over 5 years and I have to disagree with almost everything you said. Ruby blew my mind when I learned it.
93.
by jfabre 13y ago
So true, we had to read Steve Blank to figure out this one. Our previous mindset was: let's build an 'MVP'(more like alpha/beta) and see how it goes. Don't code an half-baked product to test the market when you can build demos and talk to
94.
by jfabre 13y ago
Whatever you say, I actually learned vim with this game and also had moderate fun for only 10$ or so. It's clearly a win for me. The big payoff with this game is that it forced me to practice. Within two hours of game play I had the 'hjkl'
95.
by jfabre 14y ago
Very small customer here. I don't know much about the abstraction you provide us and I don't want to know as long as things go well. To my point of view, the routing is "random" thus kind of unpredictable. If scaling becomes more of an issu
96.
by jfabre 14y ago
- "Number 3 is the problematic one. If the exceptions are unchecked we’re in the wild west again." Hum, I'm going to argument at the same level: Wat?
97.
by jfabre 14y ago
I agree with you, but before one can transcend TDD, one has to learn it. The pupil was no longer confused. ;) Seriously, the current status quo most of us live in right now is zero to very few automated tests. That's what I'm arguing agains
98.
by jfabre 14y ago
I did not know much about automated tests, that's true. One thing I noticed though, is that if you don't write tests before hand, you don't have time to write them later. Your code tends to be harder to test too, so you never really write t
99.
by jfabre 14y ago
I've seen big company devs so overwhelmed by messy production code that any small feature change would require 2 weeks of work. I've seen startup devs who couldn't cope with changing requirements fast enough. There was just too many moving
100.
by jfabre 14y ago
www.vim-adventures.com :)