Comments by "" (@brownhorsesoftware3605) on "Continuous Delivery" channel.

Thank you for a super excellent video. I had the incredible luck to learn programming in assembler on mainframes where the complexity is not as hidden as in higher level languages. So my "normal" is probably more comfortable with asynchronous programming than most. Then I went on to write program debuggers which is all about asynchronous event handling. So when I wrote a phone app with an async messaging interface, I was not surprised at how well it performs - what had not occurred to me was how easy it is to debug. Since every interaction is encapsulated into a message, all you need to do is save a copy of the message stream and you have an excellent map to guide your bug hunt. Hours upon hours saved because the need to go back and try to reproduce a problem is eliminated. I have spent dozens of years fixing bugs in other people's code and usually the hardest most time-consuming bit is figuring out how to reproduce the problem and narrowing down the culprit code. I handled the shared data modification complexity by having all updates handled on a single device. Also important to make each message atomic and delivery order agnostic because Firebase messaging does not guarantee ordering. In the few cases where there was too much data for a single message, the incoming queue is used to sort that out. Long story short- I've gone from being tolerant of async interfaces to becoming a full blown fan.
1
@mecanuktutorials6476 I totally disagree. Building incrementally creates robust code because it is constantly run and tested. The software grows organically. There is never a need for tape of any kind.
1
Why would anyone choose a waterfall as the metaphor for project management? You start on a smooth river then things get dangerous when you hit the rapids until suddenly you are flung over the edge and smashed to pieces.
1
Did you contact them and report the bug?
1
My learning points are continuous. You could say I practice Continuous Learning. Even when learning that something is not new!
1
Excellent video! Make haste with deliberation.
1
You might like to know the rest of this quote. It is "A good rider is never in a hurry. Make haste with deliberation. " The source is my riding mentor and the advice is on how to jump a stadium course. It's a timed event but if you go too fast the horse will jump flat and knock down rails and you won't make tight turns. So you walk the course, plan your route, and then try to convince your horse to execute the plan. Not so different from writing software.
1
On this topic https://youtu.be/jAHRbFetqII
1
Programs are one or more plot lines. Data is organization. Code is focus and plot. Software exists in time like music - it is serial. Speaking for myself, being an English lit major who is wicked good at math and music from a family of engineers is an excellent background for a software engineer. 😉
1
🌟 🌟 🌟 🌟 🌟 🤩
1
Use a queue.
1
Tools and languages don't write buggy code, people do.
1
Thank you for another great thought-provoking video! My career has been defined by the great team or two I have managed to be a part of. Something even more important than sharing top skills within a team is how they have your back. That is what transforms a group into a team. Also, I'd like to point out that people who work on mobile phone software have a term for a phone that does not connect to anything: it is called a brick. I have (mostly) worked remotely since 1991 when I was told to do so after an acquisition landed me in a cubicle in a huge open sales office where phonecalls were announced over the intercom and the colleague seated next to me spent all day talking on the phone to his mother in Russian. Every few minutes a plaintive "Ma-ma!" My productivity went through the roof. After that, except for a few years after an employer was destroyed in the twin towers, I worked for companies with an office on the other side of a continent or an ocean or the planet. One makes adjustments for the time difference but most of the time we simply communicated through code. The occasional email as needed and a weekly stand-up where everyone has 90 second max to give an update. But this can only work when there is a high level of both trust and safety.
1
I'd say the myth is just another artifact of testosterone poisoning. I am convinced that my success in software is based on listening skills. That is all you need to frame a good question. Some people do like to work on their own but for me the joy comes from the effect my software has on people. Knocking around ideas would come in second. The small iteration, reponse, and variation method is how you train a horse - and also how they train you.
1
I always start with the UI which keeps you on a track of making the fewest assumptions as well as additional insight into the functional design. The initial design is the simplest list of the tasks the software needs to accomplish which grows as you work on (code and run) the software. You always build on what works so writing test code is superfluous. The backend can evolve independently and your backend bugs are immediately visible. I don't know if my process has a name. 😀 Your video has inspired me to formulate something I just took for granted.
1
@mx-hx I did not say that testing is superfluous, I said writing test code is superfluous. That is because the production code IS the test code. On the contrary, the code gets more testing because you always run the final code, not a generated test based on a possibly false assumption.
1
Why are we wasting a huge amount of energy and effort to evolve a car into the thing it replaced? How about putting these resources into humanity instead of burning the planet in order to evolve a dog and a pony? Why not put some thought into our actions. That this decision lies in so few hands is my greatest concern.
1
Everything on a phone is event-driven. I think that fact and the complete absence of msft are why I like to work in that space so much. This comes up against a strong bias amongst developers favoring the command model. My experience on Android is their urge to 'simplify' things by hiding event interaction in the platform. All that does is add cycles and create thread production mayhem. I don't know this because I use these features, I know this by observing what gets deprecated. By taking advantage of the event architecture, I have never had a performance problem.
1
Writing is revision.
1
@pluto7562 How does one woman's observation make other women invisible?
1
ChatGPT is not a trusted source. It has no concept of truth. It is simply the most likely next word.
1
@MK-lh3xd Actually, after implementing a second next generation of the ATM system, I had five years of a successful PC software business doing the projects that in-house departments turned away. I developed an excellent phone manner and found physical proximity not to be an issue. It all went well until the economy tanked and project funding dried up. In those 5 years I did 30 projects with only one failure (my single attempt at RPG III).
1
@MK-lh3xd I cannot help but wonder whether you would be astonished to learn that a more appropriate response would have been "You go girl!"
1
@ContinuousDelivery I would characterize it as a con on top of being hype. I have seen too much fraud in the industry to think any other way. And whatever you consider the consensus it is pretty clear that the climate does not care. Between AI and crypto the consequences will only become more dire.
1
When the only tool in your toolbox is a hammer, everything looks like a nail. When your only software tool is a browser, everything looks like a website. I was around in the early Netscape days when I worked on the Symantec JIT. They were one of our customers and once sent me the browser source for testing on a jaz drive. Too big to transmit in the 90's. But that was real Java...
1
@edgeeffect Thanks, you prove my point.
1
@EtienneSavardz Thanks for the info! I have a BA in English so there is no gray area for me. :)
1
@markhathaway9456 The story of my life.
1
Please stop leaving out the COST of AI while you are trying so hard to make it useful for something, anything. The inputs to AI are not just prompts - the energy it uses is massive not to mention the human toll in job loss.
1
@microcolonel ha ha ha 😂 🤣 😆 😄 😅 😜 😂 🤣
1
@metalalive2006 Loyalty can still exist in small companies. But corporate management and loyalty are like fish and bicycles - they don't operate in the same space.
1
Where you say "positive" I'd say "delusional". The very first thing I learned on this job is that defensive code/design is robust and therefore both resilient and reliable. Error handling is job one. I have too many stories of stupid, easily foreseen disasters to recount.
1
I liked this video even before you began speaking based solely on your t shirt. Otherwise excellent video as well.
1
❤ 😍 💖 ❣ 💕 💘 ❤ 🌟 🤩 ⭐ 🌠 💫 🌃 🌟 Best video so far.
1
Our feature phone platform had an installable component service-based architecture in order to cover a wide range of target phone capabilities. Before iPhone.
1
@RicardoSilvaTripcall I think it is an illustration of one difference between what is required for success as a harpist vs what is required for success as a programmer.
1
@niuniuch But you must write the test before you write what you are testing. And if you write the production code before the test it is no longer TDD...
1
Coding is not accounting.
1
 @qj0n Regression tests test only for regressions, not correctness. Compliance or conformance tests test for correctness.
