Gathering thoughts…
Instead of relying on your resume or portfolio to get you hired, it's best to create a narrative tailored to what the client is requesting. Your experiences should be the frame of the story, where you fit in similar situations you've faced and the solution you've helped implement. The goal is to give the client the confidence he has the right person in front of him and a sense of what working with you looks like.
Get Holy-Elie's writing delivered to your inbox, whenever they choose to send it.
Be comfortable talking money with clients Ask what their budget is Reluctance to tell the budget is a massive red flag You need to know how much money you need to survive each month Initially your current salary Double that to generate a buffer Never work for free
I came across an article on HN about making the interviewee read code instead of writing it. Many people really like this approach. As someone who is often on the other side of the hiring side, my thoughts about it would be: The sample should use the code stack I will be interacting with – languages, technologies, platforms, and frameworks. The time allocated to understand the…
Yes, the freedom is great. You can set your own time, your own rate - which is usually higher than an employee, and you can work on exciting stuff. But most of the time, it is very mercenary. You are not a part of the community that surrounds the project. You weren't there when it was only an idea, and often you're not there when it becomes a product. You can still feel proud…
