| General > General Technical Chat |
| Digi-Key has changed and it is not very good |
| << < (30/85) > >> |
| VooDust:
--- Quote from: james_s on October 27, 2020, 07:44:56 pm ---Get used to it. One of the mantras you hear floating around in most agile shops is something along the lines of "move fast and break stuff", they advocate frequent changes and pushing everything to the bleeding edge, don't worry about bugs, we'll fix that "later" when customers start to complain about it. --- End quote --- I'm a SW dev and I hate this mantra so much. It's the reason why for over 2 years I can't get a reliable connection between my apps and my TV. Every 2 weeks something else is breaking. Yet the HW stays the same. Go figure... It's just another way of saying "I have never worked on something that was truly critical or of any significance to life or death whatsoever". The worst part is that the rest of the industry tries to mimic these big players even when it doesn't make any f* sense. |
| tooki:
Yep. And then there’s Agile (the formal methodology) and “agile” (the “oh cool! We can cast these methodology shackles off and just do whatever and justify it as ‘agile’!” methodology). And I hazard that probably half of places adopting agile are the latter, and the other half think they’re doing the former, but in practice are doing the latter anyway... |
| james_s:
--- Quote from: tooki on October 28, 2020, 09:18:10 pm ---Yep. And then there’s Agile (the formal methodology) and “agile” (the “oh cool! We can cast these methodology shackles off and just do whatever and justify it as ‘agile’!” methodology). And I hazard that probably half of places adopting agile are the latter, and the other half think they’re doing the former, but in practice are doing the latter anyway... --- End quote --- That's exactly it. I've worked in multiple orgs that moved to "agile" and in every case it was adopt a bunch of rituals like daily standups, sprint planning and retrospective meetings, throw out all of the specs and documentation, get rid of most or all of the real QA and just start coding. There is this push to break down tasks into smaller and smaller bite sized chunks which creates an illusion of progress as work is steadily going in, and micromanagers love the pretty graphs and charts, following the burndown rate and other stats. Reality is that the process creates a tremendous amount of overhead, larger tasks that are difficult to break down into little bite sized chunks just never actually get done, and it doesn't take long before people are (sometimes unconsciously) massaging things to make the graphs look nice. Invariably in my experience product quality suffers. Frequent updates are touted as something good, that customers always have the latest and greatest. All it really means is that customers are now on the bleeding edge caught in a perpetual beta and are now a substantial part of the QA team. |
| Bud:
Sounds like Altium pretty much. |
| gnavigator1007:
Drinking a beer now because digikey just logged me off and lost all the odds and ends in my cart. 3rd time something like this has happened recently on digikey |O The thing is that most of what I'm ordering was already thru other distributors just so I could minimise the hassle of dealing with the digikey site. What I had in the cart were equivalents of out of stock items from the other distributors. |
| Navigation |
| Message Index |
| Next page |
| Previous page |