Software developement explained with cars

Author
Kamikaze
Max Output Level: -45 dBFS
  • Total Posts : 3013
  • Joined: 2015/01/15 21:38:59
  • Location: Da Nang, Vietnam
  • Status: offline
2016/02/13 22:35:47 (permalink)

Software developement explained with cars

I've read some of these terms mentioned in discussions about cakewalk development over the years. They still mean little to me, but others may appreciate this more.
http://kuvaton.com/kuvei/...xplained_with_cars.jpg


 
#1

7 Replies Related Threads

    craigb
    Max Output Level: 0 dBFS
    • Total Posts : 41704
    • Joined: 2009/01/28 23:13:04
    • Location: The Pacific Northwestshire
    • Status: offline
    Re: Software developement explained with cars 2016/02/14 00:12:41 (permalink)
    I used to be the guy by the stove, but I knew even stranger languages so I'm now the guy at the bottom on the right... 

     
    Time for all of you to head over to Beyond My DAW!
    #2
    KenB123
    Max Output Level: -66 dBFS
    • Total Posts : 1229
    • Joined: 2006/08/16 12:02:50
    • Location: Illinois, U.S.A.
    • Status: offline
    Re: Software developement explained with cars 2016/02/15 09:24:42 (permalink)
    Dang. What made you post this? It is an almost like an omen.
     
    My place of employment has been moving in these directions over the past few years. A lot of it makes sense and looks great on paper. Lean is essentially making your work flow more efficient. Evaluate the process and correct inefficiencies. Nothing wrong with that. Kanban I have not yet heard about (yet, I am sure). As of this year though, I was assigned to a full-blown AGILE-SCRUM based project. It is a shock to the system. Daily progress status meetings. Half-day sessions sitting in a room with the team of project owners, managers, testers, etc.. In addition, special story-grooming sessions. It is all new to me. I believe these are management tools. Management loves being able to closely monitor status and progress. It breaks projects into smaller chunks of success/failure.  Again, great on paper. Great in concept. Great for management. Even developers can't necessarily argue with the concept. Where I have concern though is in the actual implementation of the process. For developers use to having there 'own' time for actual development, now have much less independence. I am adapting, but still have my concerns about successfully adapting. Maybe thiese concepts need a decade or two to become the 'norm'. Start the fresh graduates in this system and it will become the status quo.
    post edited by KenB123 - 2016/02/15 09:39:15

    Broken pencils are pointless.

    WIN-7 64-bit; Sonar X2A 64-bit; 12GB RAM; ASUS P6T Deluxe V2 MB; Intel Core i7-960; 300GB-OS (10000-RPM); 1TB-Projects (7200-RPM); 1TB-Samples (7200-RPM) 


    #3
    bapu
    Max Output Level: 0 dBFS
    • Total Posts : 86000
    • Joined: 2006/11/25 21:23:28
    • Location: Thousand Oaks, CA
    • Status: offline
    Re: Software developement explained with cars 2016/02/15 13:17:29 (permalink)
    Ken,
     
    AGILE-SCRUM has been around for well over 10 years now.
     
    Not sure they are the "norm' yet.
     
    As you say, 'great on paper' but like any methodology it takes the whole team to get behind it and developers (IME) are least likely to adapt to change quickly (much less overnight)
    #4
    TheMaartian
    Max Output Level: -47.5 dBFS
    • Total Posts : 2774
    • Joined: 2015/05/21 18:30:52
    • Location: Flagstaff, AZ
    • Status: offline
    Re: Software developement explained with cars 2016/02/15 14:45:31 (permalink)
    KenB123
    Dang. What made you post this? It is an almost like an omen.
     
    My place of employment has been moving in these directions over the past few years. A lot of it makes sense and looks great on paper. Lean is essentially making your work flow more efficient. Evaluate the process and correct inefficiencies. Nothing wrong with that. Kanban I have not yet heard about (yet, I am sure). As of this year though, I was assigned to a full-blown AGILE-SCRUM based project. It is a shock to the system. Daily progress status meetings. Half-day sessions sitting in a room with the team of project owners, managers, testers, etc.. In addition, special story-grooming sessions. It is all new to me. I believe these are management tools. Management loves being able to closely monitor status and progress. It breaks projects into smaller chunks of success/failure.  Again, great on paper. Great in concept. Great for management. Even developers can't necessarily argue with the concept. Where I have concern though is in the actual implementation of the process. For developers use to having there 'own' time for actual development, now have much less independence. I am adapting, but still have my concerns about successfully adapting. Maybe thiese concepts need a decade or two to become the 'norm'. Start the fresh graduates in this system and it will become the status quo.


    Sorry, guys. I can't let this one pass without comment.
     
    My last real job before I get laid off by a once-great company (starts with an 'M' and has a batwing logo) was Director of Strategic Quality and Director of Six Sigma, reporting to the president of 'M' University, where we housed our consulting business.
     
    I was the first to be sent packing. Why? Because I wasn't a team player. I didn't go along with the way they were packaging and selling Six Sigma. They wanted to be like the big Six (then it was Five; now it's Four), running programs and projects and selling lots of consulting hours.
     
    Well, if your goal is to generate maximum revenue with no regard for the eventual (maybe) and long-term (almost never) success of a given client with your program, then their way was just fine.
     
    My experience taught that only those firms whose leadership team (C-suite and the one- and two-downs) not only went first, but walked the talk, and then created projects that were directly linked to their own success, would find long-term business success.
     
    And as the inventor of Six Sigma and the face of 'M' to the external market, it seemed to me that I had the responsibility to lead by example. That rubbed several 'M' execs the wrong way, so they banished me to Asia and Europe, where I wound up spending 200+ nights/year in hotel rooms and many, many nights sleeping on airplanes.
     
    Where I wound up doing $7.5MM/year vs. what the entire remainder of the team accomplished in the Americas ($5.5MM).
     
    That REALLY p'd off those same execs.
     
    Then I fired a $2.5MM client (big Euro pharma company) for ethics reasons.
     
    Then I got called back to Chicago and laid off.
     
    Every single one of my clients was abandoned and hung out to dry.
     
    I am SOOOOOOOOOOO glad to be retired.
    post edited by TheMaartian - 2016/02/15 17:22:55

    Intel i7 3.4GHz, 16 GB RAM, 2 TB HD Win10 Home 64-bit Tascam US-16x08
    Studio One 4 Pro NotionMelodyne 4 Studio Acoustica 7 Guitar Pro 7
    PreSonus FaderPort Nektar P6 M-Audio BX8 D2 Beyerdynamic DT 880 Pro
    NI K9U XLN AK, AD2 AAS VS-2, GS-2, VA-2, EP-4, CP-2, OD Toontrack SD3, EZK
    #5
    craigb
    Max Output Level: 0 dBFS
    • Total Posts : 41704
    • Joined: 2009/01/28 23:13:04
    • Location: The Pacific Northwestshire
    • Status: offline
    Re: Software developement explained with cars 2016/02/15 17:17:28 (permalink)
    As a life-long programmer (and occasional project lead or tech. lead), it's my observation that if you're constantly being interrupted to provide a status on work that you never seem to be given the time to actually DO, then there's a problem with either management, the process or both.
     
    I did a small project with Intel.  Just a friend of mine and I, real techie stuff ($125 / hour type work).  Only twice over the 45+ days did we have to go to one of their meetings and, at one, one of their programmers attached his laptop to the overhead projector.  The first thing to be shown was his Outlook calendar which we couldn't help but notice had 5.5 to 6 hours of meetings scheduled EVERY DAY!  For a programmer???  We heard several comments from Intel that they couldn't believe how much work my friend and I got done.  Well, it was obvious.  We both worked from our homes and weren't interrupted.
     
    By the way, all of you that have Intel motherboards with at least four cores have some of my software that came with it! 

     
    Time for all of you to head over to Beyond My DAW!
    #6
    TheMaartian
    Max Output Level: -47.5 dBFS
    • Total Posts : 2774
    • Joined: 2015/05/21 18:30:52
    • Location: Flagstaff, AZ
    • Status: offline
    Re: Software developement explained with cars 2016/02/15 17:25:21 (permalink)
    craigb
    ... 
    By the way, all of you that have Intel motherboards with at least four cores have some of my software that came with it! 

    THAT explains why I could never get an iLok to run reliably on my Wintel computer. 

    Intel i7 3.4GHz, 16 GB RAM, 2 TB HD Win10 Home 64-bit Tascam US-16x08
    Studio One 4 Pro NotionMelodyne 4 Studio Acoustica 7 Guitar Pro 7
    PreSonus FaderPort Nektar P6 M-Audio BX8 D2 Beyerdynamic DT 880 Pro
    NI K9U XLN AK, AD2 AAS VS-2, GS-2, VA-2, EP-4, CP-2, OD Toontrack SD3, EZK
    #7
    craigb
    Max Output Level: 0 dBFS
    • Total Posts : 41704
    • Joined: 2009/01/28 23:13:04
    • Location: The Pacific Northwestshire
    • Status: offline
    Re: Software developement explained with cars 2016/02/15 17:36:02 (permalink)
    We pre-designed confusing issues based on specific user profiles.  
     
    My favorite is to randomly throughout the year create a shortcut in the Startup area that causes a reboot*.  After a few cycles (also random), we remove the shortcut.  
     
    * shutdown -s -t 5 -c For reasons we can't tell you, we're going to reboot your machine!

     
    Time for all of you to head over to Beyond My DAW!
    #8
    Jump to:
    © 2025 APG vNext Commercial Version 5.1