<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Rimon Nassory</title>
    <description>The latest articles on DEV Community by Rimon Nassory (@rimonnassory).</description>
    <link>https://dev.to/rimonnassory</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2296575%2F16d393f3-dd91-4cc1-b824-4b902262741e.jpeg</url>
      <title>DEV Community: Rimon Nassory</title>
      <link>https://dev.to/rimonnassory</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rimonnassory"/>
    <language>en</language>
    <item>
      <title>Should Junior Developers Learn to Code Without AI First?</title>
      <dc:creator>Rimon Nassory</dc:creator>
      <pubDate>Fri, 13 Nov 2026 08:31:27 +0000</pubDate>
      <link>https://dev.to/rimonnassory/should-junior-developers-learn-to-code-without-ai-first-111l</link>
      <guid>https://dev.to/rimonnassory/should-junior-developers-learn-to-code-without-ai-first-111l</guid>
      <description>&lt;h1&gt;
  
  
  Should Junior Developers Learn to Code Without AI First?
&lt;/h1&gt;

&lt;p&gt;&lt;em&gt;AI can make developers faster. But are we giving the next generation enough opportunities to learn how software actually works?&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Something That Got Me Thinking
&lt;/h2&gt;

&lt;p&gt;Yesterday, I attended &lt;strong&gt;"AI og Ledelse – Mennesket først"&lt;/strong&gt;, an event hosted by IDA and Mannaz, where we explored AI, leadership, and the importance of keeping humans in the loop.&lt;/p&gt;

&lt;p&gt;There were several interesting perspectives, but one question stayed with me:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How do we make sure the next generation of software developers actually learns to understand code when AI can write most of it for them?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It's something I've been thinking about, especially from a technical leadership perspective.&lt;/p&gt;

&lt;h2&gt;
  
  
  Remember Learning to Code?
&lt;/h2&gt;

&lt;p&gt;When I started my career as a software developer, AI coding assistants weren't an option.&lt;/p&gt;

&lt;p&gt;If something didn't work, you had to figure out why.&lt;/p&gt;

&lt;p&gt;You spent hours debugging, reading documentation, searching Stack Overflow, and occasionally questioning your career choices. 😅&lt;/p&gt;

&lt;p&gt;It wasn't always efficient, but you learned a lot along the way.&lt;/p&gt;

&lt;p&gt;You learned how to investigate problems, understand code, and recognize when something wasn't right.&lt;/p&gt;

&lt;p&gt;Today, a junior developer can ask AI to implement a feature and receive a working solution in seconds.&lt;/p&gt;

&lt;p&gt;That's impressive. But it also raises an important question.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If AI solves the problem before you've struggled with it, what have you actually learned?&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Should We Limit AI for Junior Developers?
&lt;/h2&gt;

&lt;p&gt;Imagine hiring a newly graduated developer.&lt;/p&gt;

&lt;p&gt;During the first few weeks, you want them to understand the codebase, learn the architecture, and develop their problem-solving skills.&lt;/p&gt;

&lt;p&gt;But what happens if they immediately use AI to generate every solution?&lt;/p&gt;

&lt;p&gt;They might complete their tasks faster, but are they developing the skills needed to maintain and troubleshoot the code later?&lt;/p&gt;

&lt;p&gt;I'm not suggesting that juniors shouldn't use AI.&lt;/p&gt;

&lt;p&gt;In fact, I believe learning to work effectively with AI is becoming an important engineering skill.&lt;/p&gt;

&lt;p&gt;But perhaps we need to rethink how we introduce it.&lt;/p&gt;

&lt;p&gt;What if we encouraged junior developers to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;First attempt a solution themselves before asking AI.&lt;/li&gt;
&lt;li&gt;Explain their reasoning and approach.&lt;/li&gt;
&lt;li&gt;Use AI to challenge or review their solutions rather than immediately generate them.&lt;/li&gt;
&lt;li&gt;Understand and explain AI-generated code before accepting it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The goal wouldn't be to slow them down. It would be to help them develop the judgment they'll need throughout their careers.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Human Still Needs to Understand
&lt;/h2&gt;

&lt;p&gt;One of the important themes I took away from the event was the role of humans when working with AI.&lt;/p&gt;

&lt;p&gt;For me, this is particularly relevant to software engineering and Quality Assurance.&lt;/p&gt;

&lt;p&gt;AI can generate code, tests, and even suggest fixes. But someone still needs to understand whether the solution is correct.&lt;/p&gt;

&lt;p&gt;If we become too dependent on AI before developing fundamental engineering skills, how do we recognize when AI makes a mistake?&lt;/p&gt;

&lt;p&gt;A green test doesn't automatically mean the implementation is correct.&lt;/p&gt;

&lt;p&gt;And a working implementation doesn't necessarily mean it's a good solution.&lt;/p&gt;

&lt;p&gt;That's where experience, critical thinking, and technical understanding matter.&lt;/p&gt;

&lt;h2&gt;
  
  
  I'm Curious How Other Teams Handle This
&lt;/h2&gt;

&lt;p&gt;I don't think there's one correct approach.&lt;/p&gt;

&lt;p&gt;Perhaps limiting AI during the first few weeks helps juniors learn the fundamentals. Or perhaps teaching them to use AI responsibly from day one is more effective.&lt;/p&gt;

&lt;p&gt;What I'm particularly interested in is hearing from people who have already tried different approaches.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If you're hiring or mentoring junior developers:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Do you allow unrestricted AI usage from day one?&lt;/li&gt;
&lt;li&gt;Do you encourage juniors to solve problems without AI first?&lt;/li&gt;
&lt;li&gt;How do you ensure they're actually learning instead of simply accepting generated solutions?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I'd love to hear your experiences, especially what's worked and what hasn't.&lt;/p&gt;

&lt;p&gt;Because while AI is changing how we write code, &lt;strong&gt;we still need to develop engineers who understand the code they're responsible for.&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>career</category>
      <category>softwareengineering</category>
      <category>discuss</category>
    </item>
    <item>
      <title>AI Can Write Tests. But Are We Testing the Right Things?</title>
      <dc:creator>Rimon Nassory</dc:creator>
      <pubDate>Thu, 05 Nov 2026 08:19:00 +0000</pubDate>
      <link>https://dev.to/rimonnassory/ai-can-write-tests-but-are-we-testing-the-right-things-27mk</link>
      <guid>https://dev.to/rimonnassory/ai-can-write-tests-but-are-we-testing-the-right-things-27mk</guid>
      <description>&lt;p&gt;&lt;em&gt;AI is changing how we approach software testing. But generating more tests doesn't necessarily mean delivering better software.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  AI Is Making Test Automation Faster
&lt;/h2&gt;

&lt;p&gt;Over the past year, I've been exploring how AI can improve our QA processes, especially when working with Playwright and automated regression testing.&lt;/p&gt;

&lt;p&gt;And one thing is clear: AI can be incredibly helpful.&lt;/p&gt;

&lt;p&gt;It can generate test scenarios, write automation scripts, suggest edge cases, and help investigate failing tests.&lt;/p&gt;

&lt;p&gt;Tasks that previously took hours can sometimes be completed much faster.&lt;/p&gt;

&lt;p&gt;But I've started asking myself an important question:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Are we actually improving software quality, or are we just generating more tests?&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  More Tests Don't Always Mean Better Quality
&lt;/h2&gt;

&lt;p&gt;Imagine asking AI to generate tests for a new feature.&lt;/p&gt;

&lt;p&gt;It produces 20 automated tests. They all pass. CI is green.&lt;/p&gt;

&lt;p&gt;Looks great, right?&lt;/p&gt;

&lt;p&gt;But what if the requirements were incomplete?&lt;/p&gt;

&lt;p&gt;What if an important business rule was never discussed?&lt;/p&gt;

&lt;p&gt;Or what if the AI generated tests based on how the implementation works, rather than how it should work?&lt;/p&gt;

&lt;p&gt;You can end up with a perfectly green test suite that validates the wrong behavior.&lt;/p&gt;

&lt;p&gt;And that's where I believe QA becomes even more important.&lt;/p&gt;

&lt;h2&gt;
  
  
  QA Needs to Be Involved Earlier
&lt;/h2&gt;

&lt;p&gt;Traditionally, QA is often involved when a feature is ready for testing.&lt;/p&gt;

&lt;p&gt;But with AI accelerating development, waiting until the end becomes even more risky.&lt;/p&gt;

&lt;p&gt;If developers can generate working implementations faster, unclear requirements can become working code just as quickly.&lt;/p&gt;

&lt;p&gt;That's why I believe QA should be involved before development begins.&lt;/p&gt;

&lt;p&gt;We need to ask questions like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What is the expected behavior?&lt;/li&gt;
&lt;li&gt;What could go wrong?&lt;/li&gt;
&lt;li&gt;Which edge cases are we missing?&lt;/li&gt;
&lt;li&gt;What are the risks?&lt;/li&gt;
&lt;li&gt;How do we know the feature is actually correct?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Once we understand these things, AI becomes much more powerful.&lt;/p&gt;

&lt;p&gt;Instead of asking AI to guess what needs testing, we can give it clear expectations and let it help us turn them into reliable automated tests.&lt;/p&gt;

&lt;h2&gt;
  
  
  AI Should Support QA, Not Replace Judgment
&lt;/h2&gt;

&lt;p&gt;I'm also interested in concepts such as LLM-as-a-Judge and self-healing tests.&lt;/p&gt;

&lt;p&gt;Both have exciting potential, but they introduce new questions.&lt;/p&gt;

&lt;p&gt;Should an AI automatically fix a failing test?&lt;/p&gt;

&lt;p&gt;How do we know it isn't hiding a real regression?&lt;/p&gt;

&lt;p&gt;And who verifies that an AI-generated test actually checks the correct behavior?&lt;/p&gt;

&lt;p&gt;I believe the answer is a combination of AI assistance, deterministic checks, and human judgment.&lt;/p&gt;

&lt;p&gt;AI can help us work faster, but we still need to understand what we're validating.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;I don't think the future of QA is about writing more automated tests.&lt;/p&gt;

