Like everyone else, I have a hacker news client, which is "universal" (in the Apple sense), and is made around how I use the site. I might even release this one, one day.
42 karma · joined May 22, 2017
Like everyone else, I have a hacker news client, which is "universal" (in the Apple sense), and is made around how I use the site. I might even release this one, one day.
Apple's software only runs on their hardware, they regularly exclude recent and capable devices from running the latest versions and they deprecate and ignore insustry standards liberally (OpenGL, Vulkan, Nvidia GPUs). This makes their software much simpler to write. Compare that to Android, which runs on anything, or Windows, which I hear can do crazy stuff like run apps from the 3.X days.
This creates a massive attack surface for would-be spammers, as well as a situation where "Xbox fans" have to share a space with "Playstation fans" and are expected to get along i.e. fertile ground for trolls.
The only solution I can see for this, is a return to the world we had in 2005, forum.xbox-fanatics.foo and forum.ps-fanatics.bar
Occasionally, for a side project, I'll need some sort of back-end. This usually means I need to get some data from somewhere, process it a bit, store it and then ask for it at a later date. JS (Typescript in my case) is more than adequate for this, and if I add Redis and Nginx I can get away with paying very little for a VPS to run it on quite reliably.
The JS landscape has lots of problems, but I don't wade too deep into it so I'm mostly content.
The episode with Isaac Arthur [2] is a good place to start.
[1]https://podcasts.apple.com/us/podcast/john-michael-godiers-e...
Seems like an epic pain in the ass for a 4.1% yield
I complain about gas prices as much as everyone else, but that seems pretty good. Does anyone know how much the typical miner was making with POW?When I was in university made a small 2d game engine in J2SE. Performance wasn't great, so I had to use sprite sheets, pallette swaps, masking 256 color images etc just to make things playable in most cases.
When I graduated I decided to get into mobile development, to my surprise doing things like just dumping a bunch transluscent PNG's into the workspace were recommended in the docs. Seems like the web had a similar trajectory.
I'm not sure about that. A quick search shows that the (on the box) requirements were 33mhz 486, which seems to have been fairly reasonable for the time.
Alternatively you could let users make profiles with their preferences for their ideal job (remote only, MEAN stack, >£80k, etc) and notify them when a matching ad appears, you could even charge for this. This strategy allows you to also charge employers to contact/see your users, I think Dribbble does this, so it might be worth taking a look there.
Good luck and let us know how it works out, I love hearing about stuff like that.
One issue you might have is that your user's are "shortlived", I would imagine a typical user is going to use it for a couple of months every 2-3 years, hence why I'm stressing quick growth.
I say this because it's helped me do both of these things. When MongoDB came out and I was looking to start a new personal project that looked like it could benefit from a nosql db, I bought a cheap course and was able to quickly see that boring old MySQL was more suitable. There was also the time when I needed to get back into Android development after a couple of years of doing only iOS and back-end work. For $10 I was able to quickly get up to speed on what had changed and identify what I needed to do deeper reading on.
All that said, I have trouble seeing how they will be able to make this investment worthwhile for their backers in the long-run.
1) Your network will be your main source of work. I've been freelancing for just over a year and every single job I've had has come as a result of relationships I made when I was in full-time employment.
2) In terms of billing do not be afraid to charge a lot more than you would expect to make if doing the same work as an employee. You'll get better at this.
3) It also helps if you can save a few months worth of money before hand. I've found that it helps psychologically when negotiating if you know you don't need to take a job. In practice you will (ideally) a fair amount of what you are offered, this can be because some jobs simply aren't worth taking and the opportunity cost of a mediocre pay-day.
4) Take time off when you can and always sleep well. You will switch between periods of no work and periods of too much work. Relax during the former so you are ready for the latter.
5) Know your stuff and work hard.