juangacovas

And you know it because you're forced to use windows somewhere?

Love the downvotes ;P

IMAP email parser for a ticket-like program. Even with abstractions and libraries, email can be such a pita...

I like when projects like this mention other projects. "Phinx" (PHP) has been a breeze to work with for database migrations for years now, and handles more than my team needs. Meanwhile, some time ago a colleague in other job was raging they didn't have migrations but a chaos of DBs in their environments.

Indeed, made some preliminary tests under RHEL 9 (Rocky, etc) for example and if you're used to compile HAProxy from sources to use specific OpenSSL versions, testing "aws-lc" is fairly straightforward. Their BUILD instructions and INSTALL file from HAProxy also help.

Agree. But you need confidence on being able to debug / log / fix / revert, so having a strong knowledge of some of the parts is mandatory (i.e. server if it's web-dev, etc).

My experience: coming from programming in C, then doing web-scripting with Perl, then PHP 4 through 5, 7 and 8 versions, it's been delightful. Big improvements in speed, ecosystem, very nice backwards compatibility in general (which is hard to do), and keeps being a flexible, multi-paradigm language. About frameworks, you can do things now like-ruby-on-rails with Laravel, like-java with Symfony, or just use any custom solution you see to fit better for team/yourself. Mantra: you can do shit code with any language, and PHP is flexible enough to let you organize projects the right way.

Sorry but your example shows that you know Python better than PHP.

Same here, PasswordAuthentication is globally No, but I always hold an special username for emergencies which is the only user allowed to login via password (easy at sshd_config file, Match User xxxx then "PasswordAuthentication yes"). Besides emergencies, also works wonders when some sysadmins insist to login via bare metal terminal and cannot use a key...

Same here, gource did help to visualize a complete revamp / refactor of a software, from the current mess by that time, to the final, pratically complete rewrite it was (through a process, since keep it working was mandatory). Really interesting to see the "mess" mutating into a more organized file struct, etc.

Well, in my particular experience with juniors, it's astonishing the so many ways they have to make any code run slower than it has to be (besides the network and database queries), just by thinking 'nah, this is a computer and it can do millions of ops by second'. And that's why I always take the "premature optimization" dogma with a grain of salt while my life's miserable enough having to accelerate some other's stuff.

I don't think that tools like ReaR (Relax and Recover) would agree with retiring ISOs..