Joined devRant on 6/9/2016
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
My biggest dev ambition is to continue supporting and improving the same codebase for at least 5 years.
That codebase is already 6 years old and going strong.2
I don't often have reasons to rant, but today is the one.
We had a deadline to finish a project, because today people are being trained on it. I've been working my ass off on it for a year now.
I "finished" about 2 weeks ago, meaning QA could start for real 2 weeks ago. As you can imagine for a project this long, there was bugs. Lots of them.
We did our best to fix most of them, or find work-arounds we could use during the demo.
Let's just say it isn't going great so far. We have several known bugs, which at some point may crash the app, a very low confidence in the fact that it's going to work well.
Oh and obviously the client is one who already use heavily the solution. Today we figured we never tested on a device with 0% disk space. Files are cut partway because of that, and obviously things crash.
I have a feeling there will be yelling sometime soon.
Right now I'm enjoying the calm before the storm, with coffee in hand.
Why do people still continue to promise dates to clients, after me telling them for 5 years not to do that?
We are a 2 devs team, with 11 apps on 2 platforms, 2 back-ends (one is legacy) and obviously our marketing site, which doubles up as e-commerce. We just can't promise anything, because any emergency reduce our development bandwith for new features either to 50% or 0%. There are so much known bugs it's not funny anymore, and we don't even have time to solve those.
To add insult to injury, at the beginning of the month, the SaaS provider for our legacy back-end (which have not been maintained for 2 years now) decided we had to update to PHP7.1 before 1st October. If we don't do anything, on monday this thing is broken. I hate that thing, and I hate having to maintain it even though I was promised I wouldn't have to ever have anything to do on it.
Monday will be "fun"...2
I just wanted to develop a cool webapp-controlled lighting for my bar.
Next things I know, there is electronics scattered everywhere, 2 multimeters to find what the fck is wrong with a PSU not outputting 1/100 of the current it's supposed to, said PSU opened on my desk, and I'm trying to find a capacitor online because there isn't any fcking electronics store selling spare parts anymore in my city.
- PSU means Power Supply Unit, in this case a computer one.
- PSU was given by a friend and is out of warranty
- the total consumption for all LEDs is 24A @ 5V consumption. A refurbished PSU is ideal for that
- that PSU is rated 2A @ 5V on the stand-by, which is perfect to power a Raspberry Pi. The issue is that there is a sharp voltage drop as soon as you try to use more than 20mA.9
Skipping unit tests and documentation ...
I'm starting to recover after not writing a single test for the first 6 years of my professional carrer (wasn't taught in school, didn't know where to start, man I should have really found a mentor earlier), and barely any documentation (I was the sole developer for several years, and just didn't get into the habbit).
Unit testing is still not a habit, but now I have the first tests to serve as an example and an idea what/how to test at least, and I try to get every new "framework" function/class at least commented properly.
Wish me luck2
Have my projects compile without a single warning.
The road will be long, and deprecation warnings will pounce at me, but I shall prevail.
Why the fuck does Windows still not have a fcking decent package manager?
I hear you "but but but, there is Chocolatey, it's great, try it!". Well yeah if you only want binaries.
But I do need to, you know, develop and compile things, and without includes, code, and a reliable way to produce working binaries from that, it's useless.
Guess who needs to download dependencies one by one, compile them one by one?
Don't get me started on broken MinGW, or the "recommended" way of doing a bat script to have proper includes (what the hell, that's the entire purpose of env variables), or the fact that there is NO convention on where to install things.1
After spending the year after graduation trying to do a business with some school friends, that didn't make a dime for a year, I decided to look for a real paying job.
My first step was to go to a hackathon and hack for the week-end. I got involved in not one, but 2 projects: the second was because someone I met and won with at a previous hackathon asked me to, and I finished the first project early. Let's call her "S"
Then comes the end of the hackathon, and after it concludes I muster the courage to go on stage and say that I'm looking for a job, so feel free to chat me up.
No one really came to me for a job, but S came to talk to me about the startup she wants to launch, and how she is looking for a tech guy. I was close to dismiss it, because I was looking for a job paying $$$, but agreed to met so that she could show me her business plan and try to convince me.
Turns out she did convince me, because the business plan was solid, she was very motivated, and had already started validating the idea: there was a real need.
Now there we are, 5 years later, about 10 employees and paying ourselves real salary.
Am I the only one who reads CSS "!important" as "not important", because of the '!'? No matter how many times I read it ....5
When you only have to support recent browsers/devices, but then a commercial promises more support of legacy browsers/devices for free.