So before I resign from my job tomorrow I thought I'd talk a little about a couple of things at work that I won't ever tell my boss in person but are generally some of the reasons I want to leave.

---------- warning long rant ----------

1. The CEO of the company finds out I only have my learner's and take the bus, goes on to belittle me about taking the bus.

(It may have been meant as a joke but I was offended, and we don't have any actual HR to complain to)

First off my real reason for not getting my restricted is mostly related to the fact public transportation does the job it needs to, I don't really complain unless the planning is fucked up (Adele concert rant lol) but typically I don't need a car. The other reason is because with a car I'd have to wait in traffic 1-2 hour each way. Also cars cost money which I don't have.

2. CEO buys himself and general manager brand new Range Rovers, you know those giant monstrosities box jeep looking things.

I hate this because I earn $31k, those things probably cost around $50 each (so typically 3 years worth of my wages).

When I had a talk about my contract at the 6 month mark, the general manager (my boss) said he wouldn't budge on my salary (yet they buy these jeeps)

3. I live way too far from work and because of it being Auckland and the current inflation for house prices, the rent prices have also increase, I wouldn't be able to get a house closer to home nor rent with minimum wage :(

4. Though it's not too necessary they mask that the app was made by me, whenever I see an email about the app to potential clients they refer to be as this app guy, and during their presentations they don't really include as part of the reason this app has been developed ( aside from my boss being the client, I came up with some interesting ideas to turn their paper form of the process they use into a digital one, I also did research for the specific topics, something I could have just asked for instead).

5. Old fashioned way of looking at so called "IT", they added fixing computers to my contract which I dread, especially since I'll be close to a deadline and then I get a call to fix someone's computer...

6. They don't seem to want to expand their "development team" to more than one person.

When I give my resignation I have to stay here for a month and I bet people will start to act differently around me, my likely my boss and the CEO. I think the other people that work will understand, given my situation.

I'm planning to for the last month to only do planning for the app they want me to work on, UML diagrams, use cases, Sprint planning (albiet, only developer here lol). Research on the third party libraries we need for the app and generally give the next guy the easiest path to getting the app done.

I want to do this because the Android and iOS app we're done via cowboy programming in a sense. (I don't have too much in terms of documentation and planning aside from a Microsoft planning website setup with to-do of which features are done for the iOS and paper Todo for the Android app.

Alright long rant over, I've got it all written down, glad I'll be leaving this place.

One of my potential clients insisted we guarantee that the software we build will be bug free for a year. Was almost tempted to ask if they'll be OK if it crashes and burns after that.

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

Almond: Look at these stats - our signup process sucks! We really need to make it better.

Boss: Yeah, maybe at some point. It doesn't affect live running though. Leave it for now.

<1 month later...>

Almond: These stats are getting worse. I really think we should redesign this to do x, y and z and avoid a, b and c.

Boss: Yeah, we probably should do at some point, but there's no rush. You can work on it if you really want to, but only if there's nothing else going on.

<2 months later...>

Boss: I'VE JUST SPOKEN TO TWO POTENTIAL CLIENTS, BUT OUR SIGNUP PROCESS SUCKS SO THEY'RE GOING ELSEWHERE! WE NEED THIS FIXED NOW!! WHERE ARE YOU ON THIS? CAN WE GET IT DONE AND DEPLOYED BY FRIDAY?!?!

How to offend potential clients with sales emails:

“Hey again, <name>!​

Don't understand TikTok? Don't worry - you're talking to a Gen Z now.

I wanted to follow up on my previous note and see if you had any availability this week or next week to connect.”

Apparently not interested and not responding means you must be too old to understand those meddling kids and their internet toys.

Is it normal for your boss to sell a product when it is only half completed and pick arbitrary deadlines to demo it to potential clients?

It's cool.

I have less than four weeks before I have to have my project production ready

But why not make me waste my time in useless web based fucking trainings for bullshit HR issues I'll never deal with.

"Don't give gifts of more than $100 to potential clients!" Shut fuck up I don't work with clients.

Piss off and let me do my job.

One job I picked up was for an IoT Start Up. It was quite interesting work, reporting to the technical director, who was an electronics engineer, who was designing the hardware himself, they had a couple of firmware guys already, and just needed someone to take care of the software.
So they said they needed something in Azure that they could stream their data to and provide analytics for their clients. It had to be Azure, and it had to be Azure Native, and was to be Multi-client, as they had a deal with Microsoft to showcase how well Azure works in the IoT space at an exhibition/conference in 3 months time.
So I worked flat out for 3 months, on a whole variety of technology, from C++ to get the radio packets from their IoT chip, Python to run on the hub to take the data from the C++ and stream it to the cloud, Azure IoT Hubs in every continent to receive the data and store it an a Cosmos DB, and then Power BI analytics wrapped up in an Angular front end that the clients could log into.
Got it finished 2 days before the show, and they were so pleased I got flown business class to Singapore to be on the stand and talk to customers.
The first sign of trouble was when we arrived at the show to find we just had one of those little circular tables with two stools in the middle of the floor, about two feet across and no power.
No problem, I was able to sort that, swapping laptops in and out.
Microsoft were really happy with what we had, and couldn't believe I had thrown it all together in 3 months.
We picked up a potential customer for the system, a major Asian Telecoms company.
Then when we got home, the CEO swooped in. I had never met this guy before. Imagine one of the VC guys from Silicon Valley, or the CEO from the IT Crowd. You get the picture. Could talk the hind leg of a donkey, and real street smart, but no brains. He insisted on "taking it from here" and flew alone to strike the deal with the customer. Came back with an MOU in his pocket and said to me, their guys will be in touch with you.
Then I got a call. Can you send us the source code and tell us how what servers we have to run this on?
Um, its cloud native.
No, we can't use a cloud it has to be on our servers - your CEO told us that was no problem..
He hadn't even taken the trouble to find out what it was we had built, and what he was selling.

!rant
I am on vacation from my full time job this week. I wanted to use this week to write a PoC for a potential customer of my side business. really interesting project for me.

potential customer is a window and door manufacturer and needs an application to manage their racks.

their ERP system already has a simple rack management but it is only useable in house.

they want the drivers to be able to scan racks they deliver to a customer with a native app and they want to have a webapp for the customers to see racks that are assigned to them as well as reporting a rack ready for collection. And that all needs to be in sync with their local ERP system.

as i am a .net guy i decided to go with the abp framework (because it got recommended to me) and xamarin for the native app part (because i have experience in this).

i have now spent 4 days implementing this and it has been so rewarding. the framework is so powerful and it's template saved me endless hours.

i even wrote a very basic connector service which synchronizes data between my app and the clients ERP system. Just one way until now because of time issue, but i learned to scaffold an ef core with db first. It is noticable that the ERP system is 2-tiered - meaning the clients directly talk to the db.

Tomorrow i will implement the xamarin client.

4 days just coding what i want to. choosi g my own velocity and making my own priorities without any interruptions or discussions and a bunch of new things to learn.

Probably wasted half a day because of stupidy (implemented some bugs) but fixing and learning is part of the journey and i lime that part, too.

i am so relaxed right now 😁 just wanted to share this without a real reason :P

(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.

It's cool finally seeing real world feedback for something you developed and programmed yourself, I'm still in college and I'm trying to start a company with some software I came up with, and it's being taken very well from potential clients!🙏🏻

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

Got contacted by a potential client whose job I had bid on. Spent a couple of minutes frantically studying his specification and preparing my discussion.

Turns out the job was fake. He wanted me to create a new profile, verify it with my white European identity and then let him use it to approach Western clients.

The best part? I'm as Asian as he is, and all my profile pictures bear witness to that fact.

Some people smoke some really special stuff...

I hate being able to hear my boss in meeting with potential clients. Promising the earth then when the meeting is done tell me we have a week to make it. Not only that but then ask me what half the stuff he's sold actually is and does!?

[Blue pill]
stay in my current workplace [approaching the 10yrs mark], with an agreed salary and seniority raise, with a high probability of losing my current project [which is really fun!] in Feb next year and having to switch to another one, but keep all the benefits

[Red pill]
switch full-time to contracting with a potential to reap big bucks [x2-x4] and be free to juggle as many clients as I like, dictate my terms, become a shareholder, but lose all that warm and cozy certainty guaranteed by my current employer

A potential client wants me to fix a critical bug on their app. She wants us to book a call so she can explain the issue to me.

Because so many clients have wasted my time in the past, I want to charge her some $$$ for the call. However, if the gig goes through, it’ll be deducted from her bill.

Does this make any sense?

Real, seriously honest feedback wanted.
What do you do when you are stuck at a place that has potential but it is being run by someone with the wrong idea?
For example: not to toot my own horn, but I shine at front end Development. Not just slicing up designs, but seriously creating amazing user experiences. And honestly, there is no shortage of work for that ... every client we have has an expectation that their site or application will look awesome. And we have some very big clients.
That said, the manager truly believes that we are all inter-changeable and should have no preference. As a result, John Doe over there who has zero ability in front end gets tasked with building the front end of what should be an amazing app... while I eventually get tasked with some sitecore bullshit that I have no interest in.
And it goes on and on and on.
It is no coincidence that anytime the dice land on me for front end, it wins an award and always ends with an awesome thank you from the customer.

I am not sure what to do, because it just makes no sense to me. And this is just one example of the mismanagement.

Any help?

Im having a sort of dilema. I recently started taking freelance work for web developement (and design ack) and Im uncomfortable with the state of the industry. Ill explain: Say if I bid a client for a simple 1-3 page site w contact form (a new page, not migration) My suggestion is to use djangocms, django, or just static html/css/js (ie bootstrap), which produces clean, fairly secure, and fast sites. Of course I can throw a templated unoriginal wordpress site together in a few hours 2 days latest, so I offer that option as a sidenote on the bid, charging almost 2x more. For some reason I dont understand they choose the wp shitshow. I explain all the reasons that not the way to go( which I wont list, if u dont know, u never used it. google up) but they dont care abt the details, they rather pay more for shit job. OFC I reluctantly deliver what they want, but as a result my portfolio is full of unoriginal shit Im not happy showing off. I have a few sites Ive done on the side my prefered way, but they not deployed and sit in my github for all intents n purposes unviewable to potential clients.
I want to be proud of my portfolio, and it to be a representation of what Im capable of. BUT, I gotta eat, and work is better than no work.

There are so many "wordpress designers" oversaturaring the field and it lowering the overall standard of what we are capable of. I just begining my dev journey, but if I cant have a body of work Im proud of, theres no way I can see doing this the rest of my life, and that makes me really sad. My love of developing, coding, and IT/computers in general drove me to change careers from audio engineering to web development, and the fact that this fucking mr. potatoe head of a CMS is slowly turning that love into hate really pisses me off. So Im ending this !rant looking for hope.
Your thoughts?

I have two potential client meetings next week. The first one now knows she needs a website (but I have no clue what her budget is), I think she wants me to host the site as well as do site maintenance. The second potential client I'm working using the barter system (but I think she will end up owing me some money at the end). We will see how they both go.

Have this iOS maniac/UI guy/hustler at my office. (Refers to my first Rant,he's the fucker who always try to shove his iPhone to my face.) Hats off to him for knowing how to generate passive income and his hustling skill. But I hate that fucker. He always like to start a debate. He's always doing his sidejobs all the time. He sells staff online(even fidget spinner). He also does wedding photo shoots. Heard from a friend, he's a mediocre photographer but gets client by giving his potential clients lower prices than his competitors. He got a few connections and somehow always doing websites for his own client by going to codepen and copy pasting JavaScript from here and there. He doesn't know shit about programming. That fucker doesn't even know about closures. He literally doesn't know shit. Yet try to debate about with us regarding programming (wtf?) Always trying to get us to help him with his side paid jobs -when he encountered an error,he will immediately bug us- sometimes would interrupt us while we are busy with the company's stuff. If we don't help, he would slightly mock by saying things like "it's ok...I understand you guys are not that experienced yet..etc". The senior dev was pissed off the other day and emailed a super detailed complaint to the HR.
Note : He gets paid more by his photoshooting jobs on the weekend, he's only at this job for his future citizenship application. That fucker. He's the type of fucker that will definitely gets rich but gets hated by everyone.

Not 100% hackathon, but I was once in one of those weekend coding challenges - aka: have idea, implement MVP, present to a Juri and get a chance to win a prize.

So, to start things off, you had a few months to prepare the idea, gather a team (minimum of 2, maximum of 5 per team) and register.

I gathered a few friends from university, that was cool. We were 5, I had the idea already, they agreed. I started talking business with some partners/governmental stuff (no time to explain all, ask in comments if you want to know).

2 weeks pass by after registering, still 1+ month before the event, 2 of the team members let me know they want to focus on university, so they cannot spend a weekend on this competition. Well, ok, still 3 people, no worries.

Fast forward, 1 week before the competition, another one says he won't be in town, we're 2. Still enough, we meet the requirements, it's just for the fun anyways.

Day 1 of the competition, I'm there waiting for my other teammate. Call him countless times, doesn't pick up. Later tells me he's sick.

I tell the organization about it. They asked: You can continue, but it's fine if you give up now.
> Yo, dafuck you mean give up? I'll die before I give up. It's for the fun anyways, worst case scenario I spend a nice weekend doing what I like *shrug*

So there I am, all alone, doing a first MVP of the mobile app in Android (without any prior android experience, and don't ask me why I chose to do mobile app for that project, was stupid back then).

Lots of nice things there, overall a good weekend, networking, food, gadgets and stuff like that.

Juri day, put on pretty clothes to present my super idea alongside my super MVP of the ugliest mobile app I've seen.

Judge 1: likes the idea, ugly app.
Judge 2: likes the idea, ugly app, could improve and work on the concept, etc
Judge 3: Lots of business questions, to which I came prepared with already potential clients and partners, liked that part although seemed a little confident of it working or not.
Judge 4: "Yo, that's the most stupid thing I've heard, not even gonna ask questions, that's just stupid"
Judge 5: A teacher in my university, the one to actually tell me about this competition, kind of like that meme from "How to train your dragon" where he does the thumbs up thing. Obviously the app sucks, but understandable, no one in the competition has much experience, bla bla bla

---

Final decision: No prize, fuck the idea, got a participation amazon voucher of like, $10 usd. *shurg*

--

Fast forward a few months, my aunt who shared the idea with me and who i was working with before the competition, sends me a link for an article on FB messenger.
The company where that MF judge worked at build a system exactly like the one I presented, claiming it was a very innovative idea. Never heard of them again, it was a consultation company (Deloitte), so I assume they didn't sell it well and dropped it also.

Moral of the story: I guess there's no moral, just have fun.

This is more of an advice seeking rant. I've recently been promoted to Team Leader of my team but mostly because of circumstances. The previous team leader left for a start-up and I've been somehow the acting Scrum Master of the team for the past months (although our company sucks at Scrum generally speaking) and also having the most time in the company. However I'm still the youngest I'm my team so managing the actual team feels a bit weird and also I do not consider myself experienced enough to be a Technical lead but we don't have a different position for that.

Below actions happen in the course of 2-3 months.

With all the things above considered I find myself in a dire situation, a couple of months ago there were several Blocker bugs opened from the Clients side / production env related to one feature, however after spending about a month or so on trying to investigate the issues we've come to the conclusion that it needs to be refactorised as it's way too bad and it can't be solved (as a side note this issue has also been raised by a former dev who left the company). Although it was not part of the initial upcoming version release it was "forcefully" introduced in the plan and we took out of the scope other things but was still flagged as a potential risk. But wait..there's more, this feature was part of a Java microservice (the whole microservice basically) and our team is mostly made of JS, just one guy who actually works as a Java dev (I've only done one Java course during uni but never felt attracted to it). I've not been involved in the initial planning of this EPIC, my former TL was an the Java guy. Now during this the company decides that me and my TL were needed for a side project, so both of us got "pulled out" of the team and move there but we've also had to "manage" the team at the same time. In the end it's decided that since my TL will leave and I will take leadership of the team, I get "released" from the side project to manage the team. I'm left with about 3 weeks to slam dunk the feature.. but, I'm not a great leader for my team nor do I have the knowledge to help me teammate into fixing this Java MS, I do go about the normal schedule about asking him in the daily what is he working on and if he needs any help, but I don't really get into much details as I'm neither too much in sync with the feature nor with the technical part of Java. And here we are now in the last week, I've had several calls with PSO from the clients trying to push me into giving them a deadline on when will it be fixed that it's very important for the client to get this working in the next release and so on, however I do not hold an answer to that. I've been trying to explain to them that this was flagged as a risk and I can't guarantee them anything but that didn't seem to make them any happier. On the other side I feel like this team member has been slacking it a lot, his work this week would barely sum up a couple of hours from my point of view as I've asked him to push the branch he's been working on and checked his code changes. I'm a bit anxious to confront him however as I feel I haven't been on top of his situation either, not saying I was uninvolved but I definetly could have been a better manager for him and go into more details about his daily work and so on.

All in all there has been mistakes on all levels(maybe not on PSO as they can't really be held accountable for R&D inability to deliver stuff, but they should be a little more understandable at the very least) and it got us into a shitty situation which stresses me out and makes me feel like I've started my new position with a wrong step.

I'm just wondering if anyone has been in similar situations and has any tips or words of wisdom to share. Or how do you guys feel about the whole situation, am I just over stressing it? Did I get a good analysis, was there anything I could have done better? I'm open for any kind of feedback.

Hey, freelancer programmers, web developers, etc. I need your help. I’m writing a “Mother of All Blogs” post about why clients should a) pay you for your work and b) expect to pay you your asking rate. I’m trying to make the argument more forcefully that you get what you pay for with this work and that when you cheap out you only hurt your business bottom line. So, what are your experiences (positive and negative) or points that you would make to a potential client, who wants you to work super cheap or even for free, that you find are irrefutable about this topic? I want to include as many as I can! Thanks.

So i got this service i made for fun and learning. Theres many providers in it for money, not me, only a little (lets not lie to ourselves).
Id just like to have a handful of happy clients to make it pay for itself so i dont lose money.
I have no idea how to advertise or gain clients. Those potential clients i cling with are from US and the server is in EU, and i wont convince anyone to buy something i wouldnt buy myself.

I suck at marketing.

I just finished posting this but think it deserves its own post.
If you're creating a business or "startup" (as people like to call it these days) don't assume the idea is novel or investors will just jump on board. Focus on the business fundementals, money and cash flow, even before launch, unless you can afford not to. But really you can't afford not to. Selling before launch means that you're effectively doing two things 1 you're collecting new customers and income for the business and 2 you're. raising awareness at the same time. Obscurity is death and failure.

Get you a good sales team and marketer when the time is right.

Have a year of runway.

Identify the sites and groups your target audience and investors frequent. Start conversations now, buzz is the hardest thing to generate.

Start building relations with customers and potential clients now. Discuss launch, ask them if they'd be willing to pay up front before launch, in order to secure a "lifetime membership", offer it as an early opportunity and charge extra. Giving a discount out of the gate is a mistake B/c it says to potential investors that you don't think it's ready or worth it yet. Of course if it's between making 1. Some money or 2. No money, don't let it be a deal breaker, offer a discount. Going from no clients to any clients is a BIG deal. If you can do 1 you can make it to 10, if 10, you can reach 100, we etc.

No one likes asking for money and yet it is as important if not more important than development.

Looking for potential clients on Upwork is like finding a holy grail these days.

Cheap clients with laughable budgets and high expectations on the right.

"Devs" and "Designers" with questionable skills who will work for the lowest rate possible on the left.

And don't forget the ever growing service fees and absurd measures like turning your profile private if you don't make any income in 30 days. Suuure, that's totally going to help anyone who isn't willing to work with low rates.

I am getting done with Upwork. Back on Elance I managed to get a couple of really good clients for long term projects and good commissions. Here it's impossible, even with lower rates.

You're competing against people whose portfolio involves changing a few colors for a envato template or logos made of stock graphics, and they are still more likely to be hired over you because they are willing to work on a t-shirt design for $4!

Networking is where is at. Getting contacts, talking to people, force yourself to introduce to companies as a potential asset.

That's how you get the good projects, right?

... Right, folks?

FOMO on technology is very frustrating.

i have a few freelance and hobby projects i maintain. mostly small laravel websites, go apis, etc ..

i used to get a 24$/ month droplet from digital ocean that has 4vCPUs and 8GB RAM

it was nore than enough for everything i did.

but from time to time i get a few potential clients that want huge infrastructure work on kubernetes with monitoring stacks etc...

and i dont feel capable because i am not using this on the daily, i haven't managed a full platform with monitoring and everything on k8s.

sure u can practice on minikube but u wont get to be exposed to the tiny details that come when deploying actual websites and trying to setup workflows and all that. from managing secrets to grafana and loki and Prometheus and all those.

so i ended up getting a k8s cluster on DO, and im paying 100$ a month for it and moving everything to it.

but what i hate is im paying out of pocket, and everything just requires so much resources!!!!

Companies that pose to be successful and you come across awesome reviews about them, until you try their services out only to find that they have been scamming others. This is a company called Host4Geeks, I was truly impressed by the company until I dug deeper.
It saddens me that companies like these who have huge potential work on providing an awful service while they could earn a lot more if they just provide a better service.

My personal experience was a little different and partially my fault. Someone introduced me to their service and I liked their Reseller service, I tried it out for some of my clients, it was only until I decided to move on that H4G locked down my account and content barring me from attempting any sort of content transfer.

This is Host4Geeks. Beware.

So the project I have been working on for the past 5 months was finally released yesterday with only very minor problems, this stemmed from both programming side, and users entering data incorrectly.

It has been a rather hectic 5 months. I've had to deal with crap like:
- clients not knowing their own products
- a project manager that didn't document anything (or at least everything into a Google Slides document)
- me writing both requirements AND specifications (I'm a dev, not a PM)
- developers not following said specifications (then having to rewrite all their work)

But the worst thing I think would be the lack of vision from everyone. Everyone sees it as a "project" that should be get it over and done with rather a product that has great potential.

So with the project winding down, and only very few things left to fix/implement. Over these 5 months I learned a lot about domain driven design, Laravel's core, AWS, and just how terrible people are at their jobs. I imagine if I worked with people who gave a damn, or who actually had skills, I probably wouldn't have had such a difficult project.

Right now I'm less stressed but now feel rather exhausted from it all. What kind of things do you to help with the exhaustion and/or slow down of pace?

Anyone else get told their rates are too high (by potential clients)? Too low (by fellow freelancers)? How does one put a value to their time and still stay market competitive?

Details: USA only. Not on any platforms such as freelancer, upwork, or fiver. Cost of living is Portland Oregon standards. Ask for any other details.

Looking for thoughts, recommended readings, any helpful input would be awesome.

Design in Motion: Real-Time Rendering's Impact on Architecture

Architecture, a discipline that once relied heavily on blueprints, models, and lengthy render times, has undergone a revolutionary transformation in recent years. The advent of real-time rendering technology has fundamentally altered the way architects visualize, present, and interact with their designs. This paradigm shift has not only enhanced the creative process but has also empowered architects to make more informed decisions and create immersive experiences for clients and stakeholders.

Real-time rendering, a technological marvel that harnesses the power of high-performance graphics hardware and advanced software algorithms, allows architects to generate photorealistic visualizations of their designs in a matter of milliseconds. Gone are the days of waiting hours or even days for a single rendering to complete. This acceleration in rendering time has not only expedited the design process but has also encouraged architects to explore multiple design iterations rapidly.

One of the most significant impacts of real-time rendering on architecture is the ability to visualize a design in various lighting conditions and environmental settings. Architects can now instantly switch between daytime and nighttime lighting scenarios, experiment with different materials, and observe how their designs respond to different seasons or weather conditions. This level of dynamic visualization offers insights into how a building's appearance and functionality evolve throughout the day, contributing to more holistic and thoughtful design solutions.

Moreover, real-time rendering has transformed client presentations. Architectural concepts can now be communicated with unprecedented clarity and realism. Clients can virtually walk through spaces, observing intricate details, exploring different angles, and even experiencing the play of light and shadow in real-time. This immersive experience fosters a deeper understanding of the design intent, enabling clients to provide more targeted feedback and make informed decisions.

The impact of real-time rendering on collaboration within architectural teams cannot be overstated. Traditionally, architects and designers would need to wait for a rendering to complete before discussing design changes or improvements. With real-time rendering, team members can make adjustments on the fly, observing the immediate effects of their decisions. This seamless collaboration not only enhances efficiency but also encourages interdisciplinary collaboration as architects, engineers, and other stakeholders can work together in real-time to refine designs.

The integration of virtual reality (VR) and augmented reality (AR) into the architectural workflow is another transformative aspect of real-time rendering. Architects can now create VR environments that allow clients to step inside their designs and explore every nook and cranny. This not only enhances client engagement but also enables architects to identify potential design flaws or spatial issues that might not be apparent in 2D drawings. AR, on the other hand, overlays digital information onto the physical world, facilitating on-site decision-making and construction supervision.

Real-time rendering's impact extends beyond the design phase. It has proven to be a valuable tool for public engagement and community involvement in architectural projects. By creating virtual walkthroughs of proposed structures, architects can offer the public an opportunity to experience the design before construction begins. This transparency fosters a sense of ownership and allows for constructive feedback, contributing to the development of designs that resonate with the community's needs and aspirations.

The environmental implications of real-time rendering are also noteworthy. The ability to visualize designs in various environmental contexts contributes to more sustainable architecture. Architects can assess how natural light interacts with interior spaces, optimizing energy efficiency and reducing the need for artificial lighting during the day.

In conclusion, real-time rendering has ushered in a new era of architectural design, propelling the industry into a realm of dynamic visualization, immersive experiences, and enhanced collaboration. The ability to witness designs in motion, explore different lighting conditions, and interact with virtual environments has redefined how architects approach their craft. From facilitating client presentations to fostering sustainable design solutions, real-time rendering's impact on architecture is profound and multifaceted. As the technology continues to evolve, architects have an unprecedented opportunity to push the boundaries of creativity, efficiency, and sustainability in the built environment.

Hey guys, I need your honest opinion. What do you think about service provider office location? Situation is that Im looking for an office for me and two employees. Found one good location which is perf in the inside: has a private modern office, meeting rooms, skype rooms, nice kitchen and etc. However its ugly af from the outside: U need to get inside this hospital looking soviet building and take an elevator to the 8th floor to see all the modern stuff. While price seems a bargain, Im kinda afraid of how we could come across potential clients who would visit us for a meeting. As a potential client how would you judge service provider (in this case android dev company) which has nice offices in the inside but ugly af building from the outside?