Youtube hearted comments of (@brownhorsesoftware3605).

  1. Excellent stuff!! I learned to code by refactoring all the systems I was put in charge of. Operations loved me as everything I took over stopped having problems.
    20
  2. ❤ Complexity is something that software engineers, scientists, and artists all wrestle with. All of them work by experimentation. It is the nature of creativity in any field. Lovely and very interesting video!
    12
  3. Excellent! Only one thing to add: read lots of code. You can learn piles from both good and bad code and you will get some insight into what it means for code to be readable.
    11
  4. Thanks for another super video. I'm beginning to think that the most important thing to learn as a programmer is how your brain works. My brain does not go to solutions when someone describes a problem, instead it goes into a kind of absorb mode that generates questions. Later, when I pick up a pen, it goes into thinking on paper (graph preferred) to describe, organize, and begin having ideas about the problem. That generates a list of things to explore and research. It is only as this stage progresses that I begin to formulate possible solutions. I always do the easiest things first. Start with something that runs and build from there so you implement what is needed as you need it. Make notes on what is needed as you go. Things you learn on the easy stuff will probably make the hard stuff simpler. Through the entire process I think on paper so I can check things off and remember where I am. I don't think in code, I think on paper - probably due to decades of working in assembler. I do, however, dream in code and rely on sleep to find complicated bugs. When I type code my brain goes into an edit/organize mode quite distinct from the writing with a pen creative mode. Some academic study discovered better exam outcomes for students when taking hand-written notes vs typing on a laptop.
    11
  5. Thanks very much for this exceptional video! It resonates in so many ways. The principles behind agile go back much further than the 20 years. It explains how I as a single person could compete with entire dev departments when I had PC app business in the 80's by working directly with the people in the user department every step of the way. I think the first thing that determines whether an org is truly agile is trust. The second is a sense of humor
    10
  6. Five stars for this video. Excellent discussion on several topics close to my heart. Great to hear backend folks emphasizing user experience and supporting async architecture.
    9
  7. Based on the comments, men appear to believe they know more about gender bias than women. Why even bother commenting at all if everything is so wonderfully gender-balanced in the IT community? In my 45 years working as a programmer bias against women has gone from bad to worse. Of course now I also have age working against me. I mostly had better luck with colleagues from other continents than Americans. There is a wide range based on culture. Thank you for raising this topic.
    6
  8. The difference between functional and oo programming is point of view. In functional programming code is data. In oo programming data is code. This from the point of view of someone who's native language is assembler. All points of view are useful in the right context. Arguing that one is better than the other simply misses the point. Thanks for another great thought-provoking video!!
    6
  9. In this case you simply implement an event that is generated when the state is as A is interested in. Then A just registers a listener for that event. NO POLLING! Polling is the opposite of event driven.
    4
  10. I had the incredible luck to learn programming in a shop that practiced something very close to what you describe as Continuous Delivery down to having a group devoted to what is now called DevOps. A decade before I started in the 70s, they worked with IBM to create CICS and maintained an in-house version called Pronto. I learned to write code for distributed systems by fixing production bugs and rewriting parts that suffered from the entropy of earlier misguided fixes. The data was distributed over time, not space. We were the electric utility for Chicago and surrounding suburbs. The customer dataset was so large that it took a week of nightly runs to process the entire thing and everything happened in cycles of various lengths. Anyway, I just wanted to point out that CD is a great but not necessarily new idea.
    4
  11. On the subject of shiny things: back in the early 80's when I was working in banking writing ATM networks an MBA decided to program a weekly business accounts summary in APL. He showed the auditor how to run the program which took hours to run and brought the mainframe to its knees. I could not watch this so I wrote the report in a scripting language and gave it to operations to run every week. The auditor was eternally grateful. The MBA took me across the hall into the bank vault and balled me out for being unprofessional.
    4
  12. Wow! Too many things to chime in on. Great talk! Count me in as a grumpy old gal who also agrees with everything. I was an English major lucky enough to start programming in the 70's when an interview consisted of the IBM programmer aptitude test. Then you had to pass all the exams during the first three months of working through the IBM self-taught assembler course. I remember asking a colleague during training about this language called assembler. I had heard of COBOL and Fortran but not assembler. Will it be useful to learn? Don't worry about that, he replied. It will definitely be useful.
    4
  13. 🌟 🌟 🌟 🌟 🌟 🤩
    3
  14. Thanks for yet another interesting, informative, and thought-provoking video. It made me think about my experience with teams and experts. The best and most successful teams I've worked on were small and everyone was an expert. If there was something outside our expertise we learned it or added another person as needed. I've also been an expert passed around to other teams. My experience with that was no good deed goes unpunished. It was also a path to burnout: the product would ship and everyone goes on vacation except the expert who is needed for some other project. I usually felt more like a software cleaning lady than an expert.
    3
  15.  @andreaszetterstrom7418  Event structure requires thought like anything else. You need to create a rational model to have a comprehensible result.
    3
  16. 🌟 🤩 ⭐ 🌠 💫 ✡ 🌟 Dave squared equals violent agreement! I had to watch twice so I could look up abbreviations. Excellent and enjoyable. Note from a harpist: the conductor is waiting for the orchestra's attention.
    3
  17. My synopsis of yet another very fine video: Strive to write code that is both readable and robust.
    3
  18. Very excellent video! Makes me want to work for Spotify.
    2
  19. When did enterprise devs stop being responsible for their work? When I started and worked on mainframes EVERYTHING ran in the middle of the night. If the job that was your responsibility crashed, you got in your car and drove in to fix it because other jobs were waiting and operations had to get all the output printed before a certain time. I became famous among the ops folk for refactoring away problems in programs that crashed. It was a tricky environment because it took a week to process the entire customer base. And lots of things happened on cycles of different lengths. I worked for Chicago's (and suburbs) electric utility. Same thing when I worked for a banking data center. I left that in favor of writing custom PC applications in the mid-80s. So when did things change?
    2
  20. Thanks for another excellent video! You are singing my tune. The basis of good design is making no assumptions. Always testing for and handling failure is the key to robust code. That is what queues are for...
    2
  21. The future is now. I've implemented an entirely message-based logistics phone app using Firebase messaging. No database just distributed JSON graphs. My data tool is a text editor. It is totally flexible and ridiculously easy to debug. The time it took to implement was due to the complexity and bugs in the Android life cycle, not the data architecture. The only bit in the cloud is an endpoint to pipe the messages to Firebase.
    2
  22. Excellent video. I wish I had had it to show to all the managers who ignored my warnings about these very things and gave me major flack when I pushed back.
    1
  23. My learning points are continuous. You could say I practice Continuous Learning. Even when learning that something is not new!
    1
  24. Excellent video! Make haste with deliberation.
    1
  25. ❤ 😍 💖 ❣ 💕 💘 ❤ 🌟 🤩 ⭐ 🌠 💫 🌃 🌟 Best video so far.
    1
  26. 🌟 🌟 🌟 🌟 🌟
    1