One of the best decisions I made during a very turbulent 2020 was to leave conventional coding behind and embrace the #nocode movement. @bubble made this a reality. Although my own journey thus far is premature, I’ve learned a lot so here’s a power thread on....

Google's interview system is not great but there are various reasons why it feels less than it is. Most candidates don't know what the goal of our interviews are. First rule, it is not about finding an optimal solution or any solution at all.

You are interviewed for multiple skills simultaneously. Cognitive skills, communication, leadership are a few to name. If the point is not finding a solution, then what is it? Let me explain.

Your interviewers try to understand what it feels like to work with you on a daily basis. An interview question is just a tool in achieving that, it is not there to specifically measure your skills on a topic but a tool to understand the depth of your thinking.

Before the interview starts, ask them what they want to get out of this interview. Good interviewers should already have a plan and a set of expectations. Ask them what you should do. Don't start coding yet. Ask them you should produce. Discussion, diagrams, pseudo code, code?

Then, start cracking the question. List whatever questions you think it is important to solve this question, ask your edge cases. Get to a point where you are discussing about pros/cons of the solutions. These steps are critical. Don't just start coding. Have a consensus first.

Oh are we talking about Sheryl Sandberg again? Well, your reminder that disabled feminists, LGBQT feminists, and feminists of color criticised her ‘lean in’ deal from day one. Don’t let anyone retcon that out of existence.

Like, a pretty narrow slice of feminists actually endorse and support corporate feminism, they’re just white, nondisabled, straight, cis, and noisy so their voices have a bigger reach.

So if your impression is that ‘feminism’ gave her a ‘free pass’ maybe you should question your overall impression of feminism rather than continuing to centre a handful of people as ‘thought leaders’ or whatever.

Critics within feminism have been doing this work for a long time and have been getting shat on it for about as long and I'm tired of seeing them erased. But what do I know — I am, after all, not a feminist.

But I WILL say, from my not-a-feminist perspective, that people who aren’t feminists who are criticising feminism should maybe understand the movement more deeply beyond a handful of high profile celebrity feminists.

Observing the public conversation around FB, and the private ones happening among techies and ex-FBers, I think the mutual misunderstanding is worse than when I set out two years (and 500 pages) ago to (in a small way) bridge that gulf.

We're basically fucked.

The tech world has gotten so huge, self-reinforcing, and insulated from reality they can no longer even vaguely look at themselves (and their actions) as others do. They just live on a different planet than most people.

Conversely, the average tech consumer doesn't understand the technology that has slowly taken over their lives, and their designated emissaries to figure it out--politicians, pundits, regulators, journalists--understand it barely better than they do, and have their own agendas.

To say more than generalities for a moment, here's what I think is likely the core problem.

Techies take weird, improbable visions, and make them realities: some BS pitch deck to a VC, mixed with money and people, really does turn into some novel thing.

Most people work inside a legacy industry that's evolved that way over time (usually for good reasons), and they think about the future via some analogy with their present (which is a function of a long-ago past). The interruption that tech will introduce is often hard to grasp.

#RaspberryPiPico silicon teardown time!

Board as received optical + x-ray images

Inspecting package. X-ray shows bond wires easier after removing thermal slug

Thermal slug removed w/ HCl + H2O2

Decapped to show copper bond wires connecting die to package pins. Initially used only nitric acid which destroyed copper bond wires (last image). Fixed by switching to mixed nitric + sulfuric acid

1/12 @HathorNetwork offers a unique set of features for both builders and users. Some well known ones, others not so much. Let’s look at why you might want to consider Hathor as the layer 1 solution for your project. $HTR @HTRFDT #BuildOnHathor

2/12 Easy tokenization is the obvious one. You create your own token in less than a minute, no coding required.

3/12 As opposed to ERC tokens, your custom Hathor token is a layer 1 token. It inherits the same features and security as the native token, $HTR, effectively giving your token the same level of security as the #Bitcoin $BTC blockchain.

4/12 Hathor Network also passed their security audit by @SlowMist_Team so you can feel safe knowing that your L1 token fulfills the same security requirements as $HTR.

5/12 By configuring built-in nano contracts you will be able to add logic to your token. No coding required. Native nano contracts also mitigate the risk of bugs and security issues that comes with custom smart contracts development on other platforms. $HTR