Client: we want X.
Dev: Quote for X.
Client: We only want to pay x.
Dev: Requote for x.
Client: approved x.
Dev: Deliver x.
Client: where is X we asked for X.

... perspective of project scope matters.

I like what I do for a living.

I build software, mostly from scratch or early stage products. Those are different industries, different companies, different technologies, frameworks and languages. Systems that impact economy in a different way.

When I develop software I am picking different parts of same project and try to understand how companies earn money and what are advantages of their software. What are required regulations and requirements to sell the stuff.
How the money flows from client and what they’re changing for. I especially try to understand stuff from business perspective.
When I pay my debts and luckily be still alive but unemployed and with minimum income from stocks / properties rental I will have plenty of time to duplicate many of those businesses.

I picked programming cause it’s touching all parts of economy basically without any skill requirements and certifications. It’s young impactful industry that is luckily not yet regulated. You just need laptop, like to solve puzzles and have plenty of free time and you can create everything. Never forget about it.

Cloud corporations try to make people think differently but it’s just that simple.

(long post is long)
This one is for the .net folks. After evaluating the technology top to bottom and even reimplementing several examples I commonly use for smoke testing new technology, I'm just going to call it:

Blazor is the next Silverlight.

It's just beyond the pale in terms of being architecturally flawed, and yet they're rushing it out as hard as possible to coincide with the .Net 5 rebranding silo extravaganza. We are officially entering round 3 of "sacrifice .Net on the altar of enterprise comfort." Get excited.

Since we've arrived here, I can only assume the Asp.net Ajax fiasco is far enough in the past that a new generation of devs doesn't recall its inherent catastrophic weaknesses. The architecture was this:

1. Create a component as a "WebUserControl"
2. Any time a bound DOM operation occurs from user interaction, send a payload back to the server
3. The server runs the code to process the event; it spits back more HTML

Some client-side js then dutifully updates the UI by unceremoniously stuffing the markup into an element's innerHTML property like so much sausage.

If you understand that, you've adequately understood how Blazor works. There's some optimization like signalR WebSockets for update streaming (the first and only time most blazor devs will ever use WebSockets, I even see developers claiming that they're "using SignalR, Idserver4, gRPC, etc." because the template seeds it for them. The hubris.), but that's the gist. The astute viewer will have noticed a few things here, including the disconnect between repaints, inability to blend update operations and transitions, and the potential for absolutely obliterative, connection-volatile, abusive transactional logic flying back and forth to the server. It's the bring out your dead approach to seeing how much of your IT budget is dedicated to paying for bandwidth and CPU time.

Blazor goes a step further in the server-side render scenario and sends every DOM event it binds to the server for processing. These include millisecond-scale events like scroll, which, at least according to GitHub issues, devs are quickly realizing requires debouncing, though they aren't quite sure how to accomplish that. Since this immediately becomes an issue with tickets saying things like, "scroll event crater server, Ugg need help! You said Blazorclub good. Ugg believe, Ugg wants reparations!" the team chooses a great answer to many problems for the wrong reasons:

gRPC

For those who aren't familiar, gRPC has a substantial amount of compression primarily courtesy of a rather excellent binary format developed by Google. Who needs the Quickie Mart, or indeed a sound markup delivery and view strategy when you can compress the shit out of the payload and ignore the problem. (Shhh, I hear you back there, no spoilers. What will happen when even that compression ceases to cut it, indeed). One might look at all this inductive-reasoning-as-development and ask themselves, "butwai?!" The reason is that the server-side story is just a way to buy time to flesh out the even more fundamentally broken browser-side story. To explain that, we need a little perspective.

The relationship between Microsoft and it's enterprise customers is your typical mutually abusive co-dependent relationship. Microsoft goes through phases of tacit disinterest, where it virtually ignores them. And rightly so, the enterprise customers tend to be weaksauce, mono-platform, mono-language types who come to work, collect a paycheck, and go home. They want to suckle on the teat of the vendor that enables them to get a plug and play experience for delivering their internal systems.

And that's fine. But it's also dull; it's the spouse that lets themselves go, it's the girlfriend in the distracted boyfriend meme. Those aren't the people who keep your platform relevant and competitive. For Microsoft, that crowd has always been the exploratory end of the developer community: alt.net, and more recently, the dotnet core community (StackOverflow 2020's most loved platform, for the haters). Alt.net seeded every competitive advantage the dotnet ecosystem has, and dotnet core capitalized on. Like DI? You're welcome. Are you enjoying MVC? Your gratitude is understood. Cool serializers, gRPC/protobuff, 1st class APIs, metadata-driven clients, code generation, micro ORMs, etc., etc., et al. Dear enterpriseur, you are fucking welcome.

Anyways, b2blazor. So, the front end (Blazor WebAssembly) story begins with the average enterprise FOMO. When enterprises get FOMO, they start to Karen/Kevin super hard, slinging around money, privilege, premiere support tickets, etc. until Microsoft, the distracted boyfriend, eventually turns back and says, "sorry babe, wut was that?" You know, shit like managers unironically looking at cloud reps and demanding to know if "you can handle our load!" Meanwhile, any actual engineer hides under the table facepalming and trying not to die from embarrassment.

