Agile for Embedded — Impossible!

Posted by lazlo – May 3, 2013

A sarcastic collection of the typical lousy excuses people come up with for why “agile” can not be applied to their project

Watch end enjoy!

Gerard Meszaros on Automated Testing Patterns and Smells

Posted by lazlo – May 3, 2013

Got my first scope!

Posted by lazlo – May 3, 2013

A friend of mine lend me a HP 54600A (100 MHz dual channel) and I’m so happy and confident that having such a tool will help me to better understand the some electrical effects that are still mysteries to me.

Thank you tec!

$T2eC16hHJHwE9n8ikMRbBRWHj4wPRQ~~60_57

Processing LHC Data

Posted by lazlo – April 23, 2013

Inside the RT (Linux Kernel) Patch

Posted by lazlo – April 19, 2013

A interactive map of the Linux Kernel

Posted by lazlo – April 19, 2013

I just discovered that the image, I’d carelessly have taken from Google image search when looking for a depiction of the Linux kernel structure months ago,is actually “only” a bitmap of an interactive map that can be found at MakeLinux.net and has been created by Constatine Shulyupin.

Linux_kernel_mapNot only can you zoom in and out of the kernels structure but each entity is linked to a documentation page.

Knipper – Symphony No. 4 [1/4] (Moscow Symphony – Dudarova)

Posted by lazlo – April 18, 2013

Lehakat Cheil Hayam – Keshe’eheye gadol

Posted by lazlo – April 18, 2013

Foyer des Arts – Hubschraubereinsatz (1982)

Posted by lazlo – April 18, 2013

Read “Stop Writing So Much Firmware”

Posted by lazlo – April 17, 2013

Just read an very nice article by James Grenning titled “Engineers and Programmers, Stop Writing So Much Firmware” on software design with regards to embedded system and this piece of software embedded folks call firmware.

He makes the point that business logic must be decoupled from technological implementation dependencies very nicely. This wisdom is nothing new but still you don’t see it used very often in the real world (sadly).

My conclusions from this reading are basically:

  • firmware should be designed with a systems software aspect in mind (not application software)
  • decouple any business logic from implementation technology (okay, this is an obvious one)

I think especially the first point is one I’ll be able to apply to my  prototype scope firmware.