Stefan Đokić’s Post

The #1 article from this week's Reasonable AppSec Newsletter is The Economics of Developer Tooling. Better Developer Experience (DX) significantly impacts software quality, capabilities, and cost reduction. It highlights the challenges in improving the toolkit developers use, the long process involved in prototyping solutions, and the need for investment to bridge the gap between academic prototypes and usable tools. [We explored DX and secure by default tools for developers on this week’s Security Table.] Subscribe in the comments!

Restate: Simplifying Distributed Application Development With Lightweight Workflows-As-Code https://lnkd.in/ecGrEdXC #Tech #Startup #Application #Development #Workflows #Microservices

🌟 𝐃𝐢𝐬𝐜𝐨𝐯𝐞𝐫 𝐅𝐚𝐢𝐫𝐏𝐥𝐚𝐲𝐂𝐨𝐦𝐛𝐢𝐧𝐞𝐝: 𝐄𝐦𝐩𝐨𝐰𝐞𝐫𝐢𝐧𝐠 𝐄𝐧𝐭𝐫𝐞𝐩𝐫𝐞𝐧𝐞𝐮𝐫𝐬 𝐰𝐢𝐭𝐡 𝐎𝐩𝐞𝐧-𝐒𝐨𝐮𝐫𝐜𝐞 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧𝐬 🌟 🚀 𝐄𝐱𝐜𝐢𝐭𝐢𝐧𝐠 𝐍𝐞𝐰𝐬 𝐟𝐨𝐫 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐞𝐫𝐬 𝐚𝐧𝐝 𝐄𝐧𝐭𝐫𝐞𝐩𝐫𝐞𝐧𝐞𝐮𝐫𝐬! I'm thrilled to share 𝐅𝐚𝐢𝐫𝐏𝐥𝐚𝐲𝐂𝐨𝐦𝐛𝐢𝐧𝐞𝐝, a comprehensive suite of Open-Source Software Solutions designed to empower entrepreneurs and small businesses in the digital age. Developed with the latest technologies like Blazor, .NET MAUI, Entity Framework Core, Azure, and .NET Aspire, FairPlayCombined brings together multiple innovative solutions under one roof. 🎯 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐅𝐚𝐢𝐫𝐏𝐥𝐚𝐲𝐂𝐨𝐦𝐛𝐢𝐧𝐞𝐝? FairPlayCombined is a powerful integration of various open-source tools aimed at democratizing access to technology. It's designed for entrepreneurs who have faced challenges due to pandemics, economic shifts, or technological disruptions. 🛠️ 𝐅𝐞𝐚𝐭𝐮𝐫𝐞𝐝 𝐒𝐨𝐥𝐮𝐭𝐢𝐨𝐧𝐬: - 𝐅𝐚𝐢𝐫𝐏𝐥𝐚𝐲𝐓𝐮𝐛𝐞: A video sharing platform offering better monetization options for new and small creators. It provides direct monetization through video sales without thresholds, detailed viewing statistics, and tools to create thumbnails, infographics, and more. - 𝐅𝐚𝐢𝐫𝐏𝐥𝐚𝐲𝐃𝐚𝐭𝐢𝐧𝐠: A user-friendly and secure dating app that focuses on enhancing user experience and safety. 🌟 𝐖𝐡𝐚𝐭 𝐢𝐬 .𝐍𝐄𝐓 𝐀𝐬𝐩𝐢𝐫𝐞? .NET Aspire is an advanced framework that enhances productivity and performance in .NET development. It streamlines development processes, reduces code duplication, and integrates seamlessly with modern .NET technologies, providing a robust foundation for building scalable and efficient applications. 🔍 𝐖𝐡𝐲 𝐅𝐚𝐢𝐫𝐏𝐥𝐚𝐲𝐂𝐨𝐦𝐛𝐢𝐧𝐞𝐝? - 𝐎𝐩𝐞𝐧-𝐒𝐨𝐮𝐫𝐜𝐞 & 𝐓𝐫𝐚𝐧𝐬𝐩𝐚𝐫𝐞𝐧𝐭: Access, use, and modify the software freely. - 𝐌𝐨𝐝𝐞𝐫𝐧 𝐓𝐞𝐜𝐡 𝐒𝐭𝐚𝐜𝐤: Built with cutting-edge technologies ensuring high performance and security, including .NET Aspire for enhanced development efficiency. - 𝐄𝐝𝐮𝐜𝐚𝐭𝐢𝐨𝐧𝐚𝐥 & 𝐒𝐮𝐩𝐩𝐨𝐫𝐭𝐢𝐯𝐞: Provides tools and resources to help you start and grow your business. 🌐 𝐆𝐞𝐭 𝐈𝐧𝐯𝐨𝐥𝐯𝐞𝐝: We invite developers, entrepreneurs, and tech enthusiasts to explore, contribute, and collaborate with us on this journey. Together, we can create a more inclusive and supportive tech ecosystem. 👉 𝐂𝐡𝐞𝐜𝐤 𝐨𝐮𝐭 𝐭𝐡𝐞 𝐅𝐚𝐢𝐫𝐏𝐥𝐚𝐲𝐂𝐨𝐦𝐛𝐢𝐧𝐞𝐝 𝐫𝐞𝐩𝐨𝐬𝐢𝐭𝐨𝐫𝐲 𝐨𝐧 𝐆𝐢𝐭𝐇𝐮𝐛: https://lnkd.in/eSrPbTfm 🔗 𝐑𝐞𝐚𝐝 𝐦𝐨𝐫𝐞 𝐚𝐛𝐨𝐮𝐭 𝐭𝐡𝐞 𝐩𝐫𝐨𝐣𝐞𝐜𝐭: https://lnkd.in/eVJqQRS6 Let's build the future of open-source solutions together! 💪 #OpenSource #FairPlayCombined #FairPlayTube #FairPlayDating #TechForGood #Entrepreneurship #Blazor #DotNet #Azure #Aspire #Innovation #Community

