A big part of my work has to do with code. I’ve worked as system administrator – installing, patching, and configuring someone else’s code. I’ve worked as independent programmer, writing code on my own. I also programmed as part of the team. And on top of that, I worked as Team Leader and Project Manager, where I had to interact a lot with programmers. Programming world on its own is as huge as the universe. There is always something to learn. When I find something worthy or something that I understand enough to write about, I share it in this category.
WordPress Theme Developer Handbook:
The Theme Developer Handbook is a repository for all things WordPress themes. Whether you’re new to WordPress themes, or you’re an experienced theme developer, you should be able to find the answer to many of your theme-related questions right here.
Finally, there is a more organized resources that WordPress Codex!
PHPMetrics is yet another tool for static analysis of your PHP codebase. It aims to provide a simpler and easier to understand report, than all those other tools in the PHP ecosystem today.
Headless Browsers is a list of (almost) all headless web browsers in existence. These are browsers without graphical user interface, controlled programmatically, and useful for testing, automation, and other similar tasks.
I’ve used one or two. I’v heard about three of four. I had no idea there was such a variety though.
Software Engineering Tips shares some tips on how to figure out if you are a bad programmer, and how to remedy that.
Signs that you’re a bad programmer
- Inability to reason about code
- Poor understanding of the language’s programming model
- Deficient research skills / Chronically poor knowledge of the platform’s features
- Inability to comprehend pointers
- Difficulty seeing through recursion
- Distrust of code
If you are not a bad programmer, check if you are mediocre one.
Signs that you are a mediocre programmer
- Inability to think in sets
- Lack of critical thinking
- Pinball Programming
- Unfamiliar with the principles of security
- Code is a mess
And, finally, here are some signs that you shouldn’t be a programmer.
Signs that you shouldn’t be a programmer
- Inability to determine the order of program execution
- Insufficient ability to think abstractly
- Collyer Brothers syndrome
- Dysfunctional sense of causality
- Indifference to outcomes
The article also suggests some alternative career paths for you.
