 | Lars Fosdal on Security alarm provider Woonve… |
 | Thomas Mueller on Question got closed in May 202… |
 | Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
Posted by jpluimers on 2025/01/16
For me, saving bitbucket.org passwords fails consistently (when using app passwords, it keeps popping up the git credentials dialog on Windows each time I try to push to origin), so I need to dig deeper into [Wayback/Archive] Updating Git for Windows credentials for Bitbucket app password – Stack Overflow.
Query: [Wayback/Archive] windows store bitbucket app password in git – Google Suche
--jeroen
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2024/11/12
[Wayback/Archive] GitHub – src-d/hercules: Gaining advanced insights from Git repository history.
This project, with the command-line tools hercules and labours is on my research list as it can get pretty good long-term insights on project health (the tool is programming language independent).
Especially the half-life of code is a good measurement, as well as the existence of code bursts (hello major version increments!).
This research part is important: [Wayback/Archive] Change Bursts as Defect Predictors – Publications – Software Engineering Chair (Prof. Zeller), by Nachiappan Nagappan, Andreas Zeller, Thomas Zimmermann, Kim Herzig, Brendan Murphy
Posted in BASTA!, Conference Topics, Conferences, Development, DVCS - Distributed Version Control, EKON, git, ITDevCon, Software Development, Source Code Management, Static Code Analysis | Leave a Comment »
Posted by jpluimers on 2024/11/07
This one is clear and concise. [Wayback/Archive] liburing/CONTRIBUTING.md at master · axboe/liburing · GitHub of which some highlights:
…
The main reasons for the rules are:
- Keep the code consistent
- Keep the git repository consistent
- Maintain bisectability
…
No fixup commits! Sometimes people post a change and errors are pointed out in the commit, and the author then does a followup fix for that error. This isn’t acceptable, please squash fixup commits into the commit that introduced the problem in the first place. This is done by amending the fix into the original commit that caused the issue. You can do that with
git rebase -iand arrange the commit order such that the fixup is right after the original commit, and then use ‘s‘ (for squash) to squash the fixup into the original commit. Don’t forget to edit the commit message while doing that, as git will combine the two commit messages into one. Or you can do it manually. Once done, force push your rewritten git history. See reasons 1-3 in the introduction series for why that is.…
A good commit explains the WHY of a commit – explain the reason for this commit to exist. Don’t explain what the code in commit does, that should be readily apparent from just reading the code. liburing commits follow the following format:
Posted in Development, DVCS - Distributed Version Control, git, Open Source, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2024/10/24
Some good slide material (and even better further down this post) from [Wayback/Archive] Lou Creemers on Twitter: “Which of these software development books would you want? I loooved Blaming the User”:
Posted in Conference Topics, Conferences, Development, DVCS - Distributed Version Control, Event, git, Google, GoogleSearch, Pingback, Software Development, Source Code Management, Stackoverflow | Leave a Comment »
Posted by jpluimers on 2024/09/26
A while ago [Wayback/Archive] b0rk (Julia Evans [Wayback/Archive) wrote an interesting Tweet on finding back where you broke code of which the OCR text reads like this:
strategy: change working code into broken code
If I have a working version of the program, I like to:
- go back to the working code
- slowly start changing it to be more like my broken code
- test if it’s still working after every single tiny change
· ⬊⸳⬈˙⬊⸳⬈˙⬊⸳ OH THAT’S WHAT BROKE IT!!!I like this because it puts me back on solid ground: with every change make that DOESN’T cause the bug to come back, I know that wasn’t the problem.
by JULIA EVANS @bork wizardzines.com
This is similar (her arrows were of varying length) to using a binary search algorithm hunting for where the code was broken using bisection: repeatedly halving your search space to quickly zoom into the problem.
Another important aspect is that small commits while fiddling to solve an issue can help you determine what small commit was actually solving the issue.
Posted in Algorithms, Conference Topics, Conferences, Development, DVCS - Distributed Version Control, Event, git, Mercurial/Hg, Ruby, Software Development, Source Code Management, Versioning | Leave a Comment »
Posted by jpluimers on 2024/08/27
These Tweets from Kris are food for thought about using standards for Commit Messages and Commit Emojis.
It is the “writing zzzz by convention” mantra all over the place (where zzzz can be anything from code to documentation): does it add value, should it be formalised, can it by achieved by other means?
I need to think about it later, so I saved his tweets below:
Posted in Conference Topics, Conferences, Development, DVCS - Distributed Version Control, Event, git, Software Development, Source Code Management | 2 Comments »
Posted by jpluimers on 2024/08/07
At the time of writing a lot of this might be more recent, but for quite some time codepoints.net had not been updated with code point information newer Unicode releases.
Basically it was stuck at Unicode version 8.0 with some 120k glyphs. At the time of writing Unicode version 15.0 is in beta and the difference between 15.0 and 8.0 is some 24k glyphs.
So I had a quick twitter chat with the author and jotted down the links in this blog post so I won’t forget them.
There I learned it was open source (I think it is the only Unicode codepoint site that is).
Here it goes:
Posted in *nix, *nix-tools, Apache2, codepoints.net, Conference Topics, Conferences, Database Development, Debian, Development, DVCS - Distributed Version Control, Encoding, Event, GitHub, Linux, MySQL, PHP, Power User, Scripting, Software Development, Source Code Management, Unicode, Web Development | Leave a Comment »
Posted by jpluimers on 2024/07/04
For my link archive:
In todays cross-platform world, it pays if your tooling can send logging to syslog.
Though originating from the CP/M and SunOS background, I have done most of my professional development work in Windows back-ends and front-ends, so here are some links relevant to that:
BSD SYSLOG protocol
Used RFC: RFC-3164
--jeroen
Posted in .NET, C#, Delphi, Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management, Subversion/SVN | 2 Comments »
Posted by jpluimers on 2024/06/25
Every once in a while, b0rk (Julia Evans, of [Wayback/Archive] wizard zines fame) asks interesting questions like below that results in lot of cool links.
I have blogged assemblies of them before (see for instance Lots of interesting git links via b0rk on Twitter) and this one is no different:
[Wayback/Archive] Julia Evans on Twitter: “what are some helpful programming learning games? thinking of things like mystery.knightlab.com for SQL, and flexboxfroggy.com, and ohmygit.org especially interested in games that have helped you learn something”
The response was overwhelmingly good (I tried to indicate when games are not free or not playable from a web browser). I summarised it below.
Posted in *nix, *nix-tools, Conference Topics, Conferences, CSS, Database Development, Development, DVCS - Distributed Version Control, Event, Games, git, Multi-Threading / Concurrency, Power User, RegEx, Scripting, sh, Sh Shell, Software Development, Source Code Management, SQL, Web Development | Leave a Comment »
Posted by jpluimers on 2024/06/11
Hopefully Gitlab can do this: [Wayback/Archive] 🔎Julia Evans🔍 on Twitter: “what’s an easy way to release the code of a project without allowing issues / pull requests? An archived github repo is almost like this, but it doesn’t seem to let you push new commits (I sometimes have code that I want to let people view but don’t want to maintain in any way)”
[Wayback/Archive] Jeroen Wiert Pluimers on Twitter: “@b0rk @MrSwats In a lot of features, GitLab is way ahead of GitHub especially on fine grained settings. Of course this means it is way harder to configure. You can for instance organise your projects in hierarchies and configure access control on each node.”
Though GitLab has other drawbacks:
[Wayback/Archive] __ian__ = RfcReader() on Twitter: “@jpluimers @b0rk @MrSwats Gitlab has no way to disable commenting on commits or blocking assholes though, so 6 of one, half dozen of the other” / Twitter
–jeroen
Posted in Development, DVCS - Distributed Version Control, gist, git, GitHub, GitLab, Software Development, Source Code Management | Leave a Comment »
The Wiert Corner - irregular stream of stuff 