dustinleblanc

4 ms·

1.
by dustinleblanc 11y ago
Super helpful! Thanks for the tip
2.
by dustinleblanc 11y ago
If you are writing integrations for API features that are fantasy at this point, you are digging your own grave. You have extended your risk and when you find out six months from now that you bet the farm on a useless feature, oh well; them
3.
by dustinleblanc 11y ago
Absolutely none of this matters to agile vs. waterfall. You can accomplish this with agile development: 1. People meet at the beginning of the project and say "heres what we think our washing machine needs" 2. They create a backlo
4.
by dustinleblanc 11y ago
No, it doesn't, you are making things up. There are plenty of agile/scrum teams who run continuous integration that won't allow code that breaks a build to even be in production. They write integration tests and acceptance te
5.
by dustinleblanc 11y ago
You can do agile test first too. "hey here's a feature we're pretty sure we need: As a foo, I need to bar, So that baz okay, write the test, make the test pass, refactor" What about that isn't possible in agile?
6.
by dustinleblanc 11y ago
Agile has never said you don't plan, you just don't fully trust plans made without all the information. You make your plan, and its great as far as up front plans go, but it WILL be wrong in some ways, and you will update it. Who
7.
Lightweight alternative to JavaScript breakpoints(singlebrook.com)
1 points by dustinleblanc 11y ago|0 comments
8.
by dustinleblanc 11y ago
This is exactly my point, the browser doesn't make me choose comic sans and wingdings. I hold in my hands, the ability to not make a site look like garbage...by using less crazy css. Information is what is relavent, it's the desig
9.
by dustinleblanc 11y ago
No those websites should be expected to be readable at all times, but it up to the provider of the content to make that happen. Old sites read fine, as long as their stylesheet didn't make decisions to try to look a certain way at a ce
10.
by dustinleblanc 11y ago
Its up to the person who wrote the site stylesheet to make it behave in this instance. It's not Safari, or Chrome, or FF, or Dolphin that made me declare that my text should be this big or that my div should be that wide no matter the