Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "poor grad"
-
So, I'm a CS student in a third world country. I love coding and I think i'm pretty good at it.
As I'm kind of poor, I'm pretty much constantly looking for any job I can take, and I've already done a dev gig at a software sweatshop here doing mostly PHP, JS and Android/Java... the dev experience was cool, but money was absolute crap ($1.5USD/hour at the current rate, working 9h/day Mon-Sat, did it while in vacation). Better than min wage in my country but still, looking at the numbers I see from programmers all over the world... it was practically working for free. The real problem is almost every dev job here is similar, so I was looking into going remote but every opportunity I see is for seniors/people with 2-3 years experience or more.
Can you give me some tips on getting a remote job as a student/recent grad with little experience? What would you do in my position? Any input is greatly appreciated!17 -
First job while in college... Was working for web dev team lamp set up before lamp was lamp (year was 2000).
Had deadline one week after summer vacation. Worked non stop a couple of days to get shit done and didn't make it. Got in a conflict with my manager in front of the team and I blew my steam off. Quit on the spot.
Lessons learned:
1. Don't be a fucking idiot when estimating work.
2. Be cool with other teammates, nobody cares about drama and nobody has to feel sorry for you.
3. Uhm, plan? Had entire fucking vacation to get work done. I was a fucking moron.
4. Burning out is stupid and unproductive.
5. Your manager can be as poor in management as you are. Your job is to try to make them better at it, as they have less visibility in the details.
Next job in grad school. Worked for a security company. Direct manager had the bright idea to make execs sign the change requests. WTF. Code was in Perl/php, a mess. Team rewrote back end DB access , taking over six months, or more, failing twice the deadline. After a final 48 hour burn out, we ship and get laid off the week after.
Lessons learned:
1. Don't work for dicks.
2. Don't be a dick yourself.
3. Don't work for dicks.
Third job was in silicon valley. It was a great company, and I stayed there for five years.