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.
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.
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.
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.
Tutorials are all very well, but what we really need is the programming equivalent of Geocities or Diaryland. That's how many of us got started with HTML and CSS - by making stuff and trying to get it to look nice.
Ideally this place would take care of the back end and provide a few basic components (e.g. pages, views) for you to structure your app. There would be code boxes for you to type into, and once you click save you'd be able to view and use the app at username.site.com. At first you might piece together a program out of pre-written components via point-and-click, then you might tweak the code to better serve your app, later on you'll get bored with the presets and start writing your own functions...eventually you'll learn to code from scratch.
There are tools that come close to this (GAE for example), but nothing at the absolute-beginner-anyone-can-do-this level.
These days it's all about results: what are we going to get for doing this action? What purpose does it serve? The same thing has happened with our eating habits, among other things. How many calories does this contain? What vital nutrients will this give me? (I'm not saying it's a bad thing.) However I have a feeling it'll be a while before this approach will work with child development.
- Nutrition
- Financial literacy
- Logical fallacies
- Emotional intelligence
- The creative process