86 karma · joined September 25, 2011
tomspencer.dev meet.hn/city/gb-Bristol
https://www.oecd.org/sdd/purchasingpowerparities-frequentlya...
Next time use ChatGPT.
- Vonage: https://www.vonage.co.uk/communications-apis/sms/ - CM: https://www.cm.com/en-gb/sms/
Of course, one of the big drawbacks here is conceding control of a critical part of your infrastructure to another organisation. Better hope they don’t hell ban you, or you’ll be totally screwed. But that seems to be an issue with whoever you choose.
Initially, I stuck with the ‘permanent’ day job and start freelancing part time, in the evenings. This allowed me to focus on building a network of connections without the stress of needing to find a contract that would pay for my cost of living.
My first contract was through upwork (when it was called elance). I found a UK-based client who needed a small job doing for $25/hour. This merged into a new opportunity with the same client. 9 years on, and I’m about to go back to working for the same client once more, on a different project, at a much higher rate.
In parallel with this, as the pressure was not on to earn a living from freelancing (yet), I didn’t feel the need to fill every spare hour with billable work. Instead, I signed up to a bunch of different meetups, and volunteered to help run a couple of them. Through this I built a network of connections and opportunities, which led to _every_ other client I have worked for. I can’t stress enough how important this was for my freelancing career - visibility is everything. Tell everyone who will listen that you are a freelancer and you are open to new opportunities.
The contract market is rich and lucrative in the UK but you can’t expect to be handed opportunities via platforms. As others have mentioned, the best gigs come to those who put themselves out there. Speak to other developers at meetups and conferences, tell people you are a freelancer and eventually something will crop up.
Good luck!
As an aside, if you are being compensated less than permanent employees as a contractor, then your rate is not high enough. The ‘fully loaded’ cost of a permanent employee is higher than their stated salary, due to tax, insurance, pension contributions etc - all of these need to be deducted from the contractor’s billable rate to provide an accurate comparison between the two.
Best of luck with the project - as others have noted, this is a space ripe for improvement given the success of the closed source incumbent that is Firebase. I still mourn the loss of Parse!
As someone who has worked as an ‘Independent’ for the past 8 years, this really resonated with me. I aspire to be a consultant, but realise now that most of the time, I’ve been a contractor. I think the lines are a little more blurred (e.g. a consultant can still advise based on a set of requirements, which usually come from the client) but it’s one of the most concise explanations of the differences between these two roles that I’ve heard.
One big issue with the pull-based model though is with concurrency. If you have multiple workers polling an API endpoint for new data, you need to synchronise the ‘last seen’ ID or timestamp across all workers. Otherwise, worker A and worker B might pull the same data and you could end up with duplicates. There’s no silver bullet here, either model requires work to harden against edge cases.
Tired of listening through the browser, I found Radio for Mac [2] which allows you to play streams - DI publishes the stream address for all of its stations, so you can pipe these into Radio and hence listen to their music without needing a browser open.
Radio also has a recording feature - a stream can be recorded and saved as an mp3 file. After a few months of subscribing to DI I noticed they were simply repeating the same (few hundred) tracks on each station. So I set up my Mac to record a few stations over the course of a month, so I could listen to the tracks when offline (with Tiny player [3]). Since I was listening to the same songs over and over, I started to question whether I needed a subscription to DI any more…
[1] https://www.di.fm/ [2] http://radioformac.com/ [3] https://www.catnapgames.com/tiny-player-for-mac/
That being said, I agree with other comments that this is somewhat swimming against the tide. Redis is much more commonly used, and so if you don’t mind adding another service into the mix, I’d probably recommend going with Redis instead.