News for hackers. Stuff that matters.

dustinleblanc

Super helpful! Thanks for the tip
Re:Scrum is the new waterfall on Wednesday November 11, 2015 @12:01PM (#10547625)
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; thems the breaks.
Re:Scrum is the new waterfall on Wednesday November 11, 2015 @11:56AM (#10547597)
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 backlog based on those features

3. They start working and implement some features.

4. They find out they don't actually need the washing machine to wink and smile and say its done in a fancy british accent. It was a silly idea marketing came up with that adds no value. They drop that feature from the backlog.

5. They find out making the machine text you when your laundry is done is a desirable feature, they add it to the backlog.

6. Management says the competitor is launching a month earlier than us so we need to accelerate the time table. Engineering gives them the hard news that they need to sacrifice some features. They look at what they have left to do and prioritize the important items and drop the feature for the washer tie-dying your clothes if you want from the backlog.

6. Project enters qa, all tests are passing but testers found a bug. They write a test to confirm and reproduce the bug, they squash it and update the build.

7. Software is working, launch happens, everyone celebrates.

Nothing here says the software has to change anymore; its done, its shipped, its good to go, and done using scrum/agile.

Re:Scrum is the new waterfall on Wednesday November 11, 2015 @11:47AM (#10547546)
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 tests and all of it is done with sprints and iteration.

Agile does no encouraging of adding features. It simply gives you the freedom to choose which ones get implemented based on the current knowledge rather than be forced to make those decisions based on 18 months ago knowledge.

Re:Scrum is the new waterfall on Wednesday November 11, 2015 @11:42AM (#10547515)
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?

Re:Scrum is the new waterfall on Wednesday November 11, 2015 @11:36AM (#10547478)
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 ever said you don't plan in agile and scrum? Where does the magical backlog you start the project with come from?

The point is not to pretend you know things that you don't. You have a severly flawed interpretation of what agile means.

Re:Google to Hacker News: Not Mobile-Friendly on Sunday May 03, 2015 @09:00PM (#9483776)
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 designer's choice to make it look like poop. This is exactly the argument that it's your job as a developer/designer to apply good css. If you do some crazy positioning and lock down your text size so it looks great on a 27inch iMac, its not the browser's fault when it obeys your styles and renders like a turd on an Galaxy S1, 2, or 50 million.
Re:Google to Hacker News: Not Mobile-Friendly on Sunday May 03, 2015 @07:16AM (#9480880)
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 certain resolution. If you never made the decision to write your styles a certain way, you don't have to worry about wierd rendering issues. Unless we want to force folks to use Lynx, it is up to the content provider to say what their content looks like. A browser can not predict the particulars of my design well enough to make those decisions for me.
Re:Google to Hacker News: Not Mobile-Friendly on Sunday May 03, 2015 @06:44AM (#9480805)
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 context. I am capable of writing css that adapts; if I choose not to, my site is less readable. Writing a web browser that makes those decisions for me would make my job of designing the site harder, not easier.

Perhaps an alternative would be some declaration that says "Hey render me this way if you feel like it, but use these all powerful browser supplied styles if I become unreadable"

Some browser's have implemented that reading mode (safari?) and it seems like a cool idea, but I think it only works if you provide really good HTML5 markup.