Youngest OSDever

[nexos]

I was 12, but I basically just copied and pasted Brokenthorn, which didn't work very well in the long run... It wasn't till I was 14 that I new what I was doing.

Now my problem is being too thorough

[euclaise]

When I was ~14 I remember being jealous of another osdever who was around the same age and had their OS written in assembly up to having a basic web browser, while I was stuck on figuring out paging. It might have been the GhostOS person, but I'm not certain.

I'm now 20 and decided to revisit OS development in the past week's mornings, and it was nice to find that I no longer had any trouble, and was able to get to userspace by the end of the week.

[zaval]

2A. I wish, I started, when I was 12, but then my craze was chemistry. I got the computer, when I was 27 (in decimal ). it was january 2008. I learnt VBA, then Java, then quickly realized, I want to know how the things really work, instead of these endless OOP abstractions and who "extends" whom and whom "implements" and that my biggest interests are C and OS. plus assembly, of course, but it's kind of a dainty, a cherry on top this tempting cake. I decided, that I am going to try to implement an OS probably in 2010, but I knew, I am way not ready for that. I decided to start making it in 2014, I wasn't ready for it still, but then I couldn't resist letting this idea live anymore. so I bought Cubieboard 2 and Beagle Bone Black SBCs, inaugurating by this the start of the era and, practically, for having an architecturally diverse target park, I always remembered, that Windows NT was started this way for not making architecture biased decisions. later that year, I bought iMac g5. the next year I was given a cute MIPS SBC (grateful for this to Alexandru Voica, then an Imagination employee). ^_^ and still am at the very beginning. at least, the desire is very time stable. and I am glad it is.

[bellezzasolo]

I was 12, but I basically just copied and pasted Brokenthorn, which didn't work very well in the long run... It wasn't till I was 14 that I new what I was doing.

Now my problem is being too thorough

That was my starting point too (other than a very simple 16 bit assembly one. Where I thought "BITS 32" would enable 32 bit mode ).

Iteration after iteration followed.

[astrido554]

Ye i started with 9 or 10, some years ago. I really got interested in OSDev with 8 though, but only saw some projects. I've improved my skills, but still looking forward to improve them even more.

[AJ]

My age is the meaning of life, the universe and everything.

Started back in uni in 2000, so aged 19.

[PavelChekov]

I started in 6th grade and joined this forum not long after that (excuse some of my early, really stupid posts). I wrote the first OS code that actually ran (just initialized the stack and GDT and such up to jumping to long mode) when I was 9, but only recently have I actually started writing good code. I taught myself C when I was 7, and I still haven't had any formal instruction in anything computer-related, so it took me a few years to figure out how to really read documentation and write professional code.

(Btw thank you guys here that have helped me over the years and been patient with my shenanigans.)

[avcado]

I started in 7th grade (12? 13?). By then, I had been programming assembly and C for 1-2 years. I was browsing the OSDev subreddit and thought to myself, hey this seems fun. I started out writing a small "Hello world" bootsector with NASM.

It wasn't for I'd say a few years (15-16 [now]) that I knew what I was doing. OSDev has been in the back of my mind since 7th grade, it's (to me) the most fun branch of programming

[adev5311]

I started programming on 5 (probably roblox lua)
and C# on 8, and OS developing on 10.
When I started OS developing, I tried to jump to 32bit without setting GDT/Protected mode

[Kaius]

Originally was about 12 (or 13, depending on what we're considering "OS dev"). I wrote a bootloader and a few sectors worth of an assembly program. At 13, I decided to just use GRUB and start working with C a bit. Didn't get very far, but I'm currently on my third go-around and so far so good.