Difference between revisions of "Developers"

From Wiki at Neela Nurseries
Jump to navigation Jump to search
(Add Iomico 2026 Zephyr course exam link)
m (Zephyr intermediate course study resources and schedule)
 
(2 intermediate revisions by the same user not shown)
Line 80: Line 80:
  
 
********* ********* ********* ********* ********* ********* ********* ********* ********* ********* -
 
********* ********* ********* ********* ********* ********* ********* ********* ********* ********* -
 +
-->
 +
 +
== Zephyr Meetups ==
 +
<!--
 +
<pre>
 +
Dawid Marszalkiewicz  [2:33 AM]
 +
Hi Team! I was at Zephyr Project Meetup. I did some notes, mostly on AI agents working in Zephyr environment. Hope you find them useful
 +
 +
First presentation AI-aided coding - The speaker claimed that he doesn't write code anymore. He just creates the architecture and a set of requirements that his agents/sub-agents shall follow. He claimed that he recently built a product in 3 months and did not write a single line. Below are a few insights from the presentation.
 +
Vibecoding is an antipattern
 +
Vibecoding has been depicted as looking for a path without a map.
 +
 +
LLMs are very sensitive to context rot - the response quality of an AI model decreases during long conversations or work sessions. There are mechanisms to limit the context size and increase the quality of the AI model's work (even make its output deterministic). In fact, hitting half of the maximum context capacity makes the model generate garbage (his opinion). Below are some ideas on how to limit the context.
 +
Skills - md files describing how to do particular things - e.g. write a specification, write tests, etc. The thing is that skills are not loaded into the context if they are not used.
 +
Agents/Subagents - agents have their own context, which means that they are not polluting the "main" context.
 +
Use MCPs and LSP (like clangd), as curl/grep uses more tokens than MCP/LSP integrations.
 +
 +
What to do when working with AI (based on Claude Code) - tips:
 +
If you are not content with the output, talk it through and plan actions to avoid doing the same thing again - in other words, find the root cause and plan corrective actions.
 +
Set a proper set of permissions so Claude does not need to ask for permission each time - better flow.
 +
Use /compact "prompt describing what should be kept from the session"
 +
Use plugins - one that is very good according to him is superpowers (a framework for software development).
 +
TDD works pretty well with AI models, as they can validate their outcome.
 +
Describe/document as much as you can, e.g.: how to build the project, how to test it, etc.
 +
git worktree allows a multiagent cohort to work on many branches at the same time.
 +
You just need to review it afterwards.
 +
 +
The second presentation was about the RPi Pico 2 ($7 devkit) that can help you with prototyping any communication protocol thanks to its on-board wifi chip and special PIO (programmable I/O) that can be programmed to be UART/SPI/I2C - as I understood.
 +
The last one was about the UART API - Polling/Interrupt/Async. Demo + performance analysis.
 +
(edited)
 +
</pre>
 +
-->
 +
 +
Intermediate Course
 +
 +
<!--
 +
*  https://iomico.thinkific.com/users/sign_in
 +
 +
1 https://iomico.thinkific.com/courses/take/zephyr-intermediate-course/texts/77193524-welcome
 +
 +
- https://www.geeksforgeeks.org/c/c-pointers/
 +
 +
- https://gcc.gnu.org/onlinedocs/cpp/Macros.html
 +
 +
- https://www.tutorialspoint.com/cprogramming/c_structures.htm
 +
 +
- https://www.digitalocean.com/community/tutorials/linux-commands
 +
 +
- https://cmake.org/cmake/help/latest/guide/tutorial/index.html
 +
 +
- https://www.atlassian.com/git/tutorials
 +
 +
- https://sourceware.org/gdb/documentation/
 +
 +
- https://www.freertos.org/Documentation/01-FreeRTOS-quick-start/01-Beginners-guide/01-RTOS-fundamentals
 +
 +
- https://www.learn.iomico.com/courses/iomico-zephyr-course-2026
 +
 +
2 https://iomico.thinkific.com/courses/take/zephyr-intermediate-course/texts/77031601-schedule
 +
 +
```
 +
Course Schedule
 +
 +
Week / Dates
 +
 +
Activities
 +
 +
Aug 5
 +
 +
Course Kick-off / Orientation
 +
 +
Aug 6 – Aug 12
 +
 +
Module 1: Kernel and Scheduling
 +
 +
Aug 13 – Aug 19
 +
 +
Module 2: Synchronization and Shared-State Safety
 +
 +
Aug 19
 +
 +
Live Meeting 1
 +
 +
Aug 20 – Aug 26
 +
 +
Module 3: Deferred Execution and Execution Flow
 +
 +
Aug 27 – Sept 2
 +
 +
Module 4: Communication and Event-Driven Architecture
 +
 +
Sept 2
 +
 +
Live Meeting 2
 +
 +
Sept 3 – Sept 9
 +
 +
Midterm Assessment (Modules 1–4)
 +
 +
Sept 10 – Sept 16
 +
 +
Module 5: Memory, Resource Constraints and Reliability
 +
 +
Sept 17 – Sept 23
 +
 +
Module 6: Tracing, Debugging and Runtime Analysis
 +
 +
Sept 23
 +
 +
Live Meeting 3
 +
 +
Sept 30
 +
 +
Module 7: Security (Live Meeting)
 +
 +
Oct 7
 +
 +
Module 8: Unit Testing Intermediate (Live Meeting)
 +
 +
Oct 8 – Oct 14
 +
 +
Final Assessment
 +
 +
Nov 2 – Nov 6
 +
 +
Final Certificates Issued
 +
 +
Live Meeting Schedule:
 +
Biweekly on Wednesdays at 8:00 PM CET / 3:00 PM Buenos Aires / 2:00 PM EST.
 +
 +
Note:
 +
All live meetings will be recorded and made available for replay. Each module includes a practical hands-on assignment that participants should complete before the corresponding live session to maximize discussion and learning during the meeting.
 +
```
 +
 
-->
 
-->
  
 
<!-- EOF -->
 
<!-- EOF -->

Latest revision as of 03:31, 6 August 2026

Embedded and Software Developers

This page started to hold onto links to interesting works and developers writing about these works.


Zephyr RTOS Project contributors:


Zephyr Meetups

Intermediate Course


Retrieved from "https://wiki.neelanurseries.com/index.php?title=Developers&oldid=9070"