Details
-
AboutSoftware engineer
-
LocationSarajevo, B&H
-
Github
Joined devRant on 7/15/2016
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
!rant
Me and my friend just launched the invitation phase for our paid service hookdoo at www.hookdoo.com
Service enables you to quickly set up webhooks with minimal effort that can run your code on your fleet of servers.
If you are interested, request an invitation.
I'll make sure to give devRant users a priority over others, and some bonus credits as well :-)6 -
Got assigned an intern to mentor him, with an explicit order not to do any of the legwork for him.
We start out with some fuzzy requirements. Intern starts overengineering a generic solution, so I make out a best architecture that conforms to the business requirements and I explain it to the intern why are we going to use such approach and tell him how we are going to do it in three phases.
I explain the intern the first phase, break it down in small tasks for him and return to my projects...
After a couple of days of no words from the intern, I decide to check up on him to see how is he progressing, only to hear him complaining the task is boring. So, instead of doing the assigned tasks, he decided he should do a "design" for a feature I told him explicitly not to do, since it is going to be designed by the design team later on.
I explain it to the intern that we have to do the boring task first because we can't proceed with the next phase of the implementation without the necessary data from the phase one.
Intern says okay and assures me he got it now. Few days later, I check up on him, and he tells me he feels he is doing all the work and that I don't contribute to the project. I call up my boss and tell him intern wants a meeting. Since I was working from home, I quickly pack my things and head to the office. Boss talks to the intern before I managed to get to the office. Once I got there, I meet the intern, and he tells me everything is okay. I ask what did the boss say to make things okay all of a sudden, and he tells me he said we are a team now. Our company has a flat hierarchy model, so he tells me he doesn't feel he needs a mentor, that we are both equal, and that I have no idea how to work in a team, and then proceeds to comfort me on how human interaction is hard and that I will learn it one day... I was like wtf?
I tell him to finish the phase one of the project and start with the phase two, and I leave home again.
I call up my boss and ask him what did he say to the intern, and he says: "nothing much, just explained the project a little bit and how it fits in the grand scheme of things.". I ask about the equal team members thing, and me not being a mentor any longer, the boss goes wtf, saying he never said anything about that to him.
So the kid can't focus on a single task, over-engineers everything and doesn't feel he can learn anything from developers with more experience, doesn't want to obey commands, and also likes to lie to manipulate others.
Tomorrow we'll decide what to do with him...
Sorry for the long rant, it was a long stressful day.86 -
Go to the vacation.
Return back to see all those useless features that should not be part of the MVP, that I have previously rejected multiple times, poorly implemented...
Now we have to maintain this shit, that nobody even uses in real life...
Fucking imaginary use cases... -
Creating a real mvp prototype, and not a "mvp prototype" that ended up being a production release...
-
!rant
I've made an opensource project, some of you guys might find it useful. Simple, lightweight and fast tool/server that allows you to execute scripts/programs on incoming webhooks. Check it out at https://github.com/adnanh/webhook -
x comes out.
Team: hey let's rewrite our project using x!
4 months later..
y comes out.
Team: x is so crappy, let's rewrite our project using y!
3 months later...
z comes out...
Team: why did we ever use y, let's rewrite our project using z!
.
.
.5 -
Boss: don't worry about the architecture, it's an one-off project, just make it work...
2 months later...
Boss: hey, remember that one-off project? we need to add in a few more features... Also can we reuse that code for this new one-off project we have to do for this new client?3