Differences

This shows you the differences between two versions of the page.

--- user:yephick [2018/06/14 16:48] – created Igor Yefmov
+++ user:yephick [2022/04/04 23:32] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-Every problem in software engineering can be solved by introducing a new layer of abstraction. Except for a problem of too many layers of abstraction.
+\(\text{Every problem in software engineering can be solved by introducing a new layer of abstraction. Except for a problem of too many layers of abstraction.}\)
+Until joining 2r1y (and later SUB2r) my experience included being a systems admin, a DBA, team lead on a very sizeable project (totalling over 100 people involved), writing in Assembly and even in machine code (for a Soviet-era programmable MK-61 calculator), in C and C++, %%FoxPro%%, Basic (MS/GW, Turbo, Visual), Pascal (and Delphi), Lua, Java, JS, HTML, DOS batch, ... the list goes on and on, well beyond the count of 200 for applications ranging from tiny home toy projects to accounting, to online education tools, to high-performance ETL tools, to cloud payment services, and even (once, by necessity) an actual antivirus. But never have I had a need to write something to be run on a non-PC (except for that MK-61, of course).
+All that changed with writing firmware code for our SUB2r camera and with the few lines in Verilog for the "code" running on FPGA itself - at this point the realization came that this quite literally covers "all" the aspects of the modern world's software engineering areas. From transistor gates and CPU microcode all the way to clouds. The term "full stack" engineer doesn't really convey the breath of all that experience which is why a suggestion was made by [[user:richn|our CEO Richard Neumann]] to call this a **"hyperstack engineer"**.
+  * [[Embedded C code doesn't have to be ugly]]