Hacker News Re-Imagined

My process for building a feature

  • 100 points
  • 7 days ago

  • @simonw
  • Created a post

My process for building a feature

@kkoncevicius 5 days

Replying to @simonw 🎙

Thank you for sharing. Even thou I have a lot fewer projects and majority of my work happens on the projects of clients - I managed to take away some useful ideas and tips. Specifically using "issue" as a place where everything gets tied together and combining all aspects of a feature into a single main-branch commit is something I will try to do more from now on.

Since your workflow is so GitHub centered, one place that IMO could use more structuring is GitHub issue labels [1] [2] [3]. Defaults are quite ad-hoc, with color not really representing anything. And setting up new default labels for new projects can be automated with command line scripts.

[1] http://karolis.koncevicius.lt/posts/improving_github_issue_l...

[2] https://medium.com/@dave_lunny/sane-github-labels-c5d2e6004b...

[3] https://robinpowered.com/blog/best-practice-system-for-organ...


@harryvederci 5 days

Replying to @simonw 🎙

Hey Simon, as you mentioned Github and I regard you as one of the biggest SQLite hackers on the interwebz, I was wondering if you've tried Fossil[0]?

Might be nice to hack around with, especially combined with its CGI extension[1] feature.

[0] https://fossil-scm.org/

[1] https://fossil-scm.org/home/doc/trunk/www/serverext.wiki


@zomglings 6 days

Replying to @simonw 🎙

I was hoping this would discuss how he chooses which features to build. Unfortunately, that is not what this is.

It is a description of a pretty rigorous development workflow, but I think it will mostly only be useful to people who want to contribute code to Simon's projects.


About Us

site design / logo © 2022 Box Piper