In regular “semantic versioning” (the most popular), there is no build number.

Wasting money and development resources is not though.

Curl.

Don’t forget to ask what is the other possible value(s) if the scenario doesn’t happen, because that is something forgotten most of the time.

CMake does that…

I have a cure for all cancers. Except that bodies refuse to use its molecules, but it still cures cancer in theory. That’s how agile have always been used around me.

Agile wants to empower devs, but managers do not want this.

It assumes that: devs can and have the right to talk to the final user, devs can negotiate anything, and devs can make plans. Where I’ve used agile, the whole circus was taken hostage by the managers and there was nothing you could do about it.

You’ll tell me it’s not real agile, but it’s like real communism, I’ve never seen it.

Most companies I’ve worked for “do agile because agile” and everything revolves around agile. And you can’t change this because they decide and they have the money.

It’s not Agile’s fault

that managers want to stay in control of everything, and they decide whether they do it or not.

It’s like real communism: it’s perfect but it’s not possible to implement in our universe.

Noooooodo

There are 5 or 6 ridiculous questions about AI at the beginning. They should have made it less obvious.

Handlers, module managers, any shitty thing that handle stuff or load stuff, but has a name more obscure than a philosophical book. God I hate this.

Sublime Merge is the best. Not easy but I’ve tried them all.

Coming from SVN and Mercurial where commits are increasing integers, I thought the SHA-1 stuff would be a PITA. It’s not and no one cares about numbers anymore.

In 20 years of using Python, I never had one issue with the indentation. Use spaces all the time, use PyCharm, and that’s it.

Whitespace is statistically insignificant in Python.

no-code effort

And we know that the no-code fad was very successful in the past.

With an infinite supply of shitty projects created by “devs” who can’t code, I’ll have a guaranteed job for ever. Thanks AI!

Why? I got a new job and, for a lot of reasons, it’s the first time I’m really motivated by my coworkers. I want to understand this small but relatively complex codebase, and the bookmarks/breakpoints system is not good when you need to discover a lot of topics in a short amount of time (a few months usually when you get a new job).

I’m currently fixing bugs, and while it’s going great so far, some bugs are more complex and may require me to understand the whole “flow” of the architecture, but it’s different for each bug. I work in the medical field and I have to juggle with a few bugs at the same time before anything is validated, that’s why I wanted to take notes of what I deemed interesting while debugging.

Also I often switch branches which explains why breakpoints have to be changed all the time. Breakpoints and Doxygen don’t show in a simple way how the code can go from step 1 to step 2 to step 3.

You’ve said everything actually.

1. Fork
2. Build (and if you can’t, stop because it will be too painful)
3. Learn the code, debug, and write at the same time
4. Write a merge request

That’s it. If you’re not a professional it will be longer but the steps are the same.

The only advice would be to learn your tools, learn the IDE, learn to debug. And if there is no documentation, write it.

it’s good but it’s wrong

That’s impossible.

People around me have used https://playwright.dev/ successfully and you can program it in multiple languages. That’s for web sites though.

For real applications (like C++ or C#) it’s still a mess but it works fine, nothing really broke for the past 10/15 years.