Last week, I submitted by Masters Thesis[1] on – to summarize greatly
– using Ruby to bring agile software development practices like TDD and
BDD to the cold, dark realm of hardware development.
I am very thankful to Matz and the community for the Ruby language,
which – to say the very least – saved me from the year-long drudgery
of researching and producing the trillionth (read: boring) thesis on
microprocessor caches.
May there be more research and papers on/with Ruby in academia! Fiat
Lux!
Last week, I submitted by Masters Thesis[1] on – to summarize greatly
– using Ruby to bring agile software development practices like TDD and
BDD to the cold, dark realm of hardware development.
Solid work! You probably just have created a useful tool!
Cold, dark hardware? I know they’re trying to reduce power consumption
of servers, but cold?
Ah, their goals reflect their world, it seems. It is a place so cold and
dark that you shiver with fear and cringe with disgust upon its sight;
for the development techniques it employs are those left behind by the
software world of 10 years ago.
According to one of my advisors, it was not until a few years ago that
the hardware industry finally accepted SCM (version control) systems.
Before that, they refused to hear of such nonsense because file backups
worked just fine!
Shocking. O_O
P.S. This is, of course, a brash generalization! Do correct me.
According to one of my advisors, it was not until a few years ago that
the hardware industry finally accepted SCM (version control) systems.
Before that, they refused to hear of such nonsense because file backups
worked just fine!
Shocking. O_O
P.S. This is, of course, a brash generalization! Do correct me.
I remember in the days before flash memory firmware, and before even
UV-erasable firmware, when firmware was in good old ROM. Man, it took
days to get anything changed. And every time I complained, I was told,
“Be patient! After all, ROM wasn’t built in a day!”