Tech considerations after a public launch. A month ago we publicly launched  Plannix. Having such a tight and unavoidable deadline has put a lot of pressure on the development team, and the inclusion of a fourth guy in our dev group has indeed increased the entropy of the moment. Nevertheless, the platform is stable and we managed to ship all the core features that were worth the "promise" of the product. From this crazy intense moment, I isolated 5 takeaways that I feel like sharing: ✅ - Spending an extra day in the design phase saves a week of development  Although it seems trivial and deadly obvious, it is very easy to lose this habit in hectic stages of production where time is running out. It must be held very tightly and the team must recognize the value of design. ✅ - having a common, unambiguous language saves lives A misunderstanding can cost hours of development time. Agreeing on the meaning of words, verbs, and actions that need to occur in the product is crucial, especially when haste takes over and not understanding each other can greatly divert the feature development trajectory. ✅ - resolving conflicts quickly and taking responsibility  A conflict in the team over an implementation detail leads to delays, discussions, and often chatter completely disconnected with the ultimate goal of the feature.  In a product discovery phase, no one knows with certainty, always and 100% where the choices made today will lead. Sometimes (very often, actually) there may be different opinions, solutions, and priorities. At some point, however, the team recognizes that it is going around in circles without actually solving anything, and it is healthy to elect an applied decision owner, tasked with documenting the choices made. ✅ - deploy at most every 2 hours.  Software should always (or almost always) be in a buildable and deployable state, frequent pushes on the branches that operate the CI/CD allows you to speed up the feedback loop and resolve any problems in real time. Realizing after two days that a build fails, perhaps for a development we considered "done," implies a jump back into the context that destroys focus and degrades production performance. 🫀 BONUS 1 - if you can afford it, buy advisor time Having external advisors is a real blessing in our journey, because they know enough about the product to give you good advice but are not operational enough to become blind to the problems and shortcomings of the product. They are worth their weight in gold. 🫀 BONUS 2 - have fun while making mistakes. Making mistakes is human but more importantly it is the basis of development work. If you do not derive joy from this drill, when you are under pressure you will explode badly, ruining the working life of more than one colleague. I hope these little thoughts can help you both in times of crisis and in the "quiet" of ordinary work. 🤔 How about you? What did the last pressure job you had to do teach you? 📸: JESHOOTS.COM su Unsplash

