Yesterday I posted a short article about SDLC, and yes, it is about a tedious work of development. You need to comply with the sequence of the development process and obey the development process. Starts with gathering requirement, planning, developing, testing, and deploying. One story short, you may take about a week of timeline process for 1 hour of development. Crazy work it is.
Many developers often takes shortcut of their work and fast forward the development process ahead of it's timeline. They also overlap one development projects with another, so they only takes about one day of their time for two or three projects at the same time. It is efficient, and seemingly good plan, in terms on one part of the project: development. But an app development consist of many part of module like planning and testing. And overlapping projects might result to a overlapping responsibility, which might occurs to testing process and deployment process. What if two of their app broken at the same time? Which one will they fix first? Since they overlap development at the same time?
One Day, One App
I was once a one-man-army of development. I do the gathering requirement. I do the planning, development, testing, and also deployment. In conclusion: I am a genius :)
But no, really. It is very common for a developer to do all the development task all by themselves. It is efficient since only they know how their app works, and therefore they can easily deploy it themselves. So many developers did this. And such a Full Stack Developer exist.
Once I did a three apps development on three days. So on average I did a one-app per one-day. They are simple apps really. I only customize on the logic part. I reused the same framework, templates, authentication, forms, and database structure. I recall it was a Presence App, Document Repository App, and Document Dashboard App. Three department needed three different apps, and I made all of the three. Did it overnight for each of the app. And I also made it all online on three days. Dang!
I think it was easy since mostly my job is copy pasting the same template form on each app. The only thing different was the Controller, Database, and App Theme. They only needed basic logic of computation and therefore no need for complex libraries.
Was It Good?
Most of my application was used by 10 to 20 employees concurrently, and no need for heavy traffic and computation. I seldom got bugs report on my apps since they only used for the basic features. But this is the fun part:
Do they really use our app? Or they found bug but never report it? And continue using their excel based work?
Ah, I never found out it myself. I only did the basic part of deployment of my apps. It ran on VM. The monitoring done by other IT sub department. And yet I never got metrics of my apps. Maybe they never configure it on the VM. Or the metric so small they don't even spiked the app :')
The most important thing is i did my job. I did it complete with no reported bugs. It was good, optimistically.
Really?
No, really. It was a complete mess. Here are the lists:
- No technical documentation
- No monitoring
- No unit tests (only minimal ones)
- No customization by admin
- No security guard
And I think so many more missing part here I can't even list. I think no developer should done Full Stack Development all by himself. They might be have a wider knowledge, but no specification dedicated to one part of development, and it is not good. A generalist might fits them more than a developer.
Knower of all, master of none
Yes, I think that's it.
It was a fun experience, doing all SDLC process by myself. But so many missing part of them all, and yet nobody even notice since the user don't even notice it themselves. Good ol' times.
Top comments (0)