" Agile blinds you from seeing the whole product and causes bad, segmented, low-focus mistakes. If you are TOO agile you may build a DB/API/Logic/Data structure that is too narrow and limiting of the eventual goal."
I disagree, your goal should be agile too!!!
It has to always change !
ShapeUp TLDR;
>> Backlogs are big time wasters too. The time spent constantly reviewing, grooming andorganizing old ideas prevents everyone from moving forward on the timely projects that really matter right now. <<
They need them because they all have their dependencies that they need to manage separate from this project. A client may need to plan training, transitions, budgets, deprecation of old systems, etc.
Others above me have mentioned the reasons why they need them. But I'll reiterate my emphasis on rough/relative timelines. Exact dates are impossible and the farther away a milestone is, the hazier the date is. As an example, a milestone a month away could be +/- a week, but a milestone a year away could be +/- three months.
Yes. They need to not sell the next version too soon, but start selling soon enough to develop hype. They need to decide if they should invest in updating the previous solution one more time while waiting... They need to decide if the whole is worth the cost or should they develop a different project instead.
Best way is to build your product. A real world product. There only you will be able to confront upon the wall of Reality .... Even the lightest simplest product is the best tool to really learn, as you confront, think, invent, try and errors everything.
Languages have no meaning if there are not tested in real space. I lost a lot of karma here because of discussion on PHP (I am a ruby guy). But at the end you can keep and relie on PHP, because until you don't see yourselve flaws, then those flaws doesn't really exist. And only then you choose your language that will correct problem the right way ;)
After your product is done, show it to us here, return to HN and expose your vision, and receive rewards and critics at the same time.
Sorry guys,PHP is the outdated! (From someone who start PHP in 2000 with PHP 2.0 and is still reading lastest Laravel code source).
To young people: choose your language wisely, you don't need to know PHP to be successful in Web dev
The top open-source ecommerce platforms (magento, woocommerce, etc) and content management systems (wordpress) are all in PHP, and yes they were written before 2000. You don't need to know PHP to be a successful web dev if you are working at a silicon valley tech / social media company, but e-com and content management are still what most companies are trying to do on the internet, and if you are interested in a tech career outside of silicon valley, being handy with PHP is great.
That's certainly true, but we're living in a funny time, everything has evolved so quickly that there are 15yr old PHP apps rubbing shoulders with 7yr old Rails apps next to 4yr old Node apps and now React etc. Some of that represents actual progress, some fashion, but for all those legacy apps, someone has to keep the lights on (until the plug gets pulled). That said, I don't really miss PHP too much, it was much nicer than Perl for adding a little magic to html, but building anything big was not fun (I gather Laravel makes that better these days, but there are a lot of other choices if you're starting fresh).
That doesn't add up. There was no "PHP 2.0"; the language was still referred to as PHP/FI at that point. And PHP 3 was released in 1998 -- by 2000, I have a hard time believing you would have still been using PHP/FI, which was a much more limited tool.
