[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"topics":3,"posts:technology::2:6:":62,"$fmAbo7HX1697lOJ4AVNBJl1PR7wUF0IkR_62krtbwQAE":183},{"data":4,"meta":59},[5,15,23,31,40,50],{"_id":6,"name":7,"description":8,"image":9,"imageAlt":10,"slug":11,"createdAt":12,"updatedAt":13,"uuid":14},"6a92c7892f7e20762f654f94","AI","Posts on AI in real product and engineering work: building AI-powered tools, using large language models for SEO and data platforms, and honest takes on where AI actually helps versus where it's overhyped.","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnewsai-2.jpg","AI flying to you!","ai","Sat Aug 29 2026 19:50:33 GMT+0800 (Singapore Standard Time)","Sat Aug 29 2026 20:18:46 GMT+0800 (Singapore Standard Time)","6f2f7079-c45c-4d74-b758-5419dd8755ee",{"_id":16,"name":17,"description":18,"image":19,"imageAlt":19,"slug":20,"createdAt":21,"updatedAt":21,"uuid":22},"6a92d5d26d3bae502260bcb4","CTO Show by TechVibe","Notes from the CTO seat - security, compliance, vendor relationships, build-vs-buy decisions, and the less glamorous parts of leading engineering that rarely make it into the highlight reel. All things given to Support TechVibe team.","","cto-show-by-techvibe","Sat Aug 29 2026 20:51:30 GMT+0800 (Singapore Standard Time)","afaf2020-622a-4b9c-961a-2e36d936230b",{"_id":24,"name":25,"description":26,"image":27,"imageAlt":19,"slug":28,"createdAt":29,"updatedAt":29,"uuid":30},"6a92d6156d3bae502260bcd3","Good Reads","Books Michal has actually read and would recommend to engineers and engineering leaders - from technical classics like Designing Data-Intensive Applications to leadership reads like Staff Engineer.","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnews\u002Fagainst.jpg","good-reads","Sat Aug 29 2026 20:52:37 GMT+0800 (Singapore Standard Time)","a9f75c75-c1b9-4637-b7ee-592babde3aae",{"_id":32,"name":33,"description":34,"image":35,"imageAlt":10,"slug":36,"createdAt":37,"updatedAt":38,"uuid":39},"6a92d78c6d3bae502260bdc3","Technology","A running log of tools, frameworks, and technical decisions Michal has actually used and formed opinions on - from React and Tauri to DevOps culture, database architecture, and API tooling.","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnewscity.mp4","technology","Sat Aug 29 2026 20:58:52 GMT+0800 (Singapore Standard Time)","Sat Aug 29 2026 21:03:33 GMT+0800 (Singapore Standard Time)","b9d2bf10-b22e-4afa-b778-2bb49d12a884",{"_id":41,"name":42,"description":43,"image":44,"imageAlt":45,"slug":46,"createdAt":47,"updatedAt":48,"uuid":49},"6a92dace6d3bae502260c000","CTO work","Notes from the CTO seat - security, compliance, vendor relationships, build-vs-buy decisions, and the less glamorous parts of leading engineering that rarely make it into the highlight reel. Plus bit of utopia in the topic image. ","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnewscto.jpg","CTO of the Future","cto-work","Sat Aug 29 2026 21:12:46 GMT+0800 (Singapore Standard Time)","Sat Aug 29 2026 21:13:06 GMT+0800 (Singapore Standard Time)","89273ffa-05fb-4e6d-bc6b-21fa593d4c8e",{"_id":51,"name":52,"description":53,"image":54,"imageAlt":55,"slug":56,"createdAt":57,"updatedAt":57,"uuid":58},"6a9373be6d3bae5022611315","DIY","Michal's own side projects and builds - desktop setup evolutions, Ace the chatbot, and small apps built for the fun of solving a real problem.","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnewsdiy.jpg","Do it yourself","diy","Sun Aug 30 2026 08:05:18 GMT+0800 (Singapore Standard Time)","ac6dffb6-41ee-41b0-8819-fed9ac1d26ca",{"totalnoOfItems":60,"perPage":61,"noOfItemsOnCurrentPage":60},6,24,{"data":63,"meta":181},[64,88,109,129,147,164],{"_id":65,"tags":66,"id":68,"title":69,"alt":70,"category":71,"categorySlug":72,"date":73,"author":74,"readTime":75,"content":76,"image":77,"more":78,"extendedContent":79,"asHTML":78,"headTitle":80,"metaDesc":81,"photoCredit":82,"createdAt":83,"updatedAt":84,"uuid":85,"__v":86,"relatedTools":87},"66d7acbf4dd49115f4a20baa",[33,17,67],"Vietnam","cto-show-podcast-a-growing-success-story","CTO Show Podcast: A Growing Success Story","CTO Show main banner","Side Project","side-project","2024-09-04T00:35:00.000Z","Michal",30,"In just under a month since our first release, the CTO Show has gained over 2,000 subscribers, and each episode is attracting more than 1,000 views. Beyond the numbers, the feedback has been overwhelmingly positive, with messages of support coming not only from friends but also from people I’ve never met before. Thank you to everyone who has tuned in and shared their thoughts. The journey has just begun, and I’m excited for what’s next!","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnews\u002Fctoshow_banner.jpg","true","\u003Cdiv style=\"width: 100%; min-width: 400px; max-width: 1200px; margin-top:30px\">\n\u003Cdiv style=\"position: relative; width: 100%; overflow: hidden; padding-top: 56.25%;\">\n\u003Cp>\u003Ciframe style=\"position: absolute; top: 0; left: 0; right: 0; width: 100%; height: 100%; border: none;\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FRJwcgcus8Tw?si=u5daQEZH4tYb4sKn\" title=\"YouTube video player\" allowfullscreen=\"allowfullscreen\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen>\u003C\u002Fiframe>\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\n","CTO Show by TechVibe after one month from first release","Join the CTO Show's growing community with over 2,000 subscribers and 1,000 views per episode. Positive feedback is pouring in - thank you for your support!","CTO Show","Wed Sep 04 2024 08:41:35 GMT+0800 (Singapore Standard Time)","Fri Sep 04 2026 16:49:50 GMT+0800 (Singapore Standard Time)","10824a84-7da2-4041-a047-54478e6a20a7",2,[],{"relatedTools":89,"_id":90,"id":91,"title":92,"alt":93,"category":94,"date":95,"author":74,"readTime":96,"content":97,"image":98,"more":78,"extendedContent":99,"asHTML":78,"headTitle":100,"metaDesc":101,"createdAt":102,"updatedAt":103,"uuid":104,"__v":105,"photoCredit":106,"categorySlug":107,"tags":108},[],"6541b43dbb58b50f1016e7d2","devops-is-a-culture-not-a-role","DevOps is a culture, not a role.","DevOps Infinity Illustration. ","Articles","2023-11-01T02:10:00.000Z",5,"In the world of software development and IT operations, there is a buzzword that seems to be on everyone's lips: DevOps. But what exactly is DevOps? Is it just another job title or a trendy concept? The truth is, DevOps is much more than that. It is a culture that has revolutionized the way organizations build, deploy, and operate software systems. ","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnews\u002Fdev-ops-inifinty.png","\u003Ch2 id=\"2\">Understanding the Concept of DevOps\u003C\u002Fh2>\u003Cp>DevOps, short for Development and Operations, emerged from the need to bridge the gap between software developers and IT operations teams. It aims to establish a collaborative and efficient environment where continuous integration and deployment are possible. But where did this culture shift originate?\u003C\u002Fp>\u003Cp>In order to fully grasp the concept of DevOps, it is important to delve into its origins and understand the driving forces behind its creation.\u003C\u002Fp>\u003Ch3 id=\"3\">The Origins of DevOps\u003C\u002Fh3>\u003Cp>The roots of DevOps can be traced back to the Agile software development movement, which emphasized iterative development and collaboration between cross-functional teams. Agile methodologies revolutionized the software development process by promoting flexibility, adaptability, and customer-centricity.\u003C\u002Fp>\u003Cp>As Agile methodologies gained popularity, developers realized that traditional siloed operations were hindering the speed and quality of software delivery. The lack of communication and collaboration between development and operations teams resulted in bottlenecks, delays, and inefficiencies.\u003C\u002Fp>\u003Cp>This realization paved the way for the birth of DevOps. DevOps emerged as a response to the challenges faced by organizations in delivering software at a faster pace without compromising quality.\u003C\u002Fp>\u003Ch3 id=\"4\">Defining DevOps: More Than Just a Job Title\u003C\u002Fh3>\u003Cp>DevOps is not just a fancy job title. It represents a paradigm shift in the way organizations approach software development and delivery. It breaks down the barriers between developers, operations, and other stakeholders, fostering a culture of collaboration, shared responsibility, and continuous improvement.\u003C\u002Fp>\u003Cp>DevOps is not about a specific role or job description; it is about cultivating a mindset that promotes efficiency, reliability, and innovation. It encourages teams to work together, leveraging automation, continuous integration, and continuous delivery practices to streamline the software development lifecycle.\u003C\u002Fp>\u003Cp>By embracing DevOps principles, organizations can achieve faster time-to-market, improved software quality, and enhanced customer satisfaction. The focus shifts from individual tasks and responsibilities to collective ownership and accountability.\u003C\u002Fp>\u003Cp>Furthermore, DevOps encourages the adoption of infrastructure as code, enabling teams to treat infrastructure provisioning and management as software development. This approach brings agility, scalability, and repeatability to the infrastructure, reducing manual errors and minimizing downtime.\u003C\u002Fp>\u003Cp>DevOps also emphasizes the importance of monitoring and feedback loops. By continuously monitoring the performance and behavior of applications in production, teams can identify and address issues proactively, ensuring optimal performance and user experience.\u003C\u002Fp>\u003Cp>In conclusion, DevOps is a transformative approach that goes beyond the boundaries of traditional software development and operations. It fosters collaboration, automation, and continuous improvement, enabling organizations to deliver software faster, more reliably, and with higher quality.\u003C\u002Fp>\u003Ch3 id=\"5\">The Cultural Shift Towards DevOps\u003C\u002Fh3>\u003Cp>One of the fundamental aspects of DevOps lies in its focus on collaboration. In a DevOps-driven culture, the entire software development lifecycle is collaborative, starting from the planning stage, all the way to deployment and beyond.\u003C\u002Fp>\u003Cp>Collaboration is the heart and soul of DevOps. It brings together teams with different expertise, skills, and perspectives to work towards a common goal. Developers and operations personnel collaborate closely, breaking down the communication barriers that often lead to inefficiencies and delays. By fostering collaboration, organizations can take full advantage of collective intelligence, which is crucial for achieving faster and higher-quality software delivery.\u003C\u002Fp>\u003Cp>Moreover, collaboration in DevOps extends beyond just developers and operations personnel. It involves the active participation of other stakeholders such as quality assurance teams, security experts, and business analysts. This holistic approach ensures that all aspects of software development and delivery are taken into account, resulting in a more comprehensive and robust final product.\u003C\u002Fp>\u003Cp>In addition to collaboration, DevOps also emphasizes continuous integration and continuous delivery (CI\u002FCD). This means that software changes are integrated and tested frequently, allowing for rapid feedback and iteration. By automating the build, test, and deployment processes, organizations can significantly reduce the time it takes to deliver new features or bug fixes to end-users.\u003C\u002Fp>\u003Ch3 id=\"6\">The Importance of Collaboration in DevOps\u003C\u002Fh3>\u003Cp>Collaboration is not just a buzzword in DevOps; it is a critical factor that drives success. When teams collaborate effectively, they can share knowledge, identify and address issues early on, and make informed decisions together. This level of collaboration leads to improved efficiency, reduced rework, and ultimately, faster time-to-market.\u003C\u002Fp>\u003Cp>Furthermore, collaboration in DevOps fosters a culture of learning and continuous improvement. By working together, team members can learn from each other's experiences, share best practices, and collectively evolve their skills and processes. This constant learning cycle ensures that the organization stays adaptable and can quickly respond to changing market demands.\u003C\u002Fp>\u003Ch3 id=\"7\">Breaking Down Silos: The DevOps Approach\u003C\u002Fh3>\u003Cp>In traditional IT organizations, different teams often operate in isolation, with limited interaction and coordination. This siloed approach can lead to miscommunication, misunderstandings, and a lack of alignment between developers and operations personnel. DevOps seeks to break down these silos by promoting cross-functional teams that work together throughout the entire software development and delivery process.\u003C\u002Fp>\u003Cp>By tearing down these barriers, organizations can cultivate a culture of shared responsibility, where everyone strives for a common goal. Developers, operations personnel, and other stakeholders collaborate seamlessly, leveraging each other's strengths and expertise. This integrated approach ensures that software development and delivery are not hindered by departmental boundaries or conflicting priorities.\u003C\u002Fp>\u003Cp>Moreover, breaking down silos also enables organizations to adopt a more agile and iterative approach to software development. Instead of waiting for lengthy handoffs between teams, DevOps encourages continuous collaboration and feedback. This allows for faster identification and resolution of issues, reducing the overall time and effort required to deliver high-quality software.\u003C\u002Fp>\u003Cp>In conclusion, the cultural shift towards DevOps is driven by the recognition that collaboration is essential for successful software development and delivery. By embracing collaboration, organizations can harness the collective intelligence of their teams, break down silos, and achieve faster, higher-quality software delivery. The DevOps approach not only improves efficiency and productivity but also fosters a culture of learning and continuous improvement, ensuring long-term success in today's fast-paced and competitive digital landscape.\u003C\u002Fp>\u003Ch3 id=\"8\">Key Principles of DevOps Culture\u003C\u002Fh3>\u003Cp>DevOps is guided by a set of key principles that shape its culture and practices. These principles are crucial in fostering collaboration, efficiency, and reliability within organizations.\u003C\u002Fp>\u003Cp>One of the key principles of DevOps is Continuous Integration and Continuous Delivery (CI\u002FCD). CI\u002FCD is at the core of DevOps, and it involves continuously integrating code changes, running automated tests, and deploying software to production environments. This practice enhances collaboration between development and operations teams, reduces development cycle time, and ensures that every code change is validated and ready for deployment. By implementing CI\u002FCD pipelines, organizations can deliver software updates to end-users quickly and efficiently, ensuring a seamless user experience.\u003C\u002Fp>\u003Cp>Another essential aspect of DevOps culture is Infrastructure as Code (IaC). Infrastructure as Code involves managing infrastructure and configuration through code, enabling organizations to automate the provisioning, deployment, and monitoring of their infrastructure. By treating infrastructure as code, organizations can achieve consistency, scalability, and traceability in their deployments. This approach reduces the risk of human errors and makes deployments more reliable. With IaC, organizations can easily replicate and scale their infrastructure, ensuring that their systems can handle increased workloads and demands.\u003C\u002Fp>\u003Cp>DevOps also emphasizes the importance of collaboration and communication between different teams involved in the software development lifecycle. By breaking down silos and fostering cross-functional collaboration, organizations can streamline processes, reduce bottlenecks, and improve overall efficiency. Through effective communication, teams can align their goals, share knowledge, and address any challenges or issues that may arise during the development and deployment process.\u003C\u002Fp>\u003Cp>Automation is another key principle of DevOps culture. By automating repetitive and manual tasks, organizations can save time, reduce errors, and improve overall productivity. Automation allows teams to focus on more strategic and value-added activities, such as innovation and problem-solving. Additionally, automation enables organizations to achieve consistent and predictable results, reducing the risk of human errors and ensuring that deployments are carried out smoothly.\u003C\u002Fp>\u003Cp>Furthermore, DevOps encourages a culture of continuous learning and improvement. By embracing a growth mindset and fostering a learning culture, organizations can adapt to changing market demands and technologies. Continuous learning enables teams to stay updated with the latest industry trends, acquire new skills, and improve existing processes. Through regular retrospectives and feedback loops, organizations can identify areas for improvement and implement changes to enhance their development and deployment practices.\u003C\u002Fp>\u003Cp>In conclusion, DevOps culture is built upon key principles such as Continuous Integration and Continuous Delivery, Infrastructure as Code, collaboration and communication, automation, and continuous learning. By embracing these principles, organizations can achieve faster and more reliable software delivery, improved collaboration between teams, and a culture of continuous improvement.\u003C\u002Fp>\u003Ch3 id=\"9\">The Role of Automation in DevOps Culture\u003C\u002Fh3>\u003Cp>Automation plays a pivotal role in driving efficiency, reliability, and repeatability within DevOps culture.\u003C\u002Fp>\u003Ch3 id=\"10\">The Significance of Automation Tools\u003C\u002Fh3>\u003Cp>Automation tools automate manual processes, eliminating the need for human assistance in routine and repetitive tasks. These tools streamline software delivery pipelines, facilitate faster feedback loops, and reduce the likelihood of human error. Automation enables organizations to achieve higher efficiency by freeing up valuable human resources to focus on more complex and critical tasks.\u003C\u002Fp>\u003Ch3 id=\"11\">How Automation Enhances Efficiency\u003C\u002Fh3>\u003Cp>Through automation, organizations can increase efficiency by reducing lead time, minimizing manual interventions, and ensuring consistent and repeatable processes. Automated testing eliminates time-consuming and error-prone manual tests, enabling faster and more frequent software releases. Automation also allows for proactive monitoring and alerts, identifying issues before they escalate and significantly reducing downtime. Ultimately, automation empowers organizations to maximize productivity and deliver high-quality software at a faster pace.\u003C\u002Fp>\u003Ch3 id=\"12\">Challenges in Adopting DevOps Culture\u003C\u002Fh3>\u003Cp>While DevOps offers numerous benefits, adopting this culture is not without its challenges. Organizations often face resistance to change and the need to address security concerns.\u003C\u002Fp>\u003Ch3 id=\"13\">Overcoming Resistance to Change\u003C\u002Fh3>\u003Cp>Implementing DevOps requires a significant cultural shift, which can encounter resistance from both technical and non-technical team members. Cultural transformation requires buy-in from stakeholders at all levels, including senior management. Clear communication, training, and demonstrating the tangible benefits of DevOps can help overcome resistance and foster a culture of continuous improvement and innovation.\u003C\u002Fp>\u003Ch3 id=\"14\">Ensuring Security in a DevOps Environment\u003C\u002Fh3>\u003Cp>Security is a critical aspect of any software system. In a DevOps environment, where speed and agility are paramount, it is crucial to address security concerns. Organizations must embed security practices throughout the software development lifecycle, adopt security testing tools, and prioritize security education and awareness. By implementing security as a shared responsibility, organizations can strike a balance between speed and security.\u003C\u002Fp>\u003Cp>In conclusion, DevOps is not just a role; it is a culture that transcends job titles and transforms the way organizations build, deploy, and operate software systems. By embracing collaboration, continuous integration, automation, and overcoming challenges, organizations can unlock the immense potential of DevOps, leading to faster, more reliable software delivery and a competitive advantage in the dynamic world of technology.\u003C\u002Fp>","What really DevOps is. ","DevOps is a culture revolutionizing how orgs build, deploy & operate software systems. It's more than just a job title or concept: it's an entire movement! ","Wed Nov 01 2023 10:13:17 GMT+0800 (Singapore Standard Time)","Mon Dec 04 2023 19:40:12 GMT+0800 (Singapore Standard Time)","7e56a404-76bf-4b14-a960-2b36495aba0a",1,"Will Porada | Unsplash","articles",[42,33],{"relatedTools":110,"_id":111,"id":112,"title":113,"alt":114,"category":115,"date":116,"author":74,"readTime":86,"content":117,"image":118,"more":78,"extendedContent":119,"asHTML":78,"headTitle":120,"metaDesc":121,"photoCredit":122,"createdAt":123,"updatedAt":124,"uuid":125,"__v":126,"categorySlug":127,"tags":128},[],"65387aebbb58b50f1016e7d0","navigating-the-vendor-relationship-the-importance-of-mutual-respect","Navigating the Vendor Relationship: The Importance of Mutual Respect.","handshake","Thought","2023-10-25T02:14:00.000Z","I just dropped a new text that spills the beans on nailing those vendor relationships. Let me share why respect and openness are the keys to successful business partnerships. In this fast-moving market, it's all about staying ahead of the curve. ","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnews\u002Fhand-shake.jpg","\u003Ch2>Navigating tech consulting challenges with third parties.\u003C\u002Fh2>\n\u003Cp>In my journey working with various vendors, I've come to appreciate the significance of respecting our business partners. However, recently, I've encountered disappointment with some companies I've had long-standing relationships with. It appears that they may have taken my positive attitude towards their offerings for granted, assuming that they can maintain their profitability without staying competitive. When new potential leads are presented with more enticing packages, superior service, and increased engagement, it seems these vendors believe that their past goodwill will guarantee their place in my business.\u003C\u002Fp>\n\u003Cp>Unfortunately for them, my loyalty isn't set in stone. I continuously explore new opportunities and evaluate alternative offers. I'm not complacent, and I exercise common sense in making decisions. If necessary, I am willing to put in the effort to switch vendors.\u003C\u002Fp>\n\u003Cp>This situation raises some important questions: Why do these vendors seem to take my loyalty for granted? Is it their belief that I'm too reluctant to seek other options? Or do they consider special terms as investments that will eventually pay off? Even if this is the case, why not be transparent and honest about their intentions, rather than hoping that I remain oblivious to the ever-evolving market dynamics?\u003C\u002Fp>\n\u003Cp>In any successful business relationship, mutual respect and transparency are key. Both parties should value each other's contributions and communicate openly to maintain a healthy, long-term partnership. It's a reminder that, as business partners, we should never underestimate the importance of respect, fairness, and staying competitive in the constantly evolving marketplace.\u003C\u002Fp>\n","Managing vendor relationships can be challenging.","This post reveals how to build successful business partnerships through respect and openness. Stay ahead of the curve in this fast-moving market!","Austin Kehmeier \u002F Unsplash","Wed Oct 25 2023 10:18:19 GMT+0800 (Singapore Standard Time)","Sat Aug 29 2026 09:29:34 GMT+0800 (Singapore Standard Time)","09a9c14c-5236-4590-a4d5-c7bde68b64bc",3,"thought",[42,33],{"relatedTools":130,"_id":131,"id":132,"title":133,"alt":134,"category":115,"date":135,"author":74,"readTime":86,"content":136,"image":137,"more":78,"extendedContent":138,"asHTML":78,"headTitle":139,"metaDesc":140,"photoCredit":141,"draft":142,"createdAt":143,"updatedAt":144,"uuid":145,"__v":105,"categorySlug":127,"tags":146},[],"646ec00cf32e94034de8c974","is-tauri-a-electron-killer","Is Tauri an Electron killer?","tauri website","2023-05-25T01:45:00.000Z","ElectronJS-powered applications are ubiquitous; Slack, Visual Studio Code, Figma, Discord, Postman and countless others. My teams have released several projects using this technology, and it certainly works - albeit with a few minor but irksome bumps along the way. Releasing a project with Electron as opposed to Chromium often required a few days of extra effort just to make it stable. Therefore, when Tauri began gaining traction, I decided to give it a shot.","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnews\u002Ftauri.jpg","\u003Ch2>My first experiences with \u003Ca href=\"https:\u002F\u002Ftauri.app\" target=\"_blank\" rel=\"noopener\">Tauri\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>I was absolutely astounded to discover that I could compile my first Tauri OSX build, including a dmg package, in only 10 minutes from the time I first landed on their website! It was fast and stable too – truly remarkable.\u003Cbr> The documentation was incredibly helpful; even as an 'old timer', I could comprehend it!\u003Cbr> What's more, the bundle size was incredibly small; my entire app was compressed into just 4MB, instead of the hundreds of MBs required by Electron. I was equally impressed when I saw how easy it is to add Rust functions to a frontend project. This opens up the potential for significant speed enhancements.\u003C\u002Fp>\n\u003Cp>All in all, it's evident that Electron may have met its match. For me, this is like a bullet whizzing through the air!\u003C\u002Fp>","Is Tauri an Electron killer? Read why!","ElectronJS-powered apps are everywhere; Slack, VS Code, Figma, Discord & more. Tauri gained traction so I decided to give it a shot.","Tauri website","false","Thu May 25 2023 09:55:24 GMT+0800 (Singapore Standard Time)","Mon Dec 04 2023 19:43:24 GMT+0800 (Singapore Standard Time)","0a2edb01-9acc-491c-8bc6-e804c9de83bc",[33],{"relatedTools":148,"_id":149,"id":150,"title":151,"alt":152,"category":115,"date":153,"author":74,"readTime":126,"content":154,"image":155,"more":78,"extendedContent":156,"asHTML":78,"headTitle":157,"metaDesc":158,"photoCredit":159,"draft":19,"createdAt":160,"updatedAt":161,"uuid":162,"__v":105,"categorySlug":127,"tags":163},[],"64646e67f32e94034de8c96f","my-thoughts-on-github-copilot","My thoughts on Github Copilot.","Github Copilot creature in space","2023-05-17T06:02:00.000Z","I've been using Copilot in my main editor for several months now, and rarely press Tab to accept its suggestions. This usually only happens when I type descriptions, not code. Anyways, I found it helpful, but risky. Let's take a closer look at why.","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnews\u002Fcopilot.jpg","\u003Ch2>GitHub Copilot? I'm open, but it is not there yet.\u003C\u002Fh2>\nAs an AI enthusiast, I foresee a future where the majority of \"coding jobs\" will involve guiding engines to do the heavy lifting, changing programming into prompting! 🚀\u003Cbr>\u003Cbr>\n\nHowever, my experience with Github Copilot as my \"pair programmer\" left much to be desired. Some of its suggestions were way off the mark, not in terms of language syntax but in terms of adding real value. It sometimes created a tangled mess of code, resembling a bowl of spaghetti! 🍝\u003Cbr>\u003Cbr>\n\nCompared to simpler online versions of chat-GPT (and models trained on specific content), Copilot's prompting capabilities fell short. It didn't reduce my need to search for documentation or check Stack Overflow. However, I did find it quite useful for straightforward and repetitive tasks. It excelled at generating switch blocks with predefined options or typing out descriptions in plain English. Those were smooth sailing! ⛵️\u003Cbr>\u003Cbr>\n\nBut let's be real, Copilot didn't make the cut for me. It lacked the bigger picture thinking that proposes a solution instead of working inline. It was too easy to fall into the trap of WET code (opposite of DRY - Do Not Repeat Yourself). Sure, it's tempting to hit that Tab key, but it often leads to wasting time for code review. I prefer being in control when it comes to deciding when proposed code blocks popups to accept or escape. ⏸️\u003Cbr>\u003Cbr>\n\nThat being said, I believe GitHub Copilot shows promise as a feature. Perhaps the recently announced Copilot-X will be the breakthrough we've been waiting for. Only time will tell! ✨","My thoughts after using Github Copilot","Github Copilot is a AI backed editor tool that should save time by providing code suggestions. Does it really help? Check my pov. #editor #writing #programming","Unsplash","Wed May 17 2023 14:04:23 GMT+0800 (Singapore Standard Time)","Mon Dec 04 2023 19:43:38 GMT+0800 (Singapore Standard Time)","32477a57-00bf-4fa4-aa8b-f6183c0d753a",[33],{"relatedTools":165,"_id":166,"id":167,"title":168,"alt":169,"category":115,"date":170,"author":74,"readTime":126,"content":171,"image":172,"more":78,"extendedContent":173,"asHTML":78,"createdAt":174,"updatedAt":175,"__v":105,"uuid":176,"photoCredit":177,"headTitle":178,"metaDesc":179,"categorySlug":127,"tags":180},[],"640eec2840ef91034d1a6a57","is-react-a-dead-end-path","Is ReactJS a dead-end path?","ReactJS is a dead end","2023-03-12T16:00:00.000Z","React is like a modern celebrity - famous simply for being famous. It's often chosen as a safe solution, and no one can fault you for that. However, once you dive deeper, you'll be exposed to all its flaws. I predict that React will die out just as PHP did in the realm of HTML templating.","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnews\u002F\u002Fdeadendreact.jpg","\u003Ch2>React JS? No thank you, I'll go for modern frameworks.\u003C\u002Fh2>\nI honestly believe working with ReactJS is a messy experience compared to other modern FE frameworks. It can be summarised as a waste of time. An extreme opinion? Allow me to share some arguments here. Let's start with a basic example, on a newbie level. To write a react functional (modern) component, containing just two input fields that are dynamically changing the line of text, you need that:\n\u003Cpre>\nimport React, { useState } from 'react';\n\nexport default () => {\n    const [a, setA] = useState(1);\n    const [b, setB] = useState(2);\n\n    function handleChangeA(event) {\n        setA(+event.target.value);\n    }\n\n    function handleChangeB(event) {\n        setB(+event.target.value);\n    }\n\n    return (\n        <div>\n            <input type="number" value={a} onChange={handleChangeA}\u002F>\n            <input type="number" value={b} onChange={handleChangeB}\u002F>\n\n            <p>{a} + {b} = {a + b}<\u002Fp>\n        <\u002Fdiv>\n    );\n};\n\u003C\u002Fpre>\nIn VueJS, it will be simpler:\n\u003Cpre>\n<template>\n    <div>\n        <input type="number" v-model.number="a">\n        <input type="number" v-model.number="b">\n\n        <p>{{a}} + {{b}} = {{a + b}}<\u002Fp>\n    <\u002Fdiv>\n<\u002Ftemplate>\n\n<script>\n    export default {\n        data: function() {\n            return {\n                a: 1,\n                b: 2\n            };\n        }\n    };\n<\u002Fscript>\n\u003C\u002Fpre>\nIn Svelte (which you should be using if not doing it yet):\n\u003Cpre>\n<script>\n\tlet a = 1;\n\tlet b = 2;\n<\u002Fscript>\n\n<input type="number" bind:value={a}>\n<input type="number" bind:value={b}>\n\n<p>{a} + {b} = {a + b}<\u002Fp>\n\u003C\u002Fpre>\nWow, React requires so much more code!\u003Cbr>\nBut let's talk about the next step on the learning curve. To get the knack of Redux, a state container commonly used with React, you're happy if you start now. With Redux-Toolkit it is quite straightforward. Unfortunately, your more experienced colleagues have used tones of different ways of doing it, including famous Redux-Saga or Thunk. What an effort needed to catch-up and be quick with all of that spaghetti. Please understand my point here, I'm not saying those libraries are bad, in fact some of them are brilliant. The problem is the entire mashed-up ecosystem, which costs you a lot of learning. In practice, the average developer has only 2-4 years of experience and is not productive in that environment. She\u002FHe consumes time paid by the employer to learn.\u003Cbr>\nThere are more surprises when you dig deeper. React is not written with Typescript but with Flow (Facebook attempts to make JS with type support). TS is added 'on top' by an external team. Which ends with unexpected results (check \u003Ca href=\"https:\u002F\u002Fwww.totaltypescript.com\u002Fyoutube\u002FM3TPmOpNFCs\" target=\"_new\">this\u003C\u002Fa>).\u003Cbr>\u003Cbr>\nI believe moving to simpler and cleaner frameworks is the path forward. They were created with all the experience gained while React was the leading edge. If you think about potential cons, there are only two, less documentation (examples) on the web, and the risk of those projects being abandoned.\u003Cbr\u002F>\n\nAs a last word, React is slow. Very slow.\u003Cbr>\u003Cbr>\n\n","Mon Mar 13 2023 17:26:00 GMT+0800 (Singapore Standard Time)","Mon Dec 04 2023 19:46:14 GMT+0800 (Singapore Standard Time)","7d1e57c7-9e26-4beb-a77e-d7da6ae109f5","Unsplash\u002FMichal","ReactJS has no future?","React is like a modern celebrity, famous for being famous. Dive deeper and you'll find its flaws. Its future? Just like PHP in HTML templating: dead.",[33],{"totalnoOfPosts":182,"page":86,"perPage":60,"noOfPostOnCurrentPage":60},13,{"enabled":184},true]