OpenBSD Journal
Home : : Add Story : : Archives : : About : : Create Account : : Login :
OpenBSD Daily, code review, and you
Contributed by pitrh on Fri Jun 9 16:48:32 2017 (GMT)
from the a-source-a-day-keeps-the-bugs-away dept.

OpenBSD developer Adam Wolk (awolk@) talks about a community effort to read at least one C source file from OpenBSD every day at https://blog.tintagel.pl/2017/06/09/openbsd-daily.html.

I made a new years resolution to read at least one C source file from OpenBSD daily. The goal was to both get better at C and to contribute more to the base system and userland development.

[topicblog]

<< Running OpenBSD on Azure | Reply | Threaded | KARL - kernel address randomized link >>

Threshold: Help

Related Links
more by pitrh


  Re: OpenBSD Daily, code review, and you (mod 1/9)
by Blake (2a01:e34:ec06:8f90:cabc:c8ff:fedb:4d83) (undeadly@2112.net) on Sat Jun 10 18:48:55 2017 (GMT)
l33.fr
  This is a cracking great idea that many organizations would do well to adopt.

Thanks.
  [ Show thread ] [ Reply to this comment ] [ Mod Up ] [ Mod Down ]

  Re: OpenBSD Daily, code review, and you (mod -1/7)
by Anonymous Coward (93.224.165.104) on Sun Jun 18 06:36:54 2017 (GMT)
  I'm just thinking I did everything wrong. Looking back 22 years when I first bought a K&R and started on a C coding path, the learning curve looked something like this: first four years were very steep learning curve filled with reading many programs and learning lots of system calls by (hundreds of?) sample/skeleton programs. But the creation of programs were limited.

The following four years after that were the first programs that exceeded 1000 lines and had a certain sophistication. Then came the first program that came to be the first project, written from scratch, 20000+ lines of code over the span of 10 years, but, hardly any code reading in the UNIX user land source, little code reading in the kernel. Looks like a stark contrast to what's suggested.

Another question that pops up in my mind is how much should one be passive and read others code before becoming active and possibly writing things from scratch?

Also, where do you draw the line on "poking someone else mind?". Code reading is cool but every time you do it you assume the state of mind of someone else, does it annoy you or do you feel swept away? Does it amass questions or does it open the pandoras box? How far does the rabbit hole really go down?
  [ Show thread ] [ Reply to this comment ] [ Mod Up ] [ Mod Down ]

[ Home | Add Story | Archives | Polls | About ]

Copyright © 2004-2008 Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to April 2nd 2004 as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. Some icons from slashdot.org used with permission from Kathleen. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. Search engine is ht://Dig. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]