nofearinc

4 ms·

1.
by nofearinc 11y ago
I don't mind the job being done by people building products with visual tools. I just believe that the "developer" title has a unified and consistent meaning across different platforms, languages, communities and what not, an
2.
by nofearinc 11y ago
most _capable_ people selling WordPress nowadays don't sell WordPress itself, but a solution, purely because of the bad rap and the "WordPress developers" out there. I personally don't feel comfortable being "ashame
3.
by nofearinc 11y ago
Precisely. I wouldn't care if it was 0.01% of the "developers" in WordPress. But when it's the vast majority, actual developers become a limited and hardly visible minority.
4.
by nofearinc 11y ago
I get your point and I'd genuinely apologize to every architect graduate (in the construction space) who feels insulted by that. Even if my day-to-day follows the "software architect" definition, I would gladly replace it wit
5.
by nofearinc 11y ago
Agreed with all of the above. I'm even surprised that more of the "hardcore devs" didn't get annoyed by WordPress crossing the 25% web market share a week ago. I can see how more and more large businesses turn to WordPre
6.
by nofearinc 11y ago
Other than the bulleted list I linked a few articles as well, including the problem with having to educate the customers. While education is always required, most of the "developers" underprice the market, sell unstable solutions
7.
by nofearinc 11y ago
I believe that what walod refers to is the astounding number of people calling themselves "developers" while installing vanilla WordPress with a few plugins and a theme, and changing a few admin options. There's certainly not
8.
by nofearinc 11y ago
A few ideas: 1) A public list of recognized job titles (think of an employment bureau catalog or else) that defines the job description by an authority. At least a reference that most would pay attention to. 2) A unified training program fo
9.
by nofearinc 11y ago
I couldn't agree more. But people need to make a living, and often loud folks take over an ecosystem if they are allowed to do so, and without standardization or a way to verify skills, we'll turn into the Internet marketing commu
10.
by nofearinc 11y ago
Two of the problems we struggle with here as technical people: 1) You receive hundreds of spam applications even if you mention explicitly code-related stuff - like GitHub/Bitbucket repo, years of programming experience, know-how in TD
11.
by nofearinc 11y ago
WordPress Core developer is standard, but my business for example is building large multisite solutions for enterprise clients and while I do have 30+ patches in Core, that's not what I do for a living and can't compare with those
12.
by nofearinc 11y ago
Correct - 500 interviews for developers including requirements for a GitHub/Bitbucket repo, X years of programming experience etc and 400 of them haven't seen code in their lifetime. The fact that people are so assured that what t
13.
by nofearinc 11y ago
Confidence ain't the problem here; it is polluting the market with broken extensions, underpricing services that have been estimated by Lego builders first, and being unable to find an actual developer in the wide pool of people with n
14.
by nofearinc 11y ago
It doesn't, unless you provide services that consist of installing WordPress and a premium theme and playing with available options, or switching to a new one if a color settings isn't available. It's like calling yourself a
15.
by nofearinc 12y ago
While that's correct, it's a global shift in the perception of building websites. 10 years ago when most CMS weren't that flexible and extensible the majority of the websites were built from scratch, or with custom frameworks
16.
by nofearinc 12y ago
Thanks for the remark