iveqy

Big companies spend a lot of resources and money to be license compliant. One way to make sure that the company follow OSS licenses is to have a process for how to contribute. The person posted the issue has not been through that processes for this specific project and hence can not contribute.

We have a few files at work that change name with every commit…

I've a long way to go before it's polished enough to be released. But for me, I use it every day.

I love a quick, keyboard driven application and I also have good codebase to use as a testing ground for CI/CD, code analysis etc.

Two weeks ago I actually got my first customer buying a license for it, after being in development for 9 years!

But as always, it's seldom the tools, but the right tool used for the wrong usecase that is the problem.

2. Domain names $50/year

3. Lenovo yoga c920 $400/year

When you are able to use large parts of the dependency, then it's often better to use it than to roll your own.

For CI/CD you can get quite a long way with git hooks and for code review I would look into git appraise. that's the best one I've found but I would really like to hear if someone else has a better idea here!

My tip is to change the requirements. Requirements are often poorly written and often contain a suggested implementation. Try to find the real problem, talk to your stakeholders and alter the requirements to find the easiest implementation.

I've saved months of work several times by doing this.

Translated from swedish: A swedish hight school did a pilot with a class with 22 pupils with facial recognition for taking attendance. The school is fined with 20 000 USD for invading the pupils privacy. All pupils has agreed to participate but that doesn't matter since the pupils is dependent to the school, they cannot agree to something like this.

Are we actually doing things too complicated and too good for the business case?

It turned out that the power supply on their server was malfunctioning sometimes delivering too little power. Specially when taking the code paths my IP phone triggered.

The server software was built in php. It's not often you start looking for a bug in PHP but end up switching a capacitor in the PSU.

My point is that even if your write in php, php is running C libraries, that is running ASM that is running hardware and every part of this chain is important. There's no such thing as "works everywhere", it's just "have a very high chance of working everywhere".

(off-topic) thanks for the sds library. I'm a heavy user of it.