Implementing the application exactly like the client specified, because they won't listen.

--- 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!

Holy shit, I never thought I would see the day that Microsoft makes me even more disappointed, but this is a NEW low.

The windows 11 email client is being deprecated, and they automatically "upgrade" you to the new outlook.

THERE'S ADS. THERE'S ADVERTISEMENTS IN OUTLOOK. WHAT THE FUCK. IF YOU CLICK THIS, IT JUST OPENS THE AD IN A BROWSER. IT'S IN MY EMAIL LIST, THEY ARE ACTIVELY TRYING TO TRICK YOU INTO CLICKING IT.

This is crappy free Chinese mobile game ad level of scummy. I never fucking thought they would honestly stoop so low as to make misleading ads a default part of their operating system. But here it is, in an app installed by default, developed in-house by Microsoft. Actually astounding and appalling.

The tech stack at my current gig is the worst shit I’ve ever dealt with...

I can’t fucking stand programs, especially browser based programs, to open new windows. New tab, okay sure, ideally I just want the current tab I’m on to update when I click on a link.

Ticketing system: Autotask
Fucking opens up with a crappy piss poor sorting method and no proper filtering for ticket views. Nope you have to go create a fucking dashboard to parse/filter the shit you want to see. So I either have to go create a metric-arse tonne of custom ticket views and switch between them or just use the default turdburger view. Add to that that when I click on a ticket, it opens another fucking window with the ticket information. If I want to do time entry, it just feels some primal need to open another fucking window!!! Then even if I mark the ticket complete it just minimizes the goddamn second ticket window. So my jankbox-supreme PC that my company provided gets to strugglepuff along trying to keep 10 million chrome windows open. Yeah, sure 6GB of ram is great for IT work, especially when using hot steaming piles of trashjuice software!

I have to manually close these windows regularly throughout the day or the system just shits the bed and halts.

RMM tool: Continuum
This fucker takes the goddamn soggy waffle award for being utterly fucking useless. Same problem with the windows as autotask except this special snowflake likes to open a login prompt as a full-fuck-mothering-new window when we need to open a LMI rescue session!!! I need to enter a username and a password. That’s it! I don’t need a full screen window to enter credentials! FUCK!!! Btw the LMI tools only work like 70% of the time and drag ass compared to literally every other remote support tool I’ve ever used. I’ve found that it’s sometimes just faster to walk someone through enabling RDP on their system then remoting in from another system where LMI didn’t decide to be fully suicidal and just kill itself.

Our fucking chief asshat and sergeant fucknuts mcdoogal can’t fucking setup anything so the antivirus software is pushed to all client systems but everything is just set to the default site settings. Absolutely zero care or thought or effort was put forth and these gorilla spunk drinking, rimjob jockey motherfuckers sell this as a managed AntiVirus.

We use a shitty password manager than no one besides I use because there is a fully unencrypted oneNote notebook that everyone uses because fuck security right? “Sometimes it’s just faster to have the passwords at the ready without having to log into the password manager.” Chief Asshat in my first week on the job.

Not to mention that windows server is unlicensed in almost every client environment, the domain admin password is same across multiple client sites, is the same password to log into firewalls, and office 365 environments!!!

I’ve brought up tons of ways to fix these problems, but they have their heads so far up their own asses getting high on undeserved smugness since “they have been in business for almost ten years”. Like, Whoop Dee MotherFucking Doo! You have only been lucky to skate by with this dumpster fire you call a software stack, you could probably fill 10 olympic sized swimming pools to the brim with the logarrhea that flows from your gullets not only to us but also to your customers, and you won’t implement anything that is good for you, your company, or your poor clients because you take ten minutes to try and understand something new.

I’m fucking livid because I’m stuck in a position where I can’t just quit and work on my business full time. I’m married and have a 6m old baby. Between both my wife and I working we barely make ends meet and there’s absolutely zero reason that I couldn’t be providing better service to customers without having to lie through my teeth to them and I could easily support my family and be about 264826290461% happier!

But because we make so little, I can’t scrap together enough money to get Terranimbus (my startup) bootstrapped. We have zero expendable/savable income each month and it’s killing my soul. It’s so fucking frustrating knowing that a little time and some capital is all that stands between a better life for my family and I and being able to provide a better overall service out there over these kinds of shady as fuck knob gobblers.

rant¡

