As a self taught programmer with a Communication Studies degree, this definitely resonates. The ability to articulate the problem in code is kind of the starting point for most productive development work.
Any experienced programmer will be able to tell what kind of person another programmer is just by the way they write their code.
Code written by programmers with humanities backgrounds is easily identifiable as being of bad quality.
Kind of like vibe coding meets programming by accident, before vibe coding was really a term.
It's a faux pas to even mention this IRL, but good coders know what's up.
Those "coders" usually get promoted to people managers, which is usually what they want anyway because their self-worth relies on abusing others to mitigate the correct self-perception they have of being "inferior".
The problem is, things need to be solved and vibe+accident programming can only go so far.
But fear not, they can always scapegoat whoever solves the problems, because if they were not to blame, how could they know what was up or even feel the need to correct it?
This is a high level of bias and generalization about an enormous group of people with varied backgrounds and experiences, not to mention selection bias as you don't know many good coders backgrounds who may in fact be from humanities.
Even if many of the bad coders are those who were in humanities and don't have coding experience because they just entered the field (because once you get it you are no longer a humanities background)
I actually have the exact opposite experience when I try out Chromium based browsers. I end up missing FF dev tools. I love the ability to edit and resend network requests. I'm sure I could figure out how do to so in Chrome devtools, but just not as intuitive (at least to me!)
For me it depends on what I'm doing. I too like the edit and resend ability in firefox dev tools but what I've found it lacking is the option to automatically open dev tools for pop ups, which is possible in chrome.
There is a beginning of solution for popups in Firefox DevTools.
You can toggle `devtools.popups.debug` preference [1] to true in about:config
and DevTools should open on popups.
Unfortunately, there is some limitations, highlighted at the end of that bugzilla entry. It won't work for <a target="_blank">, while it should work for window.open usages.
I've started tinkering on a tool for test case management. It would be a direct competitor of things link TestRail or Practitest. QA folks that I talk to seem to feel very underserved by these types of tools, so it feels like there would be demand for something with a bit more polish.
I built this desktop app to provide a gui for managing environment variables. I bounce between many environments and run scripts pretty regularly, so it helps!
No login, no network requests. Just uses your file system.
