I can't help it, but most animation concepts on modern websites just feel like prettier versions of <marquee> and <blink> tags back in the 90s.

This alternative to serverless PHP is mind blowing!

I needed a easy and non-permanent way to use a PHP debugger in existing WordPress development setups. Here's my tiny script/setup to get XDebug running within minutes in a standard WordPress image. No need to change Dockerfiles. Also works on WSL. github.com/strzyzewski/xd…

Sunday read. This is hilarious. Engineers are competing who creates the worst UI on Reddit. I think the winners are: 1/ Enter your phone number

Be very careful with Google Bard, it’s still at the beginning stages and lacks quality in its responses – although the responses look nice and sophisticated. Bard failed me several times on programming related topics and even tends to make up untrue facts. Use with caution.

Analyzing bugs, reproducing errors and setting up debuggers are essential parts of software development. You're going to be very unhappy if you don't enjoy these things. You can't avoid making mistakes but you should always work on your problem analyzing and solving skills.

Today's find: Rodrigo Pombo 's wonderful Git History extension for VSCode. Intuitive UI that breaks away from the traditional vertical lists, great work 👏

Does anyone remember this?

Had my first experiences with GitHub Copilot Chat. 1. Compared to GPT-4, Copilot Chat is less capable of understanding context. 2. Copilot generates faster and its code seems less complex than GPT-4's. 3. The UI integration into VS Code is awesome. I recommend trying it!

Whenever there's a Dev-Docker image that has all dev-tools already built in, take it. Everything that you "script" around a standard Docker image, can and will break at some point.

A messy coding environment is like a messy kitchen. The mess makes it hard to do good work. Examples: 🚫 Unused files 🚫 Failing tests 🚫 Misspelled words 🚫 Commented out code 🚫 Lint warnings and errors 🚫 No consistent naming conventions 🚫 Console filled with warnings/errors

Prediction: In a few years, the world will be divided into regions where AI usage is heavily regulated or where it’s free. We'll relive everything we've experienced with data protection and labeling obligations in the last 20 years – but multiplied by ten. It won't be pretty.

Trying to optimize Gitlab CI jobs that are filled with "sleep 60" commands is rather difficult

People who fear AI tools the most usually are the ones that can’t figure out how to use them. I’m tired of a digital society that’s mostly driven by fears and lack of knowledge.

Writing CI scripts without AI is nuts

SEO tip: Invest your time in useful content instead of obsessing with core web vitals. Technical SEO can't fix missing content.

Good advice on GitLab CI/CD scripting tinplavec.medium.com/gitlab-ci-cd-b…

How to be happy: Don't write fancy scripts in your CI/CD. Don't customize Docker Images by installing packages. Instead use specialized Docker Images and let them do that one thing that they do best. Orchestrate the workflow and collect the artifacts. Package and deploy.

How to remove joy from developer jobs: - Let them mostly do estimates - Deliver requirements and specifics through many different communication channels - Avoid to understand the issue the estimate is about - Try to reduce estimates through intense haggling

Let‘s see how the algorithm handles free speech when it comes to Elon memes #ElonMusk