The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Working thankfully, a much needed break from certain visiting family members.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
I saw your sig link and visited your site and read:
Finite State Machine for embedded systems
A State Machine is defined as a pattern that allows an object to change it's state as a result of an external stimulus. When the number of states is known and of a limited number it is called a Finite State Machine
That is probably the clearest and most concise explanation I have ever seen of state machine and finite state machine. I really like to read clear writing -- it makes learning so much faster.
And, oh yeah, I'm building a dotnet core WebAPI that uses this very cool QRCoder library[^] to generate QR Codes from text the user supplies. That library is really great. Makes things easy.