About a documentary that explores the dangerous human impact of social networking. Tech experts sound the alarm on their own creations! https://unixdigest.com/articles/the-social-dilemma.html
The other day, as I was going through some of my old notes, I stumbled upon something I had written about the console, the terminal and the shell on UNIX-like operating systems. I have decided to rewrite these notes in order to share them here on my website. So without further ado we will now stroll down memory lane and take a quick look at the origins of the Unix terminal and shell. And I will also give my advice to new users on Linux or BSD regarding the choice of terminal emulator and shell.
If we assume that no security bugs are injected by malicious programmers, then security issues, like other issues, are errors in code introduced by programmers by mistake. This means that the complexity of a program deeply affect the number of mistakes. This also means that one very important goal is to make code as simple as possible, until it becomes absolutely and obviously correct. Complexity is perhaps the most important factor that controls both the creation and defeat of errors, including
Are you a JavaScript framework or library fan-boy? One of those so-called front-end developers who cannot figure out how to build a website without completely smothering everything in JavaScript? Well, if you are, let me share a JavaScript nightmare with you. https://unixdigest.com/articles/javascript-malware-infested-nightmare.html
So, you normally do something like pip install foo, or composer install foo, or npm install foo, or perhaps go get foo, and you never read the source code of the package you just pulled down? Guess what, that's one (almost) sure way to blow up your project! https://unixdigest.com/articles/are-you-trusting-open-source-blindly-then-you-are-in-for-a-world-of-hurt.html
In 2020 Laurent Bercot, the developer of the s6 init tools, was contacted by a recruiter at Google. He wrote an answer which he made public. That answer deserves to be spread far and wide. I present the answer here as a direct copy from the original. https://unixdigest.com/articles/this-is-how-you-keep-your-dignity-and-not-sell-your-soul.html
Some people argue that you cannot test procedural PHP code, but that is not true. In this small tutorial I am going to show you how you can use PHPUnit to test your procedural functions. https://unixdigest.com/tutorials/how-to-test-procedural-functions-with-phpunit.html
It has happened again. Another company has contacted me because they had a PHP product developed which has turned into a huge beast of complexity. Basic functionality has stopped working and nobody wants to have anything to do with it. It has serious consequences for the company because they are loosing money since the product isn't up and running. I have come to the same conclusion which I have reached in other similar situations, the codebase is one big pile of complex object-oriented mess. ht
In this article we'll take a look at some of the benefits of procedural programming in PHP, and in general, and what you need to do in order to do it well. https://unixdigest.com/articles/procedural-programming-in-php.html
It's easy to determine if you really need the object-oriented paradigm, you just need to look for the things that you can only do with object-oriented programming and then ask yourself whether you really need that. It's called "The Three Pillars of Object-Oriented Programming". If you don't use all three at the same time, then you're not doing object-oriented programming and you don't need it. https://unixdigest.com/articles/how-do-i-know-if-i-really-need-object-oriented-programming.html
