Scott Logic’s Post

With the increase in low-code and no-code platforms... Here is an overview of low-code and no-code: what these solutions are, examples of platforms that fall under one or the other category, and when to use either for your company.  Link to the full insight to follow below 👇 

We revisit some of our top blog posts from 2023. First up, Isaac Lyman explores some of the potential factors why the quality of software may be getting worse - and what developers can do to build better apps and reduce technical debt in the future. https://lnkd.in/gYYdRpr5

Ever wonder how your program manages to remain tamper-proof and reliable? The digital mark that guarantees the integrity of your apps is called #codesigning. This is a #digitalsignature on a software that confirms the software publisher's #digitalidentity and makes sure the code hasn't been changed after it was signed. Here's how to verify the authenticity of an #electronicsignature - watch our video!

🖥️ Witness the pivotal moments where software met reality—and faltered. Our top article, ‘Code Calamities: A Chronicle of Software Bugs with Dire Consequences’, showcases these critical junctures. Swipe through the photos to see the impact of these infamous software failures. Don’t forget to read the full story at https://lnkd.in/gZ9sZ97v #SoftwareFailures #TechHistory #CodingCaution #DigitalLessonsLearned #InnovationResponsibility”

I was just reminded of Alan Cooper's guidelines for polite software, as outlined in his classic book "The inmates are running the asylum" (good overview here: https://lnkd.in/duPMu-SU). I think I first heard about it in 2008 when Leisa Reichelt gave a talk at an O'Reilly event I was also speaking at in Berlin. I remember getting back to the UK where I was living at the time and immediately purchasing Alan's book. I think it's interesting to revisit these in light of AI powered software, since they always seemed so anthropomorphic to me and AI is still very much prompt driven. To review, polite software: 1. Is interested in you 2. Is deferential to you 3. Is forthcoming 4. Has common sense 5. Anticipates your needs 6. Is responsive 7. Is taciturn about its personal problems 8. Is perceptive 9. Is self-confident 10. Is well informed 11. Stays focused 12. Is fudgeable 13. Gives instant gratification 14. Is trustworthy What do you think?

The Costly Consequences of Rushing Experienced Developers! 😨 Imagine a symphony led by virtuoso musicians 🎵. Now, picture demanding they perform complex compositions in record time ⏱️. It's a recipe for missed notes and discord. Similarly, expecting our seasoned developers to craft intricate software under tight deadlines is like rushing a masterpiece 🖌️. To create reliable, efficient, and future-proof software, we must grant them the gift of time ⏳. Trust in their expertise, and watch them orchestrate software magic that not only meets but exceeds your business needs! 🌟

I find it hard to believe, but it is true: another year has wrapped up. With the conclusion of 2023, I'm looking back at some of my free and open-source software accomplishments over those 12 months. Learn more about what exciting things I've been working on and get some ideas for how you can contribute with bug reports, documentation improvements, and development to the software on which we all depend every day by checking out https://lnkd.in/esxpw347

Why write greedy software? George Melikov will talk about principles of reconciliation loop (hello, k8s!). ⠀ 📋 https://bit.ly/3Vo1sQj ⠀ The world is not ideal - any large system consists of many separate subsystems. We cannot control all of them during development and exploitation at once. And according to Murphy's law, if anything can go wrong, it WILL go wrong. When applied to the creation of distributed systems, this means that absolutely everything may and will break someday. ⠀ And in such conditions, we need to develop software that does not require constant attention from its creator. ⠀ George will speak about the practices and their experience of creating software with self-healing based on the principles of closed loop automation (at last, let's talk about the reasons for the stability of kubernetes), compare it with the event-based approach that is common in the industry, and honestly admit that the employer will have increased resources overhead and spent money at the expense of our good night’s sleep. ⠀ Hope to see you at Tech Internals Conf on April 19 🙌 ⠀ ✅ Visit our website to learn more about the conference and book a ticket - https://bit.ly/49DI321

Last week, my team struggled to deliver new software on time. We already had all the new features already coded. However, we couldn't deliver it. Why? We were not meeting the 80% minimum test code coverage. Honestly, it was very disgusting. At that point, you want to deliver the software without tests... It's the truth. Although, I disagree with that. Tests should cover at least the most critical parts. You will ensure your code works as you want and protect your app's correct functioning against future changes. Also, you will likely find critical bugs while testing. I usually find a few of them when I'm testing my code. So remember... Although sometimes it seems to be an extra effort... Do the tests. You will have a bulletproof code!

Have you offered a new feature for Instantly software yet? 🚀 Reminding you about our newly-launched website, where you can: - Request features, - Give feedback, - Report bugs. Help us shape Instantly into the perfect solution for you ⚡ The link is in the first comment.