hmmmmmm let me see.

Web based? lets do web based.

Do something simple like a basic crud app on web api format:
Do it with full authorization and authentication.
Start hard. Do it with pure golang using NOTHING but the std libraries.
Now, do it in a magic mvc framework like Rails or Laravel
Now do it on dotnet core
Now do it in django rest.

Watch the differences in all of them, sell your soul to something and now do it in Clojure. If you do it on a Scheme dialect or on Common Lisp my CMS admin will suck your whatever you have. Dude seems to be pretty good at it, we are trying to keep him from pulling tricks on the street but he insists.

Then add a React client with Typescript to get them basic ass endpoints to display nicely.

It should give you a fuckload of perspective amongst the different tools and way we do things and might make you appreciate the differences in paradigms required(pro points for doing modular in c# dotnetcore using different classlibs for the major points of the application using some crazy pattern like the mediator pattern)

I would hire a mfker that throws all this shit at me on a portfolio on the spot.

Well, I posted this rant a few days ago where I was expressing my desires to get a job as a Software Developer... Here I am again re-posting.

________________________________

FFS! Can I get a remote job as soft-dev?? I know a little bit of java, I mean I have a GitHub repo for a project if anyone wants to see what I'm doing.

If anyone knows or feel that can help me, please lend me a hand, I need to start working (to get real experience) and earn a little (prevent from starving in this fucking shithole country).

I'm not asking for money, I'm asking for a freaking job, a task, anything.

Little brief of my situation... I'm from Venezuela... Done!

Now for real, I'm a freelancer IT technician for almost 8 yrs, now I'm studying software engineering (8th Semester), I'm 31 years old, have a family (7 yrs old daughter, newborn baby boy), work is not flowing since the hourly price got high due to the economic crisis and clients are hiring people instead of outsourcing.

I'm not expecting to earn the minimum wage of UUSS, 150$/month can do the job! This due to the black market price of the USD (10X.000BsF so far), where 1$ represents the 1/8 part of the minimum wage here, to put it in perspective, toothpaste cost 200.000Bsf, 1/4 of the minimum wage.

Perhaps you will be asking yourself "Damn! so how do you do to survive!?" well, at least once a week a client calls and that saves the entire week, this isn't life my people, this is surviving... And if you don't believe me, I can show a receipt from the supermarket, and show you the average salary or my incomings.

Anyway enough drama and whining for today, I'm not doing this again in my life, I'm a person who achieves goals and earns what deserve (even this situation, I know that I deserve it for not thinking properly in the past, but we can't be victims of our past or do we?)

I started a company a while back that builds really simple wordpress sites and design for small businesses. I took a client on that needed things that were well above my skill level as a "programmer" and it's been equally frustrating and satisfying to consistently have the shit kicked out of me while spending hours trying to solve problem after problem. I've never worked for a company as a coder and one of the things I'm starting to wonder about is whether or not I'm "cut out" to be a programmer. I like doing it, but from a business owner perspective I don't know that I would actually want myself as an employee. My question is: does everyone feel like a ducking retard everyday they go at it with their job as a programmer?

Our client supposedly managed our Jira board yesterday in preparation for the release to live.

It was a mess. We have two people on this project - so our effective maximum workload is 10 days worth of tickets.

The current sprint plus the next have over 60 tickets in them, with the other "light" sprints having about 15 days worth in them.

I know you shouldn't get caught up over estimates too much, but they're in place for a reason.

The client really needs a reality check, and to be reasonable. When looking from a macro perspective he loses sight of all reason and scope, trying to grossly overfill what the two of us can handle.

A junior and student placement dev can only do so much.

I guess time will tell how realistic 16th April is..

I'm writing a couple of tutorials on web development, nothing really professional, just my perspective on explaining things from scratch.

It's funny how quickly things get hard to explain.
You try to explain web frameworks and you have to differentiate between client side and server side frameworks.

But some people don't know what client or server means.

So you try to explain what the client-server model is.

But then the word model is not clear to some people, it's like a jargon word in software, so you have to give some kind of explanation for the word.

And so on.

This complexity and layering of terms is normal on every science, but I feel terms deserve proper explanation and disambiguation, which isn't usually done.

So far I don't feel a lot of things are as complex as they are considered in an atomical sense, they are complex in the sense of requiring understanding of layers that are very simple in themselves.

It is quite a challenge to be the least obscure, to give explanations with the least number of possible interpretations.

So I had an interesting conversation with a "developer" from another org:
Me: "So I might have a new client. Their site really needs an update."
Them:"Let me see." *goes to perspective client site*
Them:"Wow, that's bad!"
Me:"Yep it hasn't been touched since 08"
Them:"No, that's not the reason. The reason it looks this bad is because it is made with php."

I have an opportunity to speak to a large and well mixed group of web designers and developers plus _clients_ of designers and developers. Part of what I want to cover is what affects the client/professional relationship and project(s) in both positive and negative ways. I want to include your (dev/designer) real world perspective on that. So, please share a positive and/or negative client behavior or experience that typifies how hard it is to work with some clients and/or easy it is to work with others. If you have a solution that works well for bad situations, I’d love to add that to my presentation as well. THANKS!