456 karma · joined May 28, 2018
You can reduce the attack surface, but never eliminate it.
The level of sophistication is already making some doctors feel obsolete, by their own admission to me. If we don't get to live in exciting times, our children and grandchildren surely will.
I know this because this happened in several smaller cities in my country way before the virus, for other reasons. Anecdotally, they also tend to tell me they are happy, compared to metropolis-dwelling friends who often confide in me that city life isn't all roses...
TLDR: One only really needs a community of about 150-250 non-interchangeable like-minded people to be happy and have dating/marriage prospects. In a city of 10K people you can also change your Dunbar community several times if you want to.
1) There is no lock in - I can move on and off LI whenever I want, and have. I've exported my data and used it to create my own resume site with analytics that I send out to companies. I can see who viewed my CV, when, and whether or not they actually read through it or bounced immediately.
I've also learned to track the progression of my candidacy through the organization using this trick (recruiters tend to view my CV on their Windows desktop during work hours, hiring managers tend to check out resumes in the evening on their iPhones or Macbooks, engineers/tech leads tend to use Macbooks, desktop Macs or Android phones in the morning or during lunch time. Usually when I've hit the engineering lead I tend to get invited to interview).
It's extremely easy to create your own CV website for free (github/lab pages) that's versioned by git and deployed automatically using a CI script.
2) You're attacking the tech hiring problem from the wrong angle, like everyone else. There is no issue with discovery of candidates and employers. LI and stackoverflow, etc do a great job of approximating this O(N^2) exposure process, the filtering and sifting. The ACTUAL problem is on the hiring end - companies won't take a chance on non-traditional candidates (not talking about race and gender here, more about credentials).
You have to start by chipping away at the costs of showing competence for a candidate (the traditional way to do this is to get a three- or four-year degree that's either expensive in terms of time and money, or useless, and if you get a degree with a low score, doubly so, even though you might be a better programmer than the people who scored over 90%).
This will only happen by convincing hiring orgs to hire non-traditional candidates, and this requires establishing a very strong signal/noise ratio for candidates coming from your hiring channel. Before you start PRing me about how great TB is at this - no it isn't. Not any better than leetcode etc, and those are terrible at predicting engineering competence.
My high school physics teacher, the only one who believed in me, whom I continue to disappoint every day by not achieving a Nobel prize in physics.
The problem with GitHub profiles is that they tend to contain a lot of noise that nobody has the time to go through, and when they do, the projects are usually not very impressive. They tend to look like they were made by a project generator with little subsequent work by the actual human.
My advice to you would be:
1) keep applying to jobs
2) clean up your GH account to only contain 1-2 extremely great projects. Hardly anyone would look beyond that. Get rid of the CRA based CRUD projects if you have any, they will not impress anyone.
3) use your unique background to stand out. Make sure your projects are unique, interesting and draw attention visually. Use your background in 3D graphics. Use your ME background where there's a wealth of data to be analyzed and presented. Be creative. Put up informative and interesting READMEs for your projects, as they will be the deciding factor in whether anyone decides to spend more time on your project.
Good luck! Feel free to contact if you need advice or guidance.
edit: can never get HN formatting right
I mean this as much in a figurative sense as in a literal one.
This may be a silver lining in an otherwise very gloomy comment page? When I was in HS (though not in the US), popularity was highly correlated with wealth and/or political activism.
Otherwise a copy is required into a hardcoded address or physical memory, and then you're not double-buffering anymore.
Because in 2020, education is credentialism. Every one of my friends who approached or was approached by a VC was asked: did you go to a good school? Do people up the chain like you? Show us references from professors and supervisors! This is not some big player hiring a manager-executive, I'm talking about investors whose job is to identify left-field potential and take risks.
You can't create Harvard 2.0 if your measure of success is having attended Harvard 1.0, and Harvard 1.0 is under no pressure to change or adapt.
Even the best VCs won't invest in socially inept dropouts anymore. The next Steve Jobs isn't building something in his parents' garage, because nobody believes in his ability to sell computers. He doesn't have an MBA from Wharton; he isn't a Stanford PhD. Thiel's "just don't fuck it up" just can't happen in 2020, except maybe by Thiel himself (or Weinstein, who is slowly waking up to this truth).
If anything, crises might force VCs to take risks again. Let the flood of easy M&As run dry and the dam dismantled!
oathContract = power.witnessOath(declaration, curse);
or in the case of a Christian power (which ISA Jewish power too): oathContract = christianPower.witnessOath(declaration);
It's just not the same interface. You can't realistically ignore the type of power and use a polymorphic call. The Bible says so.
(Of course, when you oathContract.renege(), we know which power should handle your case, and can put a message in their respective queue)
Personally, I'd prefer to spend my day at home and go out to meet actual friends and family after work.
Modern office work is not the default state of humanity, let's not pretend otherwise. I bet a lot of people would be happier with a modern version of farming their own land and spending time with friends and family.
Personally, I prefer my configuration to be written in a plain-old language (e.g. Python) instead of a specialized config language (be it YAML or JSON based or whatever). I can test that code, I can reason about it, I can review it for bad stuff like infinite loops (not perfectly, but still), I know how it behaves when diffed and merged, etc.
Regarding software architects: I've seen a few companies where architects are hands-off demigods who prescribe complete architectures without ever having to contend with the results of their decisions. Those companies are, in my experience, few, and tend not to do well.
In a lot of other companies, the role of an architect is very similar to what Herr Scarface describes - individuals with a lot of experience who can make broad decisions based on both experience and data, and leave it to lower ranking engineers to work out the exact details. They do the hard/open-ended stuff and come to conclusions about the broad strokes (e.g. "yeah Redis will work well for this problem, but since you have denormalized data you might need a background process to restore consistency"). This is often called "scoping" and it is the main responsibility and impact of higher-ranking engineers (whether they're called "architects" or not, I personally dislike the term).
* Forcing users to learn a specialized language vs reusing knowledge of a general purpose language
* Inevitable Turing-completeness creep and increasing complexity in specialized languages
* Complexity and difficulty of reasoning about general purpose code (and analyzability)
So GP does have a point. He/she is just not making it very well, I think.
I've done a lot of C programming over the years and I still consider it one of the most elegant languages I've had the opportunity to work with. With the right skillset, you can be as productive as a programmer of any other language or system.
And it's great to see where some of the things we take for granted in programming, come from.
If you want to draw pixels, give Cairo a try. It's fun to use!
Thanks!