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
Search - "monthly review"
-
TL;DR, employers are often penny wise and pound foolish.
One morning, my vehicle had a potentially life-threatening condition that I needed fixed before I could drive to work. I was 3 hours late but made a productive day of it. Plus I had stayed late after work, for no pay, a couple of nights because I have the kind of work ethic that compels me to do weird stuff like that occasionally.
When the time clock report came out it showed I was 3 hours short for the pay period. I brought up that I had "paid it forward" a few weeks prior and asked for an exception based on that. I was told that a) all "extra" work had to have been approved prior to doing it and b) that pay period had already passed, so no, I'd need to make up the hours. Being pretty miffed at being so nickled-and-dimed, and for being expected to drive to work in spite of the possibility of losing my life, I just had them take it out of my time off.
Fast forward to my latest monthly review: After another potentially life-threatening vehicle breakdown and fix, I decided to ask whether I could have a couple of telecommute days per week to offset fuel and mileage to recover the repair cost for the wear and tear on my vehicle. The answer was "No, because then everyone will want to work from home and then we'd have no way to know if they're really working."
On that same day I got an offer for doing the same job at another company for 100% telecommute and at nearly twice the salary. I turned in my resignation two days later. Now they're scrambling to try to replace me.2 -
Today was my last day at my old job. At my last monthly review, the CEO actually said to me how things would be much better if I were making enough sales happen on the websites to justify my (very low) annual salary. I checked the numbers on my way out the door. In the past 8 months I definitely cleared that threshold and then some. I wonder if he would've given me the next 4 months off with pay. LOL
-
Totally hands off. Haven’t touched code for about 2 months at least. Just concentrating on organising things and meetings.
Manager in latest monthly review : “we’d like you to be more hands off”.
How!?11 -
>World War 3 outside
>Calls boss
Me: Can't come into work today, I died
Boss: This is going against your monthly performance review. -
So here's what I'm putting up with for the last 6 months, clients..
A client proposed to me a project he had in mind. Project is pretty solid, could have a bright future. Since they didn't have the money to spend, we agreed on a % of the income they will earn from the project. So, let's say I get 20% of the income in exchange for building the application. I didn't receive any down payment or payment of any kind.
Just for info, project is a Web application/portal and it is ~80% done at the moment. Client provided a logo and a wireframe/ideas/pictures how he sees the project. I built everything, from DB to Frontend. Also, project is completely custom made, no CMS or anything. Project will make profit by subscription base, every user of the project pays.
For various reasons, we did not yet sign a contract. So, what is my issue...
Client sent me his proposal of the contract, said it's solid stuff, just sign it. In the contract, it stated that he owns the application in full, can sell it, etc. and I get % of the price. There were also other sneaky parts about me having all the responsibility but owning nothing. I naturally declined and took a lawyer to construct a normal contract.
My proposal was/is, I own the application(source code) in full. They are obligated to pay the monthly percentage and can use the application normally and make profit. At any time, application can be bought by the client if they pay for the development. So, basically, they are getting the application to use "for free" with no initial payment/investment. And this is a long term deal, they can use is as this as long as they want. Also, if they go bankrupt at any time, no penalty or payment is needed, the risk is mine.
The client refused and what he claims is the following...
His share in the project is 80%, mine is 20%. If project is to be sold, I get 20% of the price. So, meaning, if we go to production tomorrow, if I want to buy his share, I have to buy 80% of the application I built entirely. Also he is convinced that by "telling me" what to built he's owning everything. In his words, he dictated me the notes and I'm just playing the violin.
I am having trouble explaining to him that he is getting the application to use and make profit basically for free and cannot and does not own the source code unless he buys it off. We are going in circles, I send him the contract to review, he changes it and returns it back. Also, he removes the parts where it is clearly states what he provided and what was done by me.
So, we kind off agreed on the authorship but in the case we break the contract he wants to be able to use the application for 3 more years.
Was anyone here in a similar situation? How do you handle this kind of situations?3 -
So my boss asked me to create an integration with a governamental program. This integration consisted in a text file being sent in a monthly basis.
Months later, he asked a coworker to automate the process, since the appointed user was finding the work too..."tedious",and asked me to check on the former regularly.
Thing is, everytime I checked, I saw a change being done in the core of the business layer, and I intervened, saying that those changes were either unnecessary or wrong altogether.
After three of these interventions, said coworker asked my boss to "ask" me to stop, and let him do his work. The boss concedes.
At the end of the week, my boss asked me to review the final product, and assert whether it conformed to our patterns.
After said review, he asks me why I've denied the work, to which I answer "a) the rules were changed by (the coworker), and are no longer correct, b) the the automator still requires a user intervention, and c) it threw an exception in the first time I (and I guess we) tested".
The job was placed in my time line the following day.