maelkum · HackerTrans

I can't recommend Sourcehut enough!

The git.sr.ht service is just the tip of the iceberg, though. It also provides you with CI, issue tracking, mailing lists... And it works perfectly in Lynx so you don't even have to leave command line to use the browser interface.

maelkum

6 anni fadiscuss

I think the Shadowrun adage is applicable here: "Watch your back, shoot straight, and never, ever, cut a deal with a dragon."

Microsoft is the dragon here. Even if it appears friendly you still don't cut a deal with it, or you become a pawn in its game.

maelkum

7 anni fadiscuss

I have a codebase that amounts to several kLOC of C++, available here: https://git.sr.ht/~maelkum/viuavm While I openly admit that parts of it are shoddily written, I also try to always use the "reliable subset" of C++.

From my experience it is not hard to make it a habit (e.g. using `::at()` and declaring variables as `auto const x = ...;` is muscle memory at this point) but the code becomes very verbose and looks like programmed defensively to a sometimes ridiculous extent.

So I understand your skepticism. To address the point of relying on developers being "ideal": just turn the compiler warning flags up to eleven, make all warnings errors, and run your tests two times - one time with sanitisers, and the other under Valgrind. This won't catch all errors, sure, but will still make you more confident in your code's reliability.

maelkum

8 anni fadiscuss

I am using this method to a great success at my current job. It leads to always having a clear, well-defined place where you look for changes related to issue XYZ.

Support from tooling also helps a lot, e.g. "checkout branch of issue XYZ".

maelkum

8 anni fadiscuss

Probably the latter. The "deadbeef" string as a "random" hexadecimal example is pretty common.

maelkum

8 anni fadiscuss

In a true hackerish style, I rolled my own solution: https://github.com/marekjm/issue

Back in 2015, I decided that all the issue tracking systems I knew are too heavy-weight. I don't need kanban, agile, or any other buzz - I just need a simple tool to track my issues. I had several requirements: 1/ it must work off-line, 2/ it must be distrubuted (to allow many people working simultaneously on their off-line clones), 3/ it must work in command line, 4/ it must provide minimum distraction, 5/ it must allow me to tag, and search the issues, and I worked from there.

fast forward to 2018 ...and I'm still using it. It does the job for my Free Software projects, and helps me at work (tested in three companies already). It is definitely not bug-free (but the risk of data-loss should be low), and the installation must be done manually from GitHub, but it Works For Me (tm) ;-)

Sample workflow:

    $ issue open "OH noes, a bug"
    $ issue ls --open
    deadbeef OH noes, a bug
    $ issue slug --git-checkout --git-branch --git deadbeef # or just issue sl -gBC de
    ...hack, hack hack...
    $ git commit -am "Fix"
    $ issue close -g HEAD de
    $ git checkout master
    $ git merge -

By using the `-` as the placeholder for "last active issue" I can make this sequence even shorter. Minimal distraction, no switching between the terminal and the browser, no waiting for slow Web interfaces.

/end of shameless plug

maelkum

8 anni fadiscuss

You mean "The most resilient torrent website in the Galaxy"? The TPB crew was ahead of the times.

comments