Did the author mistype Password-Spraying or is there a seperate type of attack known as Password-Praying? Googling doesn't reveal any other hits on this term.
13,028 karma · joined October 8, 2008
I've done so much startup stuff I'm equally bad at all of it.
I currently work coaching Founders globally from a base in Singapore: https://coaching.figuringshitout.com/
I formerly was a 3x Founder and have worked in Engineering, Design, Product & Growth.
I also have a background in Computer Vision (designed a single camera 3D tracking algorithm), Augmented Reality (Designed a AR prototype for FEMA to manage disaster response workers), Tabletop/Touch Computing (Studied how people's collaborative behaviors change when put under time pressure), HCI (Studied it for 4 years), Interaction Design (ditto) and am well read in Psychology (esp. Social Psych), Economics, & other random trivia.
I also cook... a lot.
Did the author mistype Password-Spraying or is there a seperate type of attack known as Password-Praying? Googling doesn't reveal any other hits on this term.
eg: I would be confident stepping in as a technical manager in a software team but if I were to work in eg, aerospace, I'd still have strong conceptual skills but I'd be distinctly non-technical. There's a pretty shallow set of abstraction layers beyond which, I just don't have the education. If I were to go back to school for aerospace engineering, I'm sure my strong conceptual foundation would mean I could master the material 4x faster than anyone else but it would still be a lot of grinding work doing the math and using the software and building prototypes and testing so I could learn. And like, at this stage in my life, the ROI simply cannot pencil out, which is why it's so important to build the foundation when you're young.
I'd say almost every strong non-technical manager is strong on the basis of their strong conceptual skills but that still makes them a non-technical manager and there is a distinct difference.
I'm 20 years removed from any deep technical work at this point but I'm quite thankful that my CS degree's philosophy was that by the end of the program, you should be able to sketch out conceptually what's happening on a computer from electrons on a wire to how users react to your UI (basically, Nand2Tetris before Nand2Tetris). I've forgotten the fine details but that conceptual stack still exists in my head and it's an asset I'll always have.
There absolutely are many amazing managers of tech teams that are deeply non-technical and rely on their mastery of the abstraction layers they can grok to drive effective team performance. But there's also many times where the details do matter and the ability to dive deep into the guts of minutiae is an enormously valuable tool in your toolbelt. Management is a diverse set of skills and every manager rolls a different set of attributes on your character sheet and nobody is a 10 across the board. The art of management is to figure out what differentiated management style works with your character stats and build a team/environments to buff your strengths and make up for your weaknesses.
But the kind of technical knowledge you get from a solid CS education is too time inefficient to learn on the job and so there's real value to in absorbing it as much as you can in an collegiate setting.
You build the mobile app and you still don’t ship because the mobile app was not the problem, it just hid the problem. Until you understand and confront the true problem (emotional discomfort at the consequences of shipping), there will always be another reason not to ship.
People who focus on ideas think their ideas are so inspirational and unique that they must be protected. In reality, anyone who has tried to go out actively and convince anyone else to build their "brilliant" idea quickly realizes the level of indifference and lack of engagement anyone else has to your baby.
We are not perfectly rational automatons that always work towards our rational best interests. Shipping is hard so we create mental battles inside ourselves to avoid it and use post-hoc justifications to feel morally ok with that decision.
The choice of when to ship isn't nearly as important as the answer to why you aren't shipping on the choice you said you would ship. Yes, shipping at different points of maturity represent different sets of tradeoffs in a complex multi-dimensional matrix and it's an intellectually fascinating challenge but often, the choice is far less important than the debate that sucks it in and engineers end up bikeshedding the decision. Whenever you find yourself bikeshedding, it's important to realize you don't solve it by looking at the decision but by looking at why people feel the need to bikeshed in the first place.
You talk about how "Your job is to create great software. What's great software? The kind you'd be willing to put on your resume without feeling bad.", what is the "job to be done" by that belief for you? Is this a true, genuine held belief by you or is that here as a cover to some deeper belief that is uncomfortable to surface?
The answer is something ultimately only you can answer and no internet comment can force that deep degree of introspection, only those close to you who have a requisite degree of insight and therapeutic practice can reliably help with that. But the larger point I want to make is that the shape of the conversation around shipping is all around exploring where we feel different mental resistance around shipping at any point in time and uncovering where that resistance truly comes from vs the reasons we make up to dress it up.
Tesla sold about 100,000 Model 3/Ys to Hertz for rental in 2021.
Hertz rented a ton of EVs to people who were only used to the acceleration curve of ICE cars.
A ton of those people unexpectedly crashed those cars [1].
This clogged up Tesla's repair channels and blew out the timeline for everyone else.
[1] https://edition.cnn.com/2024/01/18/business/why-do-people-ke...
The classic story is some engineer who got picked up by a company when they were 22, did well and got promoted a few times and then runs into a terrible boss that makes their tenure untenable at 29 and goes out onto the market any interviews exactly like a 22 year old again by just shooting off random resumes from LinkedIn. I've had to slap so many of my tech friends on the head and be like, no, look, there's a so much more pleasant path you can now go down.
But like, why wouldn't it be that way? The median number of hours any engineer spends thinking about how to get hired in any one year is zero, there's an extreme minority who love the system and think about it all the time and they all talk to each other so they think everyone else is an idiot but the majority of good engineers spent most of their time getting good at engineering, not being hired.
I have an alternative theory which I call the "5th most important problem syndrome". At any company/department/team/individual, we have all the aspirations in the world but we really only have the bandwidth to work on our 1st & 2nd and maaaaybe 3rd most important problems. Getting better at hiring usually slots somewhere around the 5th most important problem which is a dangerous space to be because we oh so aspirationally want to get around to it this quarter but life inconveniently gets in the way so it gets pushed onto the backburner where it will forever be the 5th most important problem.
Startups have to be super careful to make sure they're not solving the 5th most important problem in their user's lives because the initial feedback will be overwhelming that this is definitely one of the top 10 most important problems the company/user faces and everyone is gung ho about fixing it but every time it's time to make forward progress, some "unexpected" emergency appears that derails the project.
Working on technical debt is a classic 5th most important problem which is why it's a perennial topic for debate in engineering circles. Startups that aim to optimize your cloud cost, IMHO, also run into this quite a bit. I've seen so many of them come and go throughout the years and my conversations with them tend to all follow this same trajectory.
The key though is you also have to present them at least 2 - 3 very radically different versions of the same thing.
Each tool has a different purpose at different parts of the design stage. When I'm in blue sky ideation phase, I don't want users to be thinking about colors and proximity (although I do, even at that stage, care deeply about information hierarchy and hate sketch tools that make information heirarchy hard to design for). It's when I'm more in the narrowing down stage that I'll move to more higher fidelity tools.
They are part of the problem but they don’t have to be part of the solution. It’s the CTOs job to realize they’re not getting accurate information from below and work to fix it, that’s why they’re getting paid the big bucks. It’s not like it’s especially hard to figure out but building the trust to create an atmosphere of psychological safety is the job of executives and takes a lot of hard internal reflection but that’s what you sign up to when you sign up to do the job.
Remember, a lot of the big food people came from big tobacco once the government started cracking down and they're just running the same playbook.
[1] https://www.linkedin.com/posts/gunter-kuhnle-13aba0171_a-who...
[2] https://www.bristol.ac.uk/people/person/Peter-Rogers-be40b6c...
[3] https://www.independent.co.uk/news/science/study-that-said-d...
a) Immediately fire the junior, yell a bunch and send company wide messages that anyone else making the same mistake will face the same consequences
b) Do a retro, figure out process changes that can avoid the same mistake happening again and thank the junior for discovering a flaw in our processes that leave room for improvement?
But there’s an art to Q&A that’s as hard as public speaking but practiced by 1/10th the people. A simple hand vote is the most basic tool. After a Q, I’ll summarize it and ask how many people face this problem? Etc. why get an audience of people in a room if you don’t use them?
You get smacked in the face over and over again moving into physical that the real world just doesn't work that way. You can take something as simple as a flat sheet of metal and there's a half dozen different processes to make it (hot roll, cold roll, cast, milled etc.) that each have different properties but there's nothing abstract underlying it.
Here's what I suggest you go: Buy two big totes and then go to a second hand store and buy an arrangement of the most random items ever (eg: a clock radio, a fork, a teapot, a book, a tv, a sweater etc). Break each item down into constituent components and put them all in Tote A.
Pick something random from Tote A that you're curious about and the hard bit is actually finding the noun of what the manufacturing process is (ie: injection moulding, Surface Mount Pick & Place etc.) to have made that thing.
The thing I really like after that is to go to youtube and find companies trying to sell machines/services using youtube as sales collateral (random example: https://www.youtube.com/watch?v=9uet6TNtUXI). They're talking about their process in the terms the customer cares about and it helps you get into the mindset of the customer about what's important in this manufacturing process.
Eventually, as stuff moves from Tote A to Tote B, get a 3rd Tote and move stuff to Tote C when you understand the upstream process as well. If you do this often enough, eventually you start seeing a "grammar" of the physical world. You can look at a thing and understand how it was probably built and why certain choices were made to accomodate the realities that not every single manufacturing process is as easy to pull off (vs in software, you delete one library and replace it with another and you don't really think about it) and you just need to know these things to make anything.
You can specialize down at any point in this process and inevitably will but I think the fascinating thing about starting general is that you eventually just start doing a mental teardown of any engineered product you encounter in the world and builds into a lifelong practice. You instantly spot the others who share the practice via all their little tells in the world and you find a secret club of people where membership is via geeking out about physical design.
Yeah, that's not agile. The entire point of agile is that you close the loop and the reason you break your work into smaller chunks is so you can deliver them faster in order to gauge the feedback of that chunk and better understand what should be delivered in the next chunk.
If you're not closing the loop, you're not doing agile, you're just doing waterfall with more bureaucracy.
One of their most recent episodes was on the Claudine Gay plagiarism scandal where they systematically dug into every one of the 54 cases of plagiarism and demonstrated just how much of it was bad faith right wing bullshit that didn't stand up to even the slightest intellectual scrutiny. But the larger point they were making was not about the right, for which they expected intellectual dishonesty, but the complicity of the left & mainstream media in only ever talking about the scandal in terms of who is saying what about it and why and not on the meat of the facts on the ground.
They took the exact same approach to the lab leak episode where they said let's ignore all of the media meta-narrative and look at just the plain facts on the ground and they found that, like most things, it was a sandcastle built of air that collapsed when you even looked at it funny.
Again, there exists a totally different hardware product Apple could build for Android that runs on Android OS expectations but it wouldn't be an Apple Watch.
I don't see how they could have done it without significant co-operation from the Android OS team far deeper than even two allied companies are typically able to communicate. The other alternative would have been to design a totally different piece of hardware that operates according to the Android OS expectations but that's hardly "bringing Apple Watch to Android".
2 of the 5 landlords lived in the same building where I lived alone and we became decently close over time and 3 of the 5 we rented the whole house but we were a group of grad students/working professionals that were an attractive demo.
As with anything on the internet, "This went mostly fine" is a perspective you rarely see so the prevalence of problems appears grossly exaggarated.
This, at least, narrows it down a bit.