[erhk]

Request:

Make a blog post on the experience. What does the heatmap of changes look like over 5 years? I cant imagine you burnt the candle on both ends for that whole time.

What is the final lines of code?

What blockers did you not anticipate that killed a lot of time? Hardest problem?

I think you've got a treasure of interesting retrospectives to share :)

[beebs93]

Yeah, good questions that I'd also love to see see answers to!

My favorites for retro-like discussions (if you think it will be beneficial):

1. What did you worry about the most in the beginning that later turned out to be silly/inconsequential?

2. What did you intentionally put off in the beginning thinking it wasn't a big deal that you later regretted not spending more time on?

[halfer53]

Thanks, that's a good point. I'll definitely do that

[dang]

Email [e-mail] when it's up, and we can put it in the second-chance pool (https://news.ycombinator.com/pool, explained at https://news.ycombinator.com/item?id=26998308).

[halfer53]

Thanks will do

[sdesol]

Here are some quick insights until OP does his blog post.

For a high-level breakdown of the files changed:

https://public-001.gitsense.com/insights/github/repos?p=focu...

681 files were changed, with the most being C/C Header files.

The file age is interesting as it shows 175 files were changed over a 2 year period. And you have about 279 files that were probably just imported and never touched again or were infrequently changed. Note renaming files/directory can skew this number.

And if you are looking for a heatmap, you can look at

https://public-001.gitsense.com/insights/github/repos?p=comm...

The superscript value <number>v besides the file/directory indicates how many versions there are. So the higher the version, the greater the focus. In this case, the kernel, include and fs directories saw most of the activity.

In the future, I will gray out files that no longer exists on the latest tree, but for now you can look at the year beside the files/directories to get an idea of when they were last touched.

And here are the top 20 most frequently changed files

           path          | revs
   -----------------------+------
    kernel/system.c       |  151
    kernel/proc.c         |  128
    include/sys/syscall.h |  124
    kernel/exception.c    |  120
    include/kernel/proc.h |   95
    Makefile              |   90
    kernel/main.c         |   80
    user/shell.c          |   69
    fs/inode.c            |   67
    winix/sys_stdio.c     |   60
    README.md             |   53
    driver/tty.c          |   52
    kernel/sched.c        |   49
    kernel/clock.c        |   46
    winix/wini_ipc.c      |   45
    fs/fs.h               |   44
    winix/mm.c            |   44
    fs/makefs.c           |   42
    winix/sigsend.c       |   42
    init/init.c           |   41

Disclaimer: I'm the creator of the tool for the links above and there is a bug where the menu will say 45 days window but it is a 5 years window.

[halfer53]

Thanks for sharing this, that's very insightful.

[sdesol]

No problem. If you are going to do a blog post and need stats, you can contact me through my profile info.

[mmaunder]

Agreed. Not many devs tackle Mount Everest, so we’re interested in your journey.

[aiisjustanif]

Is building an OS considered Mount Everest in terms of software development?

[nlvrhvn]

No it's more like K2. Everest has become mainstream...