1
@qj0n Your memory is quite different from mine. In my experience CS has had a different standing in the industry: "Those who cannot do, teach".
1
🌟 🌟 🌟 🌟 🌟
1
Excellent video! Getting in trouble for taking a different, simpler and ultimately wildly successful approach is the story of my career. Dogma is the enemy of innovation. One question: where does the concept that ideas are equal arise from agility? It isn't something I came across when I worked for an actual agile company.
1
@ContinuousDelivery First OOP is generally believed to be Simula in the 60's in Oslo. O.J. Dahl and Kristen Nygaard
1
@ContinuousDelivery What is the fuzzy part of the origin?
1
@ContinuousDelivery My history bias is mostly ignorance- I am a programmer of vast experience but little computer science education and rely on my university educated colleagues for historical questions. So I probably have a Norwegian bias after a decade as the only American developer in an Oslo based company. 😀 As far as the first computer - I'd say it was older and fuzzy with origins in programmable looms. Why do you think most of the earliest people doing programming were women? Concept-wise it would go back to Ada Lovelace.
1
Perhaps we should tax AI vendors for work (as we humans are taxed) at a rate based on the magnitude at which they accelerate human work or, better yet, carbon footprint. Tax income will provide a universal basic income for displaced workers.
1
I did the Java MIDP implementation on a feature phone platform where the UX was FP (an in-house Scheme variant) and the backend was OOP (C++).
1