#Opendevin: The Open-Source Version of Devin the Coding Agent #wehavenomoat - the truth of the GenAI era. #Devin the coding agent (demo) blew our minds just a few days ago and we already have #opendevin - https://lnkd.in/eW5kcHve, the open-source version - with over 10k stars and growing fast. It is still a work in progress, but already impressive and supports the same design paradigm: interactive agent console and windows into the agent tools - browser, IDE, and CLI. You can select your own model (including everything on the device), and everything is #opensource. It used to be that #ideasarecheap, but it seems that now #agentsarecheap or maybe even #anythingontopofmodelsischeap. What's the future of companies in this world?! #agents #ai #genai #startups #innovation #langchain

Kubernetes probes: Kubernetes probes are a crucial aspect of ensuring the reliability and responsiveness of applications running in containers. Here are the key points to understand about Kubernetes probes: Liveness Probes Purpose: Liveness probes check if a container is running and responsive. If the probe fails, Kubernetes restarts the container. Types: There are three types of probes: liveness, readiness, and startup. Configuration: Liveness probes are typically configured using the spec.containers.livenessProbe attribute in the pod configuration. They can be set to run HTTP GET requests, TCP socket checks, or execute commands inside the container. Readiness Probes Purpose: Readiness probes check if a container is ready to accept traffic. If the probe fails, Kubernetes will not send traffic to the pod. Types: There are three types of probes: liveness, readiness, and startup. Configuration: Readiness probes are typically configured using the spec.containers.readinessProbe attribute in the pod configuration. They can be set to run HTTP GET requests, TCP socket checks, or execute commands inside the container. Startup Probes Purpose: Startup probes check if a container has started successfully. If the probe fails, Kubernetes will restart the container. Types: There are three types of probes: liveness, readiness, and startup. Configuration: Startup probes are typically configured using the spec.containers.startupProbe attribute in the pod configuration. They can be set to run HTTP GET requests, TCP socket checks, or execute commands inside the container.

⎈ 𝐀 𝐇𝐚𝐧𝐝𝐬-𝐎𝐧 𝐆𝐮𝐢𝐝𝐞 𝐭𝐨 𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬 𝐏𝐫𝐨𝐛𝐞𝐬: 𝐋𝐢𝐯𝐞𝐧𝐞𝐬𝐬, 𝐑𝐞𝐚𝐝𝐢𝐧𝐞𝐬𝐬, 𝐚𝐧𝐝 𝐒𝐭𝐚𝐫𝐭𝐮𝐩 𝐏𝐫𝐨𝐛𝐞𝐬 ⎈ ⇢ 𝙰 𝙶𝚞𝚒𝚍𝚎 𝚝𝚘 𝙴𝚗𝚜𝚞𝚛𝚒𝚗𝚐 𝙲𝚘𝚗𝚝𝚊𝚒𝚗𝚎𝚛 𝙷𝚎𝚊𝚕𝚝𝚑 𝚊𝚗𝚍 𝚁𝚎𝚕𝚒𝚊𝚋𝚒𝚕𝚒𝚝𝚢 𝚒𝚗 𝙺𝚞𝚋𝚎𝚛𝚗𝚎𝚝𝚎𝚜 ⚙️ When it comes to managing container health in Kubernetes, 𝗽𝗿𝗼𝗯𝗲𝘀 are essential tools that keep applications resilient and self-healing. Each type of probe — 𝗟𝗶𝘃𝗲𝗻𝗲𝘀𝘀, 𝗥𝗲𝗮𝗱𝗶𝗻𝗲𝘀𝘀, 𝗮𝗻𝗱 𝗦𝘁𝗮𝗿𝘁𝘂𝗽 —serves a unique role in ensuring applications are healthy, ready for traffic, and capable of recovering from issues on their own. 𝐇𝐞𝐫𝐞’𝐬 𝐚 𝐪𝐮𝐢𝐜𝐤 𝐛𝐫𝐞𝐚𝐤𝐝𝐨𝐰𝐧: 1. 𝐋𝐢𝐯𝐞𝐧𝐞𝐬𝐬 𝐏𝐫𝐨𝐛𝐞 🩺: Detects if a container is "alive." If not, Kubernetes restarts it. 2. 𝗥𝗲𝗮𝗱𝗶𝗻𝗲𝘀𝘀 𝗣𝗿𝗼𝗯𝗲✅: Ensures a container is ready to serve traffic, especially important for apps with dependencies or slow start-ups. 3. 𝗦𝘁𝗮𝗿𝘁𝘂𝗽 𝗣𝗿𝗼𝗯𝗲 ⏳: Great for apps with long startup times. Prevents premature restarts while the container initializes. Setting up probes properly can make a huge difference in maintaining application uptime and reliability. Check out my latest Medium article to dive deeper into Kubernetes probes, see hands-on examples, and learn best practices for using them effectively! 📖 𝐑𝐞𝐚𝐝 𝐭𝐡𝐞 𝐛𝐥𝐨𝐠: https://lnkd.in/gu-McUkD 🚀 𝐒𝐨𝐮𝐫𝐜𝐞 𝐂𝐨𝐝𝐞: https://lnkd.in/gE49_Dwd 𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗪𝗲𝗹𝗰𝗼𝗺𝗲! If you spot any errors, have ideas for improvements please let me know! Drop a comment below or feel free to message me directly. I’d love to hear your thoughts and make this guide as useful as possible for the community.