&lt;p&gt;It's about finding better ways to prevent defects, identify risks earlier, and make sure we're building the right things.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;AI can help us test faster. QA must help us test smarter.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I'm curious how other teams are approaching this.&lt;/p&gt;

&lt;p&gt;Are you using AI mainly to generate more tests, or are you also changing how QA is involved in the development process?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>testing</category>
      <category>qa</category>
    </item>
    <item>
      <title>From Software Engineer to QA Team Lead: How Testing Became My Passion</title>
      <dc:creator>Rimon Nassory</dc:creator>
      <pubDate>Sun, 25 Oct 2026 17:30:00 +0000</pubDate>
      <link>https://dev.to/rimonnassory/from-software-engineer-to-qa-team-lead-how-testing-became-my-passion-dja</link>
      <guid>https://dev.to/rimonnassory/from-software-engineer-to-qa-team-lead-how-testing-became-my-passion-dja</guid>
      <description>&lt;p&gt;&lt;em&gt;My journey through software development, entrepreneurship, leadership, and AI-driven automation.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;When I started my career as a software engineer, becoming a QA Team Lead was never part of my plan. I simply loved building software, solving problems, and exploring new technologies.&lt;/p&gt;

&lt;p&gt;But looking back, I can see how curiosity, entrepreneurship, and an increasing interest in automation gradually shaped my career.&lt;/p&gt;

&lt;h2&gt;
  
  
  From Software Development to Entrepreneurship
&lt;/h2&gt;

&lt;p&gt;I started as a mobile developer, building applications for iOS and Android. While I enjoyed writing code, I was always curious about the bigger picture. How do companies make money? How do you turn an idea into a business?&lt;/p&gt;

&lt;p&gt;That curiosity led me to pursue a master's degree in business innovation.&lt;/p&gt;

&lt;p&gt;During my studies, I developed an idea inspired by my experience as a football referee: replacing pen and paper with a smartwatch application to manage match events.&lt;/p&gt;

&lt;p&gt;What started as a university project eventually became a startup. I found myself not only developing software but also negotiating partnerships, understanding customer needs, and making business decisions.&lt;/p&gt;

&lt;p&gt;It taught me something important: &lt;strong&gt;Great software isn't just about technology. It's about solving real problems.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Discovering the Value of Testing
&lt;/h2&gt;

&lt;p&gt;Throughout my development career, I worked on several applications, including mobile apps, smartwatch solutions, and larger web applications.&lt;/p&gt;

&lt;p&gt;Early on, testing wasn't something I fully understood. I wrote some tests, but I didn't appreciate their long-term value.&lt;/p&gt;

&lt;p&gt;That changed as I gained experience building and maintaining real products.&lt;/p&gt;

&lt;p&gt;I started seeing how automated tests could prevent regressions, improve confidence, and make software easier to maintain.&lt;/p&gt;

&lt;p&gt;Eventually, testing became something I actively advocated for.&lt;/p&gt;

&lt;h2&gt;
  
  
  From Tech Lead to QA Leadership
&lt;/h2&gt;

&lt;p&gt;When I became a Frontend Tech Lead, I noticed that automated testing wasn't consistently part of the development process.&lt;/p&gt;

&lt;p&gt;I began introducing unit, component, and integration testing through regular knowledge-sharing sessions with developers.&lt;/p&gt;

&lt;p&gt;My goal wasn't simply to increase the number of tests. It was to build a culture where quality became a natural part of development.&lt;/p&gt;

&lt;p&gt;At the same time, I became increasingly interested in end-to-end automation and the possibilities of AI.&lt;/p&gt;

&lt;p&gt;So when an opportunity to lead a technically focused QA team appeared, it felt like a natural next step.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where AI Meets Quality Engineering
&lt;/h2&gt;

&lt;p&gt;Today, I lead a QA team focused on automation, software quality, and AI.&lt;/p&gt;

&lt;p&gt;One of my recent initiatives has been building a context-aware AI architecture using structured context, skills, rules, and prompts to help transform test cases into automated tests.&lt;/p&gt;

&lt;p&gt;I'm now looking toward self-healing test agents and LLM-as-a-Judge approaches as the next areas to explore.&lt;/p&gt;

&lt;p&gt;The goal isn't to replace engineers, but to help them spend less time on repetitive work and more time improving software quality.&lt;/p&gt;

&lt;h2&gt;
  
  
  Looking Back
&lt;/h2&gt;

&lt;p&gt;If there's one thing my career has taught me, it's that &lt;strong&gt;you don't always need to know exactly where you're heading. Curiosity and a willingness to learn can open unexpected doors.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;My journey from software developer to entrepreneur, technical leader, and QA Team Lead wasn't planned, but each experience helped prepare me for the next.&lt;/p&gt;

&lt;p&gt;Through this blog, I hope to share what I've learned about software engineering, startups, leadership, testing, and AI automation.&lt;/p&gt;

&lt;p&gt;And I'm still learning.&lt;/p&gt;

</description>
      <category>automation</category>
      <category>testing</category>
      <category>leadership</category>
      <category>career</category>
    </item>
  </channel>
</rss>
