Having been on both ends of the hiring process (in tech):
1. You don't have to be 100% qualified. Just show me that the skills you have are transferrable.
2. Tailor your CV & cover letter to the vacancy and company. List at least one work/life/volunteering experience (preferably a project with end results) that is linked to each of the requirements.
3. Keep it short and to the point. A quick glance and relevant keywords should jump out and pique my interest.
4. If you go "but..." to any of the 3 points above, you're probably wasting everyone's time.
I'm going to "but... " point 2, having been there last week.
There were 10 requirements. It was a niche job that I was skilled at. For 1 I had life experience with end results (do ppl have life/volunteering experience that applies to job requirements? I'm nearly 40 and don't). For the other 9 I could link them to exact work matches - except all are under NDAs with different clients, so had to be described vaguely.
The company I was interviewing with weren't impressed, which was ironic as I'd had to sign a NDA prior to the interview.
They also wanted to inspect code I'd written - can they see a project? Well no, because it's written for a commercial client. What can I show them on GitHub? Nothing helpful as I develop in private repositories and what is public is experimental code doodles.
How do you handle strict NDAs and private projects?
If it's under NDA then don't talk specifics, but during the interview you can talk about difficulties you overcame or lessons you learned during the process. The key is to show that you are equipped to solve their problems.
If they're pushing for you to break NDA, then you probably don't want to work there anyway.
Question everything. Not just the obvious things like "how does crypto work", but also mundane things you encounter in everyday life: Why did they react that way? Could I have handled that better? Why was ___ placed in that location? Why isn't there a ___ here? Why is ___ more expensive than ___? What are they trying to achieve with ___? Why do I want ___? Etc.
Dischidia aka String of Nickels/Button Orchids are great if you don't have a green thumb. Mine have outlived even my Tilandsia (both of these are hardy soil-less plants)
Back in 2004 I had the H2G2 website (h2g2.com) bookmarked on my Nokia 3100 and would read it whenever I was waiting for the bus (this was before Google Reader). A cheeky, entertaining precursor to Wikipedia.
I think washings machines, some digital cameras, and also a train station system in Japan were some other famous applications (from what I can remember).
Automatic gearboxes, ABS, cruise control, some plant controls. Fuzziness saw strongest uptake in Japan, so any control system developed there has a decent chance of having a fuzzy system at its core.
Tiddlywiki is what I use to manage my own personal Zettelkasten as well; it's pretty well suited for the task. There's a bit of ugliness when renaming Tiddlers, but for a lot of inter-related topics, I add an automatically-generated list of backlinks like this:
Can confirm. Many a time the owner of an iPhone has had to shift the floating dot around to show me something on their screen. Such an eyesore...almost as bad as the notch.
Google Moderator. It was a reddit-like service that allowed you to crowdsource popular opinions. We used it to pinpoint UX issues in the early days of our startup.
My office recently knocked down a dorm room so that the team sitting in the corner could get some sunlight. Made the area so much more pleasant to work in.
- Nutrition
- Financial literacy
- Logical fallacies
- Emotional intelligence
- The creative process