31–40 of 418 posts
So Francesco says they refuse to do technical interviews and says their CV and Github are proof enough. The CV shows experience as a freelance engineer at Apple for a bit, then an engineer for Samsung which they were made redundant from. Their GitHub is 3 projects, a python script, a breakout board and then a beta libary. They argue that's fine though because they'd work for £1/hr, but the real cost of an upfront hir…
This is interesting! My own anecdote: when I graduated from college I had zero experience aside from one internship at a small noname company. No one would hire me. I started reaching out to local companies big and small saying I would work for free if they'd use me. Not just programming jobs, but also general IT or even helpdesk jobs - anything remotely computer related. None took me up on my offer. I suppose they s…
the lesson should be to value your labor correctly, as large deviations in perceptions of value mean that transactions won’t happen. a more astute approach would be to communicate your (accurate) understanding of your own value and your willingness to negotiate alternate dimensions of value in exchange, like getting experience faster or doing more interesting work in exchange for less money.
tl;dr: establish a common understanding of value, then negotiate.
Why should we make any compromises on the activity that we'll spend the majority of our lives doing?
So Francesco says they refuse to do technical interviews and says their CV and Github are proof enough. The CV shows experience as a freelance engineer at Apple for a bit, then an engineer for Samsung which they were made redundant from. Their GitHub is 3 projects, a python script, a breakout board and then a beta libary. They argue that's fine though because they'd work for £1/hr, but the real cost of an upfront hir…
How about: Hire me, pay me what I'm worth, and give me interesting work. Why should we make any compromises on the activity that we'll spend the majority of our lives doing?
These are general-purpose programming languages. Due to their design, some patterns/paradigms might seem more natural to implement, but you can build anything you want with them.
For an experienced programmer eschewing conventions with this "resume", I am surprised by this comment.
My advice: pursue a PhD. If you can find the right advisor, then you will have almost complete creative freedom to pursue interesting projects while getting paid to do it.
So Francesco says they refuse to do technical interviews and says their CV and Github are proof enough. The CV shows experience as a freelance engineer at Apple for a bit, then an engineer for Samsung which they were made redundant from. Their GitHub is 3 projects, a python script, a breakout board and then a beta libary. They argue that's fine though because they'd work for £1/hr, but the real cost of an upfront hir…
I didn’t even know Apple or any of the other FAANG’s hired freelancers.
So Francesco says they refuse to do technical interviews and says their CV and Github are proof enough. The CV shows experience as a freelance engineer at Apple for a bit, then an engineer for Samsung which they were made redundant from. Their GitHub is 3 projects, a python script, a breakout board and then a beta libary. They argue that's fine though because they'd work for £1/hr, but the real cost of an upfront hir…
But overall, I somewhat agree with Francesco. I used to work at a large corporation where majority of the work was minor config changes and rolling out deployments for handsome pay (somewhat KTLO work). I left because I wasn't growing my career. As companies get bigger the money gets bigger as well but the interesting work gets much smaller. At the end of the day, once you have a solid product in place you need a lot more people to just keep it running vs. work on some very interesting technical work. I think applied research is the best way to go for very interesting technical work but I think the bar is pretty high for that.