• 1 Post
  • 4 Comments
Joined 1 year ago
cake
Cake day: June 4th, 2023

help-circle



  • IMO there’s a place for both. A print statement will reveal a flaw in the programmer’s thinking regarding the control flow of the program and the state at that time. If a print statement gives something unexpected, you know exactly where to look in the debugger. If it gives you what you expected, it reveals the problem may be elsewhere


  • I have a few projects I switch between based on how much time I have and where my interests lie.

    My most recent is a from-scratch compiler for a made-up language (MIT), Intercept, written in C with no dependencies (apart from libc, of course). I’m really proud of this one, and have even been lucky enough to work with other people on it.

    And then there’s my text editor (MIT), which is an homage to Emacs. I just have learned so much from Emacs and like it so much that I had to make my own. At this point it’s got a working SDL2 and OpenGL backend, as well as tree-sitter syntax highlighting, and, of course, is extensible through LITE LISP, the built-in programming language.

    Finally, my pride and joy, LensorOS (GPLv3). I started this project when I first started learning C++, and through it I have learned amazing things about how computers actually work, from hardware to kernels to userspace.

    Just wanted to say, this is a really good idea for a thread! I really enjoy seeing all these amazing projects from everybody