10:01:54 From Mika to Everyone:
	hello!
	
10:02:58 From Stephane to Mutheu Atsiaya (direct message):
	Good morning!  Can you turn on you camera?
	
10:03:11 From Stephane to Amar Mahmutbegovic (direct message):
	Good morning!  Can you turn on you camera?
	
10:07:32 From Viktor to Everyone:
	Hello everybody! Thanks for the presentations!
	Question for Alexey : In your presentation you used as example a C implementation of the described portability concept, since C is still widely used in embedded development (true). In your opinion, will the implementation of the same concept in C++ (using available Modern C++ features) be less memory consuming?
	Another question for Alexey and Ravindra : have you tried to apply the portability concept to very resource constrained devices (like 8 bit MCUs) ?
	
10:07:49 From Nikolaj Fogh to Everyone:
	Question for Amar: Sometimes, you need to modify the source in some sub-component (package) or library while you are developing an application. Git submodules can make this easy as the source is right there. Is there a way in conan where you can easily update the source of a component, but use a pre-compiled package if you have no changes.
	
10:13:25 From Otzen to Everyone:
	Reg. AI concerns
	We all have learned from our mistakes, Young people using AI from start, will also fail, and learn from that.
	
10:23:57 From Viktor to Everyone:
	Talking about compilers/toolchains for 8 bit, there is an interesting and promising open source project which supports many MCU vendors - SDCC. Unfortunately it only supports C language. Do you know any examples of open source C++ compilers for 8 bit MCUs ?
	
10:27:16 From Nikolaj Fogh to Everyone:
	Does any of you have experience with using Nix/nix-shell for setting up development environments and for package management?
	
10:28:29 From Tom to Everyone:
	If you were going to invest time becoming more proficient in a language, would you spend time on C++, Rust, or something else (assuming C is your baseline today)?
	
10:30:14 From Videl Smith to Everyone:
	Looking for general guidance from team leads/hiring managers: For non-embedded developers interested in transitioning into the embedded space - what would be some key skills or knowledge areas to focus on as a part of that transition?
	
10:30:45 From Otzen to Everyone:
	Replying to "If you were going to invest time becoming more pro...":
	Python!
	
	My baseline was also C, and to start with I hated Python and its weak types, and other things.
	But over time I have come to love Python too, and can use my knowledge from both to improve both.
	
10:32:50 From Otzen to Everyone:
	Replying to "Looking for general guidance from team leads/hirin...":
	Depends on the area. A main thing with embedded SW is that you really need to know the HW it runs on.
	And 80% (estimated number) of embedded contain a controll loop
	
10:35:59 From Tom to Everyone:
	Replying to "If you were going to invest time becoming more pro...":
	Agree. I choose Python for almost all host-based code. Between C and Python, I feel I have my bases covered. But I don't use Python for embedded.
	
10:38:39 From Otzen to Everyone:
	Replying to "If you were going to invest time becoming more pro...":
	@Tom Agree. My point was that learning two languages that are as different as C and Python, forches your brain to think in new ways.
	
10:39:21 From Nikolaj Fogh to Everyone:
	Replying to "If you were going to invest time becoming more pro...":
	I would maybe say rust. Or, if you chose to learn C++, you should consider it a whole new language and not just C with classes. Algorithms and ranges instead of raw for loops :)
	
10:39:32 From Mark to Everyone:
	Replying to "If you were going to invest time becoming more pro...":
	Learning C++ first is a bit more gradual, as you can still use your C knowledge in a simple C++ application, just learning parts of C++ that interest you, a bit at a time. With Rust, it’s kind of like starting to learn a new language from scratch.
	But learning Python is worth learning anyway, as it’s so accessible.
	
10:40:48 From Mark to Everyone:
	Replying to "Looking for general guidance from team leads/hirin...":
	Basic electronics
	
10:41:05 From Otzen to Everyone:
	Replying to "Looking for general guidance from team leads/hirin...":
	PID controller
	
10:41:30 From Ravindra Singh to Everyone:
	Replying to "Looking for general guidance from team leads/hirin...":
	Get into microcontroller and microprocessor architecture
	
10:42:10 From Nikolaj Fogh to Everyone:
	Replying to "Looking for general guidance from team leads/hirin...":
	real-time aspects and problems.
	
10:43:56 From Mark to Everyone:
	Replying to "Looking for general guidance from team leads/hirin...":
	For many, it starts off with a motivation to do something they can’t do without dipping intp the embedded world.
	
	So take, for example, a “non-embedded” person who is technically competent in their high level world. They use their favorite software for what they are interested in (e.g. Mathematica for a math enthusiast). When they have a need to interface with something in the real world that their software does not support, they could be motivated to see how they could do that themselves, using at first a simple way such as using an Arduino to do basic things (supported perhaps by their environment).
	But then, when they outgrow the capabilities of the solution provided by their application, they could be motivated to use an MCU eval kit to go to the next level.
	Example related to the above. They want to generate a waveform that they computed in Mathematica at a higher sampling rate than the Arduino PWM supports.
	
10:43:59 From Mark to Everyone:
	Replying to "Looking for general guidance from team leads/hirin...":
	This motivation can then propel them to do the hard part - getting started rolling their own embedded solution without the safety net of the Arduino.
	
10:45:44 From brian to Everyone:
	Thank you all!