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 - "client proposal"
-
--- HTTP/3 is coming! And it won't use TCP! ---
A recent announcement reveals that HTTP - the protocol used by browsers to communicate with web servers - will get a major change in version 3!
Before, the HTTP protocols (version 1.0, 1.1 and 2.2) were all layered on top of TCP (Transmission Control Protocol).
TCP provides reliable, ordered, and error-checked delivery of data over an IP network.
It can handle hardware failures, timeouts, etc. and makes sure the data is received in the order it was transmitted in.
Also you can easily detect if any corruption during transmission has occurred.
All these features are necessary for a protocol such as HTTP, but TCP wasn't originally designed for HTTP!
It's a "one-size-fits-all" solution, suitable for *any* application that needs this kind of reliability.
TCP does a lot of round trips between the client and the server to make sure everybody receives their data. Especially if you're using SSL. This results in a high network latency.
So if we had a protocol which is basically designed for HTTP, it could help a lot at fixing all these problems.
This is the idea behind "QUIC", an experimental network protocol, originally created by Google, using UDP.
Now we all know how unreliable UDP is: You don't know if the data you sent was received nor does the receiver know if there is anything missing. Also, data is unordered, so if anything takes longer to send, it will most likely mix up with the other pieces of data. The only good part of UDP is its simplicity.
So why use this crappy thing for such an important protocol as HTTP?
Well, QUIC fixes all these problems UDP has, and provides the reliability of TCP but without introducing lots of round trips and a high latency! (How cool is that?)
The Internet Engineering Task Force (IETF) has been working (or is still working) on a standardized version of QUIC, although it's very different from Google's original proposal.
The IETF also wants to create a version of HTTP that uses QUIC, previously referred to as HTTP-over-QUIC. HTTP-over-QUIC isn't, however, HTTP/2 over QUIC.
It's a new, updated version of HTTP built for QUIC.
Now, the chairman of both the HTTP working group and the QUIC working group for IETF, Mark Nottingham, wanted to rename HTTP-over-QUIC to HTTP/3, and it seems like his proposal got accepted!
So version 3 of HTTP will have QUIC as an essential, integral feature, and we can expect that it no longer uses TCP as its network protocol.
We will see how it turns out in the end, but I'm sure we will have to wait a couple more years for HTTP/3, when it has been thoroughly tested and integrated.
Thank you for reading!27 -
This is how I feel most of my client proposal start:
* It's simple, I'd like to re-invent <the wheel>.
* All I want to do is use <rocketship engine> on <old typewriter>.
* I'm too cheap to hire a full-time < DBA, DevOps engineer, development team>. Can I pay you pennies?
* I'm poor and broke, can you do this for free?
* I'd like to <commit illegal act> and be <legal compliant standard>.
* I heard it was possible to <fly 30 people to the moon> using <Ford Model-T>. Please do this for us.
* I <sold my house>, but now <I'm locked out by the new owners>. Please help.11 -
Me: “Hi, Client. Did you review my proposal?”
Client: “Yes. You asked me to pay you using dollar bills. I found someone else who will do the work for mere pennies. Have a nice life!”
How does anyone make any money in web design and development anymore?14 -
!rant source: LinkedIn;
Yesterday I met with a potential client who wanted a website. I gave him a quote of X. He said, do this work for X/2 as I have lots of projects and I can keep you engaged for months.
If it was 2 years ago, I'd have happily accepted his proposal. But in the past 2 years I have learned this lesson hard way. Don't work for clients who don't pay well, because when a developer is not paid enough, the quality of work degrades. Hence the portfolio is degraded and so the future projects are also of low budget.
And before you know it, you will be surrounded by low paying clients who see you as a Skilled Labour.
Today, I don't negotiate, not even a single dollar. To justify my cost I make sure that no stones are left unturned while delivery.
It's better to work for 10 hours a week for 40$/hr then to work 40 hours a week for 10$/hr.3 -
-Sent a proposal to a client in September
-Client's virtual assistant replies this October
-Virtual assistant interviews me through chat
-Every time he asks a question, I reply immediately; when I ask for clarifications on the project, he replies the next day.
-This went on for two weeks
-Finally, the assistant scheduled me for a meeting with the boss.
-Same thing happens. He replies the next day when I ask for clarifications because it appears the assistant is incompetent
-Finally both of them told me I am their guy
-I waited for a few more days for the contract. Nothing.
-I told them nicely, if you don't reply within this day, I'll withdraw my proposal.
-They didn't reply and I went to withdraw my proposal
-When they realized that, they kept harassing me through message saying I'm their guy. Please don't withdraw the proposal.
-Didn't reply and stood by my word
Some freakin clients don't know how valuable time is for developers. Fkn idiots.1 -
I'm going for longest rant. TL:DR; version here:
http://pastebin.com/0Bp4jX9y
then:
http://pastebin.com/FfUiTzsh
Twat Client,
As per our conversation, here is an invoice for the work you requested on behalf of U.S. Bloom. I realize that you ended up going with another designer, but you did request samples of what my take on the logo design would be. The following line item is indicative of 1 hour of graphic design consultation as per your request via Skype.
As I recall, you mentioned that this is not how Upwork "works" but considering it was you who requested that I converse with you via Skype instead of via the Upwork messenger, and since there were no clear instructions on how to proceed with Upwork after our initial consultation, It is assumed that you were foregoing Upwork altogether to work with me directly, thus the invoice from me directly for my time involved in the project. I would have reached out to you via Skype, but it seems that you may have severed our connection there.
After spending a little time researching your company, I could not find current information for Basic Media Marketing, but I was able to reach out to your former partner Not A. Twat, who was more than helpful and suggested that he would encourage you to pay for the services rendered.
It is discouraging that you asked for my help and I delivered, but when I ask for compensation in return for my skills, you refused to pay and have now taken your site offline and removed me as a contact from Skype.
{[CLIENT of CLIENT]},
I am sorry that I have bothered you with this email. I copied you on it merely for transparency's sake. I am sure that your logo is great and I am sure whatever decision was made is awesome for your decision. I just wanted to make sure that you weren't getting "samples" of other people's work passed off as original work by Twat Media Marketing.
I can't speak for any of the other candidates, but since Twat asked me to conduct work with him via Skype rather than through Upwork, and since he's pretty much a ghost online now, (Site Offline, LinkedIn Removed or Blocked, and now Skype blocked as well) one has to think this was a hit and run to either crowdsource your logo inexpensively or pass off other artist's work as his own. That may not be the case, but from my perspective all signs are pointing to that scenario.
Here is a transcript. Some of his messages have been redacted.
As you can clearly see, requests and edits to the logo were being made from Jon to me, but he thinks it's a joke when I ask about invoicing and tries to pass it off as an interview. Do you see any interview questions in there? There were no questions about how long I have been designing, what are my rates, who have I done work for in the past, or examples of my previous work. There were none because he didn't need them at this point.
He'd already seen my proposal and my Behance.net portfolio as well as my rates on Upwork.com. This was a cut to the chase request for my ideas for your logo. It was not just ideas, but mock designs with criticism and approval awaiting. Not only that, but I only asked for an hour of compensation. After looking at the timestamps on our conversation, you can clearly see that I spent at least 3 hours corresponding with Twat on this project. That's three hours of work I could have spent on an honest paying customer.
I trust that TWATCLIENT will do the right thing. I just wanted you guys to know that I was in it to do the best design I could for you. I didn't know I was in it to waste three hours of my life in an "interview" I wasn't aware I was participating in.
Reply from ClientClient:
Hello Sir,
This message is very confusing?
We do not owe your company any money and have never worked with you before.
Therefore, I am going to disregard that invoice.
Reply from TWATCLIENT's boss via phone:
I have two problems with this. One I don't think your business practices are ethical, especially calling MY client directly and sending them an invoice.
Two why didn't you call or email Jon before copying my client on the email invoice?
Me: Probably because he's purposely avoiding me and I had no way to find him. I only got his email address today and that was from a WHOIS lookup.
Really, you don't think my business practices are ethical? What about slavery? Is that ethical? Is it ethical to pass of my designs to your client for critique, but not pay me for doing them?
... I'LL HAVE TO CALL YOU BACK!
My email follow up:
http://pastebin.com/hMYPGtxV
I got paid. The power of CCing the right combination of people is greater than most things on Earth.14 -
Potential Client Project:
"HIPAA compliant WordPress website"
Me: Can you tell me more about the website you're trying to publish?
Client: Site for uploading patient medical test results
Me: 🤦♂️ Fuuuuuuck. Sorry, you're on your own.
WORDPRESS?!?!8 -
What the fuck is wrong with the designers? We have had meetings with the client, a proposal drawn up, a project spec written, budget agreed, witeframes drawn up exactly to spec. Designer involved in all stages for input and ideas. Now the designers have the wireframes, they are supposed to create based on these. No they make up what goes on the pages that bare no resemblance to the wireframes in terms of requirements. I am fucking fuming. I have sent the designs back with a note. Please provide designs based on the wireframes.17
-
Me : so here is your quote for the app
Client : oh yer and it needs to work in both android and iOS, that's not a big deal right?
Me : of course not, however I am going to have to add a little something to your quote!
I don't get how when I ask a client if I got everything right so I can draft up a quote, they don't think to mention stuff like other features they had an idea for or cross platforms they wanted but didn't say in the original proposal -_-3 -
I've been so pissed off so many times, I thought I should divide them into categories.
- Pissed off at a fellow dev: I told him to use a constant instead of a hardcoded number.
He changed this: obj.method(3);
to this:
public static final int three = 3;
obj.method(three);
- Pissed off at management: I once got a $10 yearly raise.
- Pissed off at a client: They rejected our design proposal because the text was in spanish and they didn't speak spanish. It was lorem ipsum text.
- Pissed off at code: I once had to refactor a 500 line legacy jsp script with HTML, CSS, JS and Java completely intertwined.
- Pissed off at Twitter: They changed their API the day of our go-live, breaking all of their widgets, forcing us to move the go-live date and making me work an additional 8 hours after a week with almost no breaks.
- Pissed off at travel and logistics: They sent me to a hotel in Mexico City 2.5 hours away from the client's office.
Fun times...1 -
This is PART 1/2 of a series of rants over the course of a software engineering class years ago.
We were four team members, two had never failed a class, I’ll refer to them as MT and FT, male and female top students, respectively, and an older student with some real world experience who I’ll refer to as SR.
Rant 1: As I was familiar with the agile methodologies I became the Scrum Master and was set with the task of explaining it to the team members, SR showed up late and nobody seemed interested in learning new methodology. At this point I knew we'd have trouble as a team.
Rant 2: FT made up her project proposal without informing anybody, which required a real client/product owner. We only figured it out after her proposal was accepted as the project, so we ended up working with fake requirements.
Rant 3: This one is partly my fault. I researched first and then worked, which meant I was the last to turn up my work. In one activity MT pressures me and I agree to a deadline so everyone can send their work to the teacher in a timely manner. Since I was the last to finish, I was also asked to give the doc some formatting, which I did in a hurry so it wasn't the best.
The next day MT and FT start complaining about me, saying I took too long and that they expect me to do better next time or else. At the same time they were stressed and in a hurry because we had to explain the project outline in front of the class and they didn't study.
Turns out copying and pasting all your work in less than an hour means you don’t learn anything. FT actually asked me for help days before and I sent her a website in English, which she wasn't very good at, so she just ran it through Google Translate and called it a day.
Later FT called me rude for interrupting MT in the presentation, which I did because he started making up stuff about the project.
Rant 4: SR expressed his dislike for school through profanity in variable names and commit messages. This caused MT and FT to dislike him. I thought it was immature but if anything it should’ve been reported to the teacher and move on.
Rant 5: I was stuck trying to get the REST API working for the project Admittedly this was my fault, too, because I was pushing for the usage of things nobody was familiar with for the sake of learning. This coupled with SR’s profanity led to drama and the progress was dropped, starting over from scratch.
At this point I stepped down from the Scrum Master role as nobody seemed to listen anymore.4 -
A few weeks ago a client came to us asking for edits on their site. They had a developer in their office but they fired him a few days prior. After some looking at the piece of garbage they called a website I told my supervisors that it was built in Adobe Muse and from what I could find in a few quick searches it's shit and I didn't want to learn to use a shit tool. Apparently as a company we decided to hire a freelancer to handle this despite the fact that we didn't build the site and the client isn't paying for maintenance so I'm not sure why it's our fault.
Fast forward to today:
I've been in the office for 19 hours straight trying to learn how to use Muse and fix the client's site because somehow the freelancer managed to delete the mobile version of the site. When I ask my supervisors why I'm fixing and supporting a site we didn't build and don't have experience working in and the response is: we're presenting the client with a $50k proposal and we need all the good graces we can get.
Unless I'm gonna see some of the commission it doesn't really matter what we charge for the site, I make the same whether it's a free site or a $100k site.2 -
Spend >3 days preparing a proposal to a potential client...made it a bit cheaper to get into the company...
Now I'm too cheap to be good apparently...
FUCK CLIENTS!!!1 -
#noestimates
I fucking hate doing estimates. It stresses me out. I just did it, for a requirement about migration. I'm on my way to a fight now with the PO, because "the estimated time is too long". There was an agreement that deliverables were not to have extensive documentation and unit testing will only cover 30% of each use case (I know, stfu), but that's gone so I have to do the whole thing. I estimated 160 hours coding time, 40% of that for docs and 50 for testing. I'm standing by it.
All that stuff aside, what bothers me the most about estimates is that there's lazy motherfuckers who say shit like "I can have their RESTful ws in 2 days, but I said a month, because fuck it" and generate a win-win situation for them and their company, because the client - practically everytime - will just argue for the task to be completed in barely 10% less of the estimated time, accept the proposal and be happy waiting, the developer will fucking dawdle and the company will be paid for more hours than it deserves. Ugh.
Fuck estimates.2 -
Me - "Talks to client about his deliverable"
Him - So when can we show a demo?
Me - On thursday we could show a totally working deliverable.
Him - "Really on thursday? i was hoping to get it done for tomorrow"
My mind - *Dude. do you even know how much time does it takes to finish the latest changes you just asked me today? i mean probably we could get it done if you weren't so cheap at the proposal, you know, when I told you we would take longer if i dropped the price. And I could have a couple more devs working here so we could had the finish product a week ago, and still we are on time... so WTH dude *
Me - No, sorry I wouldn't dare to show you a half baked demo. But ill try my best to show you before that day.1 -
Why some (ok, a lot of) sales and buying guys are there just to transform any service experience in something bad?
In my experience, most sales guys promises anything, with absurd deadlines and it's up to you to make it work. Things never get good enough and, after all, the client doesn't like the work, you don't like and the sales guy doesn't like you could not make a perfectly task.
Buying guys are even worse when buying services. Email 30 developers in BCC: "Hi, I need this done by tomorrow morning and I would like to know how much you charge for it. I need your proposals in the next 30 minutes". He closes the deal with the fastest and cheapest proposal.
These things make absolutely no sense to me. -
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...we just sent a design proposal for a new feature to our biggest client. Their response? -Hmmm, let s drop this feature for now...OMG have you guys seen the new airbnb design for ios, like it s soooo cooool, we want that, redesign the whole app like this. - Yeah sure, except our app has nothing in common with theirs...Isn't it great when clients make decisions like this based on checking a new app version in the toilet real quick? 😝 Needless to say, we're not redesigning...
-
I've been programming for 15 years now or more if I count my years I programmed as a hobby. I'm mostly self learned. I'm working in an environment of a few developers and at least the same amount of other people (managers, sales, etc). We are creating Magento stores for middle sized businesses. The dev team is pretty good, I think.
But I'm struggling with management a lot. They are deciding on issues without asking us or even if I was asked about something and the answer was not what they expect, they ask the next developer below me. They do this all the way to Junior. A small example would be "lets create a testing site outside of deployment process on the server". Now if I do this, that site will never be updated and pose a security risk on the server for eternity because they would forget about it in a week. Adding it to our deployment process would take the same time and the testing site would benefit from security patches, quick deployment without logging in to the server, etc. Then the manager just disappears after hearing this from me. On slack, I get a question in 30 minutes from a remote developer about how to create an SSH user for a new site outside of deployment. I tell him the same. Then the junior gets called upstairs and ending up doing the job: no deployment, just plain SSH (SFTP) and manually creating the database. I end up doing it but He is "learning" how to do it.
An other example would be a day I was asked what is my opinion about Wordpress. We don't have any experience with Wordpress, I worked with Drupal before and when I look at a Wordpress codebase, I'm getting brain damage. They said Ok. The next day, comes the announcement that the boss decided to use Wordpress for our new agency website. For his own health and safety, I took the day off. At the end, the manager ended up hiring an indian developer who did a moderately fair job. No HiDPI sprites, no fancy SASS, just plain old CSS and a simple template. Lightyears worse than the site it was about to replace. But it did replace the old site, so now I have to look at it and identify myself part of the team. Best thing? We are now offering Wordpress development.
An other example is "lets do a quick order grid". This meant to be a table where the customer can enter SKU and quantity and they can theoretically order faster if they know the SKU already. It's a B2B solution. No one uses it. We have it for 2 sites now and in analytics, we have 5 page hits within 3 years on a site that's receiving 1000 users daily... Mostly our testing and the client looked at it. And no orders. I mean none, 0. I presented a well formatted study with screenshots from Analytics when I saw a proposal to a client to do this again. Guess what happened? Someone else from the team got the job to implement it. Happy client? No. They are questioning why no one is using it.
What would you do as a senior developer?
- Just serve notice and quit
- Try to talk to the boss (I don't see how it would work)
- Just don't give a shit1 -
My client recently asked for help with a product idea he has. He already got his lead developer to hack a proof of concept together.
My client knows I have more time and would start progressing the whole project. He says that he is fed up of all of these huge plans for some huge product...
I said ok, let's start getting the next few features on and using the product with the team.
He then said he wanted a big plan for the whole thing... so I said the whole point was to just get on with it and see how we get on as there are so many unknowns.
Somehow, due to a lack of other work, I have decided to help make a proposal that is far too long for this project. Would have just been better to get on for a few days and make a MVP of the product that works.
Instead I am waiting to see if this latest proposal will actually land me this work...
I'm pretty sure all of this back and forth is proof I don't want to work for this client! -
Client needs a section of their current website redesigned and add some functionality based on user interaction with the website.
ac - account director
ac: Need timings on FE build for his section on the website.
me: Cool can I see the wireframes/designs?
ac: No wires yet, designs are here...
me: *sees 3 pages mocked up out of 50 different ones in this particular section, and they all have different functionalities*
me: I can only give you estimates on the designed bits
ac: Just estimate based on the UX proposal, it's here...
me: *reads first line - "Make F&Q section and sub pages more visual*
me: Tasks described in the proposal are too generic!
ac: Just estimate based on the previous work done for this client (which have nothing to do with the current scope)
me: *dies and goes to freelancer heaven*1 -
Client accepted my proposal, but ghosted me the first time I started asking questions (like which version of MySQL he's using). Do I stop working on the project ? It's been two weeks of reminder emails with no response. The dummy I am didn't get his phone number when we started.6
-
I hate writing a new technical proposal for every new client because everyone of them is a different animal.
fuck this shit.2