Je vous partage un article de blog écrit par le co-fondateur de Tailscale, qui est très en phase avec ce que je pense (et ce que j'écris sur mon blog) depuis longtemps. Quelques morceaux choisis : « What we saw was, a lot of things have gotten better since the 1990s. Computers are literally millions of times faster. 100x as many people can be programmers now because they aren’t stuck with just C++ and assembly language. But, also things have gotten worse. A lot of day-to-day things that used to be easy for developers, are now hard. That was unexpected. Instead, the tech industry has evolved into an absolute mess. And it’s getting worse instead of better! Our tower of complexity is now so tall that we seriously consider slathering LLMs on top to write the incomprehensible code in the incomprehensible frameworks so we don’t have to. I read a post recently where someone bragged about using kubernetes to scale all the way up to 500,000 page views per month. But that’s 0.2 requests per second. I could serve that from my phone, on battery power, and it would spend most of its time asleep. In modern computing, we tolerate long builds, and then docker builds, and uploading to container stores, and multi-minute deploy times before the program runs, and even longer times before the log output gets uploaded to somewhere you can see it, all because we’ve been tricked into this idea that everything has to scale. People get excited about deploying to the latest upstart container hosting service because it only takes tens of seconds to roll out, instead of minutes. But on my slow computer in the 1990s, I could run a perl or python program that started in milliseconds and served way more than 0.2 requests per second, and printed logs to stderr right away so I could edit-run-debug over and over again, multiple times per minute. As an industry, we’ve spent all our time making the hard things possible, and none of our time making the easy things easy. Modern software development is mostly junky overhead. »

Why Low Code is one of the best things happening right now (2/2) Overcoming Low-Code Perceived Limitations Critics of Low-Code often point to potential limitations in scalability, flexibility, and the complexity of problems it can solve. However, the technology is evolving, and modern Low-Code platforms are proving to be more robust than their early renditions. Scalability and Customization Initial Low-Code platforms often produced apps that were not easily scalable or customizable for complex business needs. But with growing market demand, providers are ensuring that their platforms can handle complex applications that grow alongside the business. Integration with Legacy Systems Legacy systems are the pillars of many enterprises, and the concern for their integration with new software created via Low-Code is valid. However, contemporary platforms are becoming more adept at working within the ecosystem of existing software. Changing the Future of Software Development What does this  Low-Code movement mean for the future of software development? It signifies a world where creating your own software might become as commonplace as customizing an off-the-shelf application today. There are 2 major benefits: The Democratization of Software Creation With Low-Code, we are witnessing the democratization of software creation. Citizen developers and IT professionals alike can participate in the construction of digital ecosystems through visualization and logic, without being hampered by the intricacies of traditional programming languages. Evolution Not Disruption Low-Code platforms are not set to disrupt the software industry but rather to augment it. They present an alternative, quicker, and more intuitive way to build certain types of applications. Conclusion In the big, colorful world of software creation, Low-Code is the newest vibe, representing progress and change. Not every app out there is going to be a perfect match for Low-Code, but you can really feel its impact. It's all about using abstraction to remix how we create in the digital era. For anyone into tech, business analysis, or IT management, it's a hint to get flexible, try new things, and innovate as we explore this exciting new territory. #lowcode #automation #innovation #technology