Timeline for Are missed deadlines common in programming jobs?
Current License: CC BY-SA 3.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 7, 2014 at 15:20 | history | edited | Tulains Córdova | CC BY-SA 3.0 | some grammar and style corrections |
| Aug 5, 2013 at 21:44 | comment | added | Michael Shopsin | Bonus for quoting the Mythical Man Month; Frederick Brooks holds up after all these years because he focuses on people not technology. | |
| Jul 30, 2013 at 20:38 | history | edited | Mike Partridge | CC BY-SA 3.0 | grammar, wording |
| Jul 30, 2013 at 19:58 | history | edited | Tulains Córdova | CC BY-SA 3.0 | added 5 characters in body |
| Jul 30, 2013 at 19:56 | comment | added | Tulains Córdova | @MikePartridge They are not direct quotes. I will add the "paraphrase" thing. | |
| Jul 30, 2013 at 19:33 | comment | added | Mike Partridge | If your bullet points are direct quotes from the book, formatting them as block-quotes would be better. If not, it might be more clear to replace "According to" with "To paraphrase", and I can help with some grammar mistakes in the bullet point text. | |
| Jul 30, 2013 at 19:29 | history | edited | Mike Partridge | CC BY-SA 3.0 | grammar |
| Jul 30, 2013 at 19:07 | history | edited | Tulains Córdova | CC BY-SA 3.0 | added 3 characters in body |
| Jul 30, 2013 at 16:51 | comment | added | gnat | related question: Does software reuse preclude process repeatability | |
| Jul 30, 2013 at 16:07 | vote | accept | CommunityBot | ||
| Jul 30, 2013 at 15:07 | comment | added | Maja Piechotka | For example in game industry the programmers don't do the tasks considered standard 10 years ago (say - models, materials) but create a tools for artists to do those tasks. So once we reach a 'solid base' programmers are not needed any more (or at least not in a sense we are using them today). | |
| Jul 30, 2013 at 15:04 | comment | added | Maja Piechotka | @user61852: Regarding the repetitiveness - one thing computers are great at is automation. Say you need to build a simple blog - at the point when you would have accurate 'estimates' you will get a wordpress (or any other blogging system) in place so you don't need to do any of it (in case of bridge you still have different environment so you need to adapt more carefully as the rock might be different or there might be a bird habitat or it might destroy the view) - the programmers might be more responsible for creating the tools (the standard bridge model). | |
| Jul 30, 2013 at 13:04 | comment | added | Maja Piechotka | @user61852: You misunderstood me. The 'plan' to engineering is as 'source' to computer science - i.e. detailed description of every component - but once we have it we can build it (enter make or whatever).What is 'plan' in computer science would be a 'plan of plan' in engeneering. The difference is that make in computer science takes at most few hours while writing source code (including tests and integration) takes months while in engineering the planning can takes months (including structural calculation) while building takes years.So the variance of planning have lower impact on latter. | |
| Jul 30, 2013 at 12:47 | comment | added | Tulains Córdova | @MaciejPiechotka By repetitive I didn't mean identical, just as no bridge is identical to another, but since bridges have been built for thousands of years some solid base exist. I don't agree with you in that software is only plan. You have to code, test, integrate, etc. | |
| Jul 30, 2013 at 12:38 | comment | added | Maja Piechotka | I would subscribe to the idea that the software is plan (in terms of plan in engineering - describing every detail of project). In case of engineering the time of physical construction dominates so large variance in planning doesn't play a role. However as software consist of only plan... "The state of the art in software development hasn't reached the point when software projects are repeatable and almost risk free" - in those cases why do the project at all? If something is repetitive and can be automated then it does not need to be done at all multiple times but can be done once and copied. | |
| Jul 30, 2013 at 12:18 | comment | added | Mike Dunlavey | + Good answer, but having had some exposure to mechanical and civil engineering, it's amusing how programmers make facile comparisons to building bridges and other things, when they haven't the faintest idea how those are built. | |
| S Jul 30, 2013 at 12:15 | history | suggested | Jordan Gray | CC BY-SA 3.0 | Spelling, grammar, formatting. |
| Jul 30, 2013 at 12:10 | review | Suggested edits | |||
| S Jul 30, 2013 at 12:15 | |||||
| Jul 30, 2013 at 12:03 | history | answered | Tulains Córdova | CC BY-SA 3.0 |