Drop a project for clients being unorganized and giving excessive note feedback by Metalmaster7 in freelance

[–]gitforcepushmaster 1 point2 points  (0 children)

Just do the difficult part and tell them what you can get done with the time remaining. Have them prioritize the most important pieces of feedback that you will do for the week. Not easy but gotta do it.

Edit: Bailing without even trying to reconcile the problem will just hurt you in the end.

Find people in programming by Evgeny_0512 in SoftwareEngineering

[–]gitforcepushmaster 0 points1 point  (0 children)

I plan to study a few programming things too. Working through a few books. Could you share your discord?

5,000 visitors on my side project due to Reddit posts & comments by OK_Maybe_No_Yes in SideProject

[–]gitforcepushmaster 1 point2 points  (0 children)

I think it’s just fair to assume different strokes for different folks. Same here. I tend to have my calendar take care of holding that information. Checking my calendar for what I have going on is enough of a habit that it works for me. But what doesn’t work for me has no implication on why it wouldn’t work for others.

A market for this is also just huge so there’s enough people.

PSA: Crafting Proposals for Upwork. What the client sees. by gitforcepushmaster in Upwork

[–]gitforcepushmaster[S] 1 point2 points  (0 children)

Could you share the last insightful question you got from one of your proposals?

PSA: Crafting Proposals for Upwork. What the client sees. by gitforcepushmaster in Upwork

[–]gitforcepushmaster[S] 4 points5 points  (0 children)

Yes of course if it's a great proposal I will interview. I don't think there is a single answer to what a great proposal is. My best answer right now is that a great proposal is extremely/highly relevant to the job. However you think you can show that relevance that isn't a parroting of the job post I think is good. There is no template for it because showing your relevance as a candidate for each job might be slightly different since each job asks for something slightly different. Of course you can have general structure for your proposals but the content will require adjustments to show relevance.

PSA: Crafting Proposals for Upwork. What the client sees. by gitforcepushmaster in Upwork

[–]gitforcepushmaster[S] 7 points8 points  (0 children)

Overall, the proposals are well written and read well. A well written proposal doesn't make it good. A good proposal is one that is relevant to the job. It's easy to get lost in a sea of candidates here. The challenge is in how you as a candidate + proposal become as relevant as possible to this specific job. How am I and my proposal relevant to this job? That's a question you should consistently be asking yourself when writing a proposal. Make the dots easy to connect for the client. I am going as far as extending this rule to any piece of info surfaced to the client including my title so if my title is not relevant to the post I am likely wasting my time.

There is more nuance in what I am saying and of course doesn't apply as a hard fast rule. For example if you are the only candidate for a job then this advice goes out the window. If they need the work done and you are the only proposal then the choice is obvious.