Client: "Can you add some logos to the homepage?"
Me: "Sure, I've just added it, take a look at staging."
Client: "Great, we can move it to live"

** 5 days later after it being moved to live and telling them I'm going on holiday. **

Client: "EMERGENCY change logo now, we need to change x logo. These logos look crappy too. How did this happen?"

Fuck this. I'm not employed by you, you don't have any right to speak to me like that. Especially after working tirelessly for your company.

**sent email back explaining how to upload files**

Told them not to contact me unless it's technically related.

Okay. So this Is my first rant. Don't you hate it when a client provides you with really crappy res images for a project? this tends to happen a lot...

Monday morning: The last straw.

After talking about in a previous rant about how my client wants to fix bugs that keeps popping out after bug fix.

Today I discovered, that all C-levels, worked all Saturday to "fix my code" because it "didn't work" and we "needed bug fixes not pretty things".

The app version I was working on for the last week is gone. Without mentioning that their "CTO" wrote a fucking crappy code to disable features that I added, breaking the build step.

This shit is enough for me, I'm done!

I'm fucking tired of putting my efforts into bug fixes.

5 years of web. I never had a client that likes to keep it's crappy slow piece of shit product on the market in the exact same way it is.

If they didn't sell it to state employees (and good luck for them if they do not use it) their product would be dead.

That's the only way they get money: bids. And the minimum a state pays is 15 MILLION.

And they don't have 90K to pay another dev to help creating a new product.

Their CEO fucking REJECTS anything that's not a bug fix. Once he said to our PM:

"It's pretty and more fast, but wasn't this way that made me rich"

I'm thinking I'm getting another client, seriously. Everyday the same thing breaks and they already know the fucking answer:

WE NEED TO FUCKING REFACT

CREATE A NEW FUCKING PROJECT

This shit is making crazy. I can't sleep. I can't eat and I'm always fucking tired, no matter what I do.

I need to stop working for Brazilians.
I'll try US, Canada or somewhere in Europe.

long time listener, first time caller. I love designers. seriously. I love getting a nice juicy Figma file and not knowing how the heck I'm going to do half the wild stuff in it, but it's beautiful, so I'll figure it out. Go ahead, send it to the client. But designers who learn how to use something like Elementor or one of those crappy kitchen-sink themes, call themselves developers, and win work with clients I share with them. I'm the one fixing everything when that crap breaks. I would never in a million years present myself as a designer, even though I know I know a damn sight more about design than they do about dev. I get it, everyone needs to make a buck, but every time this happens it makes me sick to my stomach. We're on the same team. I always, ALWAYS, go to the mat for good design. Why don't more designers have an equal amount of respect for us? Design phase always goes over deadlines and we always have to pick up the slack to make the hard launch date. Well, now I'm just rambling.

Normally I don't give a shit when I lost a job opportunity.

But dude, this year everything is bad as fuck. I moved out (yet again) to marry and start a new life.

And as I said a previous Rants, I got a client that just made me lost another client when they started to get shady. For almost a god dam month now, I can't find even a crappy job.

This never happened. I got more than 10 opportunities. A handful of interviews, a few tests and none of them gave me a job.

Now I have one week to get married.
The money I saved whent to all expenses. And now my anxiety is kicking in like it never did in years.

I really don't know what to do and I
can't fucking sleep.

Our approach is to get a loose feel for what the client wants, lift some visuals from Theme Forest then spend the next few weeks persuading the client to use our crappy server rather than their preferred AWS solution. Then once the project is behind schedule we break the work down into disparate tasks each of which gets a single line brief from the PM (such as 'create admin' or 'do css'). These then get assigned to different devs with no consideration of their skillset. The PM is available for 10 mins every day to answer queries, the rest of the time our devs are expected to work autonomously. Meanwhile we'll tell the client that we're back on schedule and arrange a demo for an impossibly short deadline. We have the mantra ”dont worry about it” which the PM uses to quash any dev's concerns up until the day before the deadline at which point we'll swap some devs on to unrelated work whilst others concentrate on getting "just the pages the client wants to see looking right" (we have a policy of making it look like it works before it actually does.) Following the demo we will announce all the missing features we had forgotten about from the initial undocumented agreement and set the project aside whilst we service another client.

I told you fucking moron clients doing that "little" change would be complicated and in the worst case it would end fucking up your whole spaghetti crap. A really HUGE spaghetti monster of that you aren't aware because you guys don't know a shit about coding conventions.

*Clients call me complaining about their software is broken*

-Hey, we're in serious trouble. Our users aren't being able to see the proper calculated values. Why that little change had so much side effects?
- I already told you why.
- Can you fix it asap? Our clients are complaining.
- No. Deploy an old copy of the affected modules while you give me a prudent time to refactorize that crap.
- Refactorize?
- ...

I used to work in their place, 3 years later I quit that crappy job and decided to make them my clients. I escaped from the micromanaging thing but I didn't from their ugly practices.

Anyways, I have to fix this shit asap. Money talks, at least until I can find a better client.

We are all about structures, clean code and many other things that make our life easier, right?

Well... It's not all white and black...

As talked many times, projects can be rushed... Client budgets can be low at the start and only then grow...

Let me take an example:

Client X needs a tool that helps his team perform jobs faster. They have a $500 budget. So... Testing, clean architecture and so on - are not really a viable option. Instead, you just make it work and perform that task as needed. So the code has minimal patterns, minimal code structure, a lot of repetitive parts and so on.

Now... Imagine that 3 months pass by without any notice and clients are ultra happy with the product. They want more things to be automated. They contact developers and ask for more things. This time they have a bigger budget but short timeframe.

So once again, you ignore all tests, structure and just make it work. No matter what. The client is happy again.

A year passes and the client realizes that their workflow changed. The app needs total refactoring. The previous developer has no time for adjustments at this point and hires a new company. They look at the code and rants spill out of their mouth along with suicidal thoughts.

So... What would you do? Would you rant about "messy project" or just fix it? Especially since people now have a bigger budget and timeframe to adapt to changes.

Would you be pissed on such a project?
Would you flame on previous devs?
Would you blame anyone for the mess?

Or would you simply get in and get the job done since the client has a "prototype" and needs a better version of it?

---

Personally, I've been in this situation A LOT. And I'm both, the old and new dev. I've built tons of crappy software to make things work for clients and after years - they come back for changes/new things. You just swallow the pill and do what is needed. Why? Well, because it's an internal system and not used by anyone outside their office. Even if it's used outside the office - prototyping is the key. They didn't know if the idea would work or be helpful in any way. Now they know and want it done correctly.

I'm mostly .NET Dev, working on OCR thingy, but I started as Java, Android Dev. After my boss's crappy management and burning out our two mobile devs he has assigned me to finish one app. For past four days I've worked around the clock to finish as much of functionalities as I could but it simply wasn't possible, especially because project was still changing when though deadline was around 15.12.17. Yesterday I've done as much as I could and now we have to wait for the client to either accept it or break the contract.
To be frank, I think that losing money would be like a bucket of cold water for my boss. All of us, me and those two mobile devs I have mentioned earlier, are students. We have exams right now. "Senior" Dev is only year older and will soon be applying for his engineering degree. Year after year situation like this occurs and boss haven't learn a thing.

Best: working on a cool xamarin project for a few months with a very cool client which made me a better dev;

Worst: working on a shitty legacy web - a clusterfuck of technologies, crappy workarounds and even shittier clients for the rest of the year;

You send out an email to your client with corrections on the requirements they have sent you (you know, those crappy requirements we all get), basically explaining how their application should work. They thank you for being there for them. An hour later, you get an email from the client with questions on why the development is going so slow...

Wow.

So worked myself into stupor for a react-native app(first -time). It is the client part for large system ecosystem. Was rough at first but after initail field test and refactor to the code base it is in 95% stable form. This all happend in 2 months. During this time co-workers build rest of system in node and other backend magic sauce 👩‍💻 .

My app has sibling app to collab with. I make a note (early in the development of this sibling app) that the ui is not working for the use case and get in a heated debate with co-workers. Concede 🙌 that it is not my part of the system and leave it to them, they blame the fact that no design was given. Fast forward to yesterday I get munched by client that wants to showcase the system to large company and has to struggle with sibling app. I tell him it is something "we" would look at in the next cycle ( covering for my coworkers) .

I feel shit and year now starts off with crappy feeling that all my hard work to get my app to decent version of itself is lost☠️ .

Getting started with my dissertation project for my degree. Using Java and Dropwizard for a backend service with a nice iOS client in Swift. Will make such a refreshing change from hacking crappy eForms together with jQuery and an Objective-C native bridge.