In our project we have this Sentry integration that would let us know when something goes sideways (I am sure most devs know what I am talking about).
About a moth ago (all of devs and dev-ops) have missed one notification (we were all in a meeting an ignored the email) and live site was unusable.
Ever since I made a rule (for myself) to put the errors in a common Slack channel for all the devs to see. All good, no one was bugged.
A few days ago, Petr makes this announcement:
“Note – it seems that current errors from production are maybe false-positive and they are not affecting user. Sentry integration will be updated shortly.
Second note – even these errors may be false, we will still take a look into them.”
Today I see tow dozen errors in my email and I notify the devs, that maybe something went wrong, as there are too many different ones. If they are nothing than only 5 mins of our lives were lost.
To my notification I get this from Petr:
Yes, the FE errors on production were mentioned on stand-up and also in #frontend channel. They can be false positive, due to complications with Sentry integration.
There was no mention of said errors in any of the stand-ups this week or past week.
This morning, when I got into the office, I was surprised by my tester who said that none of the bugs I’ve put in for testing are fixed. Imagine my amazement when I checked the
bug-branch I was working on and the
testing-branch and they had very different code! So I go to Petr and:
Me: hey Petr, did you get any conflicts when merging the
bug-branch into the
Petr: Yes. But I fixed them. I kept the
Me: You should have kept the
bug-branch code as it was the newest one (and I added it to fix some bugs reported on the
Petr: Yes, yes. That is the one I used.
Half of the day has passed since and we still have different versions of code even though the
bug-branch was merged into the
testing-branch…Petr is on it (fixing).
I was saying that there is no possible way that a developer can be senior after only 2 years of experience. There is simply not enough time to meet the unexpected. And that is what, in my opinion, makes a senior: the unexpected. The ability to not be surprised and blocked. That is when a developer becomes senior.
There were of course voices that said that 2 years is more than enough. And it only depends on how passionate you are (how can passion be a factor in establishing seniority?). Then there was a slip from someone who said: if you convince your current employer to make you a senior, than you can put it in your CV and the next job recruiter would have to take you into account for a senior role. That made me think: hm.. sneaky one. So you you put it in your CV just for to market yourself? So the seniority became just a keyword? Who is to blame for this? Can we fix it?
About 3 years ago someone estimated that the number of programmers doubles every 5 years. I suppose then, there is this need of making oneself appear “seniorer” than the rest. But is it fair? and I mean it. There are senior developers with less than 2 years of experience and less than 25 years of life who participate in technical reviews during interviews (and I mean it because I have seen it) and they evaluate people that have more years of experience then they have of life, only to conclude that the respective developer is not good enough. I guess I am a bit afraid that I will one day be evaluated by one of these. And maybe I am more afraid of my reaction to it. I am afraid that I will try to impress this kid into hiring me. Is this ok? Is there something wrong with me? Are there any others like me?
I was recently invited to an interview for a frontend developer role. After the interviewer asked me a lot of questions about http, http2, devOps, linking backend with frontend he said: now let’s go to the more unpleasant questions. And he started with: what is this small tag at the beginning of an HTML page
<doctype... And he went on about DTD then we moved to local storage, then CSS and pre-processors …
When and why did HTML and CSS became unpleasant? how else would you develop for the web if not using HTML and CSS?
I am now asking you: people of the world that you call yourselves web developers, who are you and what did you do with the web developers?
This article exists because a tweet is to short and @ppk does not allow comments in his articles (i.e. this article: “What is a web developer?“). And maybe is a good thing that he does not allow comments – this gave me the opportunity to write down my thoughts without using other people’s space.
For about a year I moved from web development to application development (big mistake, will explain in a different post). And the same “developer problem” is present here too.
I believe this is because there are more and more people that call themselves developers [or even worse: web architects] and they don’t know the first thing about how the web works; they have no idea about what web standards are and why they exist.
Sadly most of them started their developer life – brace yourselves – programming in jQuery, or React or Elm (that’s the latest..). And I ask you now: how can one “program” in jQuery? When did jQuery become a programming language?
I tried saying these things out loud, but I got hit very hard by the young ones.
Maybe part of the problem is the wrong/too young [please read not enough life/work experienced] people in the high management or in the hiring process on the technical level (I know I saw this one too many times in a big corporation I used to work for).
What happened to people fighting for a better web? Are we just saying it to be trendy? What’s so trendy about not knowing the basics about doing your job? Why did you chose to be a web developer if you do not know what www is?
PS: I am not as old as the article sounds, but I am very sad about what I see around me. And maybe one article is not enough to change something, but I see it as a start. Maybe it will push some button on someone.