4 ms·
Pretty much everything with strict resource requirements or other reasons for aggressive resource use optimization: embedded, automotive, industrial control syt
by swatcoder 2y ago
Pretty much everything with strict resource requirements or other reasons for aggressive resource use optimization: embedded, automotive, industrial control sytems, games, operating systems, audio and other (soft) realtime media applications, hft, tools and frameworks for all these things, etc
But you'll note that most of these things are very sensitive to quality of work. That is not something that people find easily on freelancing platforms like upwork and so people seeking contract help for these things don't post their work their.
Instead, buyers generally reach out through established connections ("word of mouth", past coworkers, approved vendor lists) or fall back to hunting through Google and LinkedIn for firms/individuals that look impressive, hoping that the impression holds up during a requirements gathering, bidding, and estimation process.
Given where it sounds like you are in your career, your best bet might be to find work inside a contracting firm that can feed you gigs (they'll do sales, they may do project management, they may staff a team alonside you, they'll take a large cut). If you make good impressions on the clients and colleagues you work with there, they will become the personal connections that feed you independent work some years down the road.
Without taking the time for that, it can pretty had to break in, and much of the work you may be able to find will be miserable table scraps for poor clients who barely know what they're doing themselves.
- yasirdevloper 2y agoreasonable freelancing is for noob python,js ,c# guys i undestood your thoughts
- GianFabien 2y agoThere is a huge difference between freelancing and contracting. With freelancing you go to sites like UpWork and seek out work. With contracting you engage in professional networking activities, you identify the organizations that might need your C/C++ skills and then pitch to them. You build your reputation and portfolio of successfully completed projects. Obviously, contracting requires more effort, but it also pays far better. For most of my career I actually had paid work for 5-7 months a year. Much of that time involved working 60-80 hour weeks with quite a bit of travel on top of that. During the "bench time" I would chill and network.