My occupation is that of serial entrepreneur. Currently I work on the internals of a graph database engine in my startup, mostly programming in C++11 but also some OCaml and Common Lisp.

My educational background is that of an autodidact. Dropped out of elementary school to work as a programmer, later dropped in on interesting bits of high school and university. Taught myself computer science from MIT's materials. Currently finishing up a physics degree at the Open University and starting on another bachelor's in history (classical antiquity).

I began OS development at the wee age of 13, with Richard Burgess's classic book "Developing Your Own 32-Bit Operating System". Thus began a long journey that I can't say has reached any particular conclusion, but has certainly been rewarding and educational nonetheless.

For 2015, I'll quit my current job and create a little startup, drop away PHP (which I use since 2004), and replace it definitively with NodeJS, thus promoting my own NodeJS web-framework.

As a hooby, I develop my kernel, OS, driver-stack and bootloader in C with assembler, and I'm actually porting V8 engine for using NodeJS as a low-level scripting engine / core application development environment for my OS.

I have worked for the past 15 years as a CNC Administrator and developer on Oracle's JD Edwards EnterpriseOne (E1). I work mostly with IBM i platform installations of E1. I now work as a private consultant.

_________________Adam

The name is fitting: Century Hobby OS -- At this rate, it's gonna take me that long!"Sometimes things just don't make sense until you figure them out." -- Phil Stahlheber

I've been working as a web developer for the last 15 years or so using C# and Java. Before that, I was mainly working with Visual Basic, QBasic, BasicA, Commodore 64 Basic, Spectrum Basic and Commodore CPM Basic.

In my spare time, in addition to OS development, I also do some indie game development, play a little bass and drums, and at one point, was lightly into drag racing street cars.

I've done engineering in Computer Science and now working in a Bank's IT dept, boring job though.From last 1 year I'm into OS development and now looking for a job which involves low-level stuff, don't think its going to happen any soon.

I'm a software developer, started before I was a teenager, now I've finished school, 3 university degrees, working full time for nearly 3 years at a huge multinational corporation.

I work with C#, Java, a lot of Perl and PL/SQL (particularly on servers), and a growing amount of Javascript (as we experiment with Node.js). I'm on a shared team that supports more than a dozen applications and accounts (we work on changes, bug fixes, research questions, etc. via tickets), although occasionally I'll be dedicated to an implementation, which are really formal with project managers, architects, testers, client QA.

i worked last ten years as a BIOS engineer. Mostly debugging, rarely write new software. ~4 years of BIOS developers and ~5 as a software quality engineer. These days, I am putting all my energy into python based automation. It is still low level testing stuff but all is happening over the SSH terminal. http://www.wsu.edu graduate in BSEE '06.

Since I look at both angles, software development tends to be highly specializing in certain areas and narrow scope and QA tends to gain more broader knowledge and of course less knowledge in certain functional areas. I liked doing both. QA tends to be more authoritative position. Especially when you have a dev experience and file a defect that is more insightful than B.S bugs which help developers a lot.

Also wanna study sort of AI and fintech in the future in a touch base, just as an interest. Also wanna finish my kernel project in few years time.

_________________key takeaway after spending yrs on sw industry: big issue small because everyone jumps on it and fixes it. small issue is big since everyone ignores and it causes catastrophy later. #devilisinthedetails

Since I look at both angles, software development tends to be highly specializing in certain areas and narrow scope and QA tends to gain more broader knowledge and of course less knowledge in certain functional areas. I liked doing both. QA tends to be more authoritative position. Especially when you have a dev experience and file a defect that is more insightful than B.S bugs which help developers a lot.

In many places there exist an unhealthy tension between dev and test/QA (precisely because test/QA is technically inferior (by design, i.e. by hiring and paying) and is looked down upon by dev) and if you happen to be in the latter group, you may need to prove you're equal (or at least not an "idiot"), if possible. If not, move to dev or a different company.

Who is online

Users browsing this forum: Google [Bot] and 2 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum