|
I am learning web development and I want to know that I am ready to do freelancing. so I need to find free projects to do. is there any way to find free projects. and how do I know that I am ready to do freelancing?
|
|
|
|
|
Finding ways to contribute to open source on GitHub - GitHub Docs[^]
Not sure how anyone knows they are ready to "freelance". I would suspect that your skill set would need to be strong enough and marketable enough to go it on your own.
I am sure there are a lot of websites that would help you on freelancing and everything that involves, etc.
|
|
|
|
|
|
chamith janaka wrote: how do I know that I am ready to do freelancing
You don't, it takes
Resources - you need to eat while you are trying to find clients
Contacts - apart from the various freelancer type web sites you need to build up a network of clients/contacts
Rhino Hide - can you take being rejected for the first hundred or more approaches you make
Admin Skills - after all you will be running a company of some description
And that does not even touch on the analysis, development, deployment, documentation and support skills you will need to bring to the market.
Good luck!
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
chamith janaka wrote: I am learning web development and I want to know that I am ready to do freelancing
If you are learning, you are not ready to freelance. Freelancers are brought in with the expectation that they have high levels of skill, knowledge and experience - and will hit the ground running. Which justifies their remuneration being much higher than permies.
Any company that is prepared to to take on junior freelancers is, almost certainly, expecting to pay peanuts; provide zero training and offload you at the drop of a hat.
My advice would be to get a 'real' job, with a company that is prepared to commit to your development over the next 2-3 years.
|
|
|
|
|
Aren't free projects and freelancing antithetical? How does one expect to get paid working on something that is given away at no cost?
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
|
|
|
|
|
Hook up with a non-profit charity and help them out with a web site.
>64
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
You're not ready.
Everybody will let you work for free. If you were "ready", you'd know this.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I installed VS2019 on a new PC and when I open the code there are these "structure lines" all over the place. They're dotted horizontal and vertical lines that seem to "match up" code blocks.
Bloody annoying as @*@&.
I've Googled and went through the Settings but I can't figure out how to turn this "feature" off.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Tools > Options... > Text Editor > General and uncheck "Show structure guide lines" at the bottom (VS2017).
|
|
|
|
|
It's already unchecked
I've toggled it on/off multiple times. It seems to have no effect
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
modified 6-Jul-21 14:35pm.
|
|
|
|
|
I'm at a loss. A hack might be going to
Tools > Options... > Environment > Fonts and Colors > Structure Guide Lines
and setting their color to that of your window background 
|
|
|
|
|
are you using ReSharper, or something similar?
|
|
|
|
|
I love those structure lines. If I could marry them, I would.
|
|
|
|
|
Not sure about the marrying part, but 'I do' like them. 
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
My kids actually used to say that all the time to me.
Me: I really love that car!
kids: Do you love it so much that you would marry it?
cute
|
|
|
|
|
So what do they say when you tell your kids you love them?
|
|
|
|
|
Queue up 'Dueling Banjos- YouTube'[^]
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
And I though it was a Monkey Island 3 video...
GCS d--(d-) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Well that took an unexpected turn...
|
|
|
|
|
Ah, thought at first you were referring to the colored crap on the scrollbar that makes it difficult to see the handle when there's been lot's of changes. IMHO, the structure bars are very useful.
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
I haven't seen them, but maybe "too many structure lines" indicates "not enough structure"?
|
|
|
|
|
You probably also want to turn off highlighting the current line.
|
|
|
|
|
I'm working on the rasterizer portion of my truetype code, for which I found some public domain code that partially works - the parts I need anyway.
it's really hard to follow C code, so I'm porting it to C# before backporting it to C++ so that I can really understand it.
This isn't the only time I've done that. In fact, I often find myself going this route when coding something based on a codebase I don't understand at first.
Do you do this?
More I guess I'm curious how y'all go about decoding code that is either more complicated than you can readily understand, or too ugly to readily understand?
I port.
Real programmers use butterflies
|
|
|
|
|
What I like to do is create some integration tests that exercise the code paths and then debug the code to see what it's doing. The advantage of that is, with minor changes to the integration tests, I can verify my new code. That said, I do live in a world where integration testing is probably easier.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
