One of the values of public discussion is that the whole world can see the advice that is shared. People who won't share their advice in public are often trying to scam, or at least sell something to, the person asking for advice.
I chose this approach in case the OP wanted deeper tangible pointers which is only possible with an understanding of their specific situation and kind of projects, location, etc.
I shoould have made this more clearer in my first comment
Not currently but we have an internal tool that does bi-directional syncing using Postgres's replication protocol and WAL2JSON. It's not quite ready for prime time but we're hoping to get it into people's hands soon.
Ocaml is developing quite well.
I wish we could simplify the readability of the language. Reason comes pretty close to this.
And a nice django clone in ocaml/reason would lead to a lot of traction
As long as the algorithm is open source and the design can be agreed upon by both parties.
You may still need a human to make some decisions that feed into the algo. If not you’re probably not doing anything new in which case an algo is anyway better.
This won’t work in positions where you’re expected to work with ambiguity and bring order out of chaos though I’d be interested to think about how that can be quantified.
It really comes down to being transparent and clear. Humans can do it too, machines can do it better.
It depends on the context. Many of Amazon or Tesla's workforces do low-skill work, and each employee isn't bringing in all that much revenue. For software-only companies, this could indeed be an intersting metric aside from just margins.
The best thing to do in this scenario is to go ahead and interview in a few small companies and startup’s. At least 6 interviews ideally
If you have no professional experience yet apply to companies asking for 1y experience. They are still open to fresh graduates and even if they’re not for that role they could open up an internship opportunity.
Don’t prepare for the first three interviews, just treat them as practice.
Prepare a little bit for the next three.
Internships are great if you want to experiment and see what you like. Do a couple internships in different kinds of roles or industries based on what you’re interested in.
Start interviewing without expecting to get a job or preparing. This will allow you to be less stressed during the interview and you will be able to learn better.
Treat interviewing like learning a new programming language. Start with a hello world.
Author here (I'm a bit late!): indeed Griffe's goal is to be able to support any Python code, natively or thanks to extensions. Thanks for sharing by the way!
