++ your comment as this is first actual dev rant i have read in a while.

A lot of comments above make sense. One thing you can do is pull back a little. Work your hours in your contract. One life lesson here is to not work overtime for free. Simple rules:

1. The other party should request over time always.
2. A trade is always required. Recognition, payment, time off in lieu, stock options....

The moment you devalue yourself so does the other party.

Giggity

She is too good for you. (Python for the win)

Could be that i am tired or in a down mood but that is on you. If you are getting a second, third or more requests you should be communicating the impacts to the client or lead.

Takes 5 minutes to pause and provide a new status.

@nedo-the-angry

If you sent an email or had a meeting, clearly identify items in scope for the project.

I personally send my pm, team lead, and project sponsors status updates if the pm is bad

For each item in scope show the start date, end date, effort, risk or issues impacting you from reaching that dead line. For example, you could identify external or internal issues impacting your deliverables.

In essence, you are doing a mini PM status update.

For bad project leads, this is my "cover my ass" approach. I send updates every week with status alerts.

Hope that helps.

Vagrant!

Try to manage expectations. If you let it slide, that same degree of overtime effort will be expected on future projects.

I prefer no comments. I like markdown docs or commit comments. If a comment is needed most likely the code requires some touch us.

I am torn on comments honestly. Previous roles it was a high priority but lately the trend has been to have 0 comments.

I now use them sparingly.

Pep8...

Java developer for 8 years and moved to python, I had lots of bad python practices. Pep8 was a nice helper

Thanks. Enjoying it.

I went through your projects on github before posting my previous comment. If I was to be honest, if i was to review you solely on github, I would probably not give you enough attention. Having to review 20+ candidates, i look for key things and if I don't see it or I have to hunt for it, it is an easy pass.

Pimp out you github profile.

I would recommend creating a project in django (saw you created a django project previously) that solves a common problem or uses a algorithm.

For example django__angularjs__twilioConsumer or django__restConsumer__websocket

The title It should be simple, descriptive, your readme should be pretty and concise. This project should be small and focused on what you enjoy. it could include:
- unit tests
- clearly defined readme file
- code comments

Remember that recruiters will look at your code style, consistently, algorithms used.

If you are applying for different jobs, have different projects that high light those skills.