| ▲ | karim79 5 hours ago |
| I see. So AI is reducing the number of jobs in the tech sector because fewer people are needed to ship stuff (thanks to AI). And since fewer people are needed across the tech sector then we don't need things like Jira anymore because it can all be done on post-its or Google sheets or something, so there's no need for Atlassian accounts anymore. And Atlassian can now do more with less thanks to AI. I can't wait for Atlassian physical sticky-notes to take over. [Edit: grammo and formatting] |
|
| ▲ | prpl 2 hours ago | parent | next [-] |
| Agile itself is predicated on software being difficult to ship/expensive. It might not make sense to continue (waterfall might be better actually) The real problem is that company decisions will never be made as fast as software can be written (and rewritten) now. |
| |
| ▲ | dragonwriter 2 hours ago | parent | next [-] | | > Agile itself is predicated on software being difficult to ship/expensive. No, the opposite; it is predicated on software being cheap and easy to ship, but hard to correctly anticipate the needs for. > It might not make sense to continue (waterfall might be better actually) Waterfall, not agile, is predicated on software being difficult to ship/expensive. | | |
| ▲ | jboy55 2 hours ago | parent | next [-] | | Imagine doing AI development in waterfall. You spend weeks writing your prompt, when you think you have it perfect, only then do you submit it to the AI. Then you wait a week or so, and see what it produced, expecting it to be exactly what you wrote. Or, do you tell it the basic functionality you want, test it out, then add feature after feature that you want, sometimes dropping them and sometimes adding new ones that you thought of as your worked. | | |
| ▲ | lazystar an hour ago | parent [-] | | > Or, do you tell it the basic functionality you want, test it out, then add feature after feature that you want, sometimes dropping them and sometimes adding new ones that you thought of as your worked the problem with this is long term maintainability. it works - and the engineer understands how it works - but a) the AI does not prioritize cleanup/organization/naming, and b) there's a blind spot/boiling frog type of phenomenon that can prevent the engineer from spotting the growing problem. the codebase becomes recognizable only to them. the engineer sees all features working, all bugs fixed, 90% test coverage, and submits it for a PR. the engineer tasked with reviewing the PR will treat it as slop. |
| |
| ▲ | atomicnumber3 2 hours ago | parent | prev [-] | | The vast majority of "AI is changing everything!" takes I read say more about people's fundamental misunderstandings of the software development lifecycle (the real one that companies actually do, not the one that people think they do or what companies say they do) than about anything AI is going to change about software eng. If anything, their solving the complete wrong problems and being blind to the actual problems is probably a reason AI won't actually result in any real, top-level appreciable gains in shipping speed. |
| |
| ▲ | oblio an hour ago | parent | prev [-] | | > Agile itself is predicated on software being difficult to ship/expensive. Software is still "difficult to ship/expensive". Code is very cheap now. Any kind of non-slop software is still expensive. |
|
|
| ▲ | nunez 2 hours ago | parent | prev | next [-] |
| Glad you mentioned Google Sheets. I moved my personal task tracking from Trello to Notion to Sheets. Sheets has been the best for me. Infinite customizability, fast, lean. |
|
| ▲ | talldan an hour ago | parent | prev | next [-] |
| I don't think it's completely right. Jira is a task manager, and the task throughput supposedly remains the same, just fewer assignees. I think these companies should be pivoting to something where tasks/issues are the places you write the prompts for the AI, or augment the prompts that devs use. It's a big shift though. |
|
| ▲ | bdcravens 4 hours ago | parent | prev | next [-] |
| In many cases, sticky notes are more productive. |
| |
| ▲ | llbbdd 3 hours ago | parent | next [-] | | Dragging a card to the "Done" column just doesn't hit as hard as crumpling up a sticky note and yeeting it. | |
| ▲ | nunez 2 hours ago | parent | prev | next [-] | | And really hard to coordinate with remote teams. I say this as a lover of sticky notes. | | | |
| ▲ | 4 hours ago | parent | prev | next [-] | | [deleted] | |
| ▲ | oliyoung 4 hours ago | parent | prev | next [-] | | wait, can you _see_ my desk right now? | |
| ▲ | thoman23 4 hours ago | parent | prev [-] | | Where "many cases" all involve a team of 2 to 5 people working together in the same room and never bringing work home. | | |
| ▲ | sanswork 4 hours ago | parent [-] | | I'm pretty confident though with no solid evidence if you lower the first number by 1 you are describing the vast majority of employed programmers in the world. |
|
|
|
| ▲ | achenatx 2 hours ago | parent | prev | next [-] |
| when agile was fairly new I worked with remote developers that had 3 locations. My specialty is software requirements and my team was brought in to do the product management. The developers had read somewhere if you were using a database to do requirements then you were doing agile wrong. They wanted me to write post it notes in triplicate, then fedex them to all their offices. |
|
| ▲ | martin_drapeau 4 hours ago | parent | prev [-] |
| In my last jobs Jira was used, and despised by all except product managers. It just becomes a mess.
In my startup (now 20 people), we use Trello. Outsiders look at us funny. I respond that its the same company after all... |
| |
| ▲ | fhub an hour ago | parent | next [-] | | The best task management solution is the one you just moved to as it doesn't have years of junk in it. | |
| ▲ | ExoticPearTree 3 hours ago | parent | prev [-] | | I hate Jira just like any other sane person does. But really, Trello? I found it worse than Jira. /smh |
|
