Learn more about computerscience with this collection
Leonardo da Vinci's creative process
How to approach problem-solving like da Vinci
The importance of curiosity and observation
People think about “being technical” in a binary way, there are software developers who know how to code, and there’s everyone else.
Being technically literate simply means that you’re comfortable with the basics of how technology works, and critically, you understand the area you work in with more depth.
36
403 reads
MORE IDEAS ON THIS
If you work at a startup, chances are you’re going to need to collaborate with developers. That work could be internal on internal tools, integrations, providing expertise, etc. or it could be external marketing to, selling to, and recruiting developers
Dev...
35
161 reads
The better you understand the software your team relies on, the more proficient you’ll be in it. This already happens naturally: teams that are large enough will usually have one “power user” who seems to know the ins and outs of Salesforce, Lever, or whatever your team runs on. You want ...
35
111 reads
The tools you use day-to-day integrate with other parts of your company’s stack. Lever job postings might be displayed on your marketing website with Lever acting as the CMS; Intercom might be pulling user-level data from your data warehouse.
Understanding them means the difference...
34
88 reads
If you’re working in startups, you’re already surrounded by people who spend their entire days doing what you’re trying to learn a little bit about software.
In this arena, you’ll want to come prepared. Structured conversations with questions you’ve thought of in advance ar...
34
68 reads
There aren’t many places on the web with curated resources you can just read through so you’re going to need to be scrappy. The best content for explaining tech concepts sits in two places:
34
87 reads
Once you’ve built your plan and started looking around the web for helpful content, you’ll likely come across some usual suspects in your particular field who are creating useful stuff. Follow them, A few examples:
35
90 reads
Product: Without understanding how software engineers work and the basics of what code they’re writing you’ll be looking at a black box. Effectively prioritizing feature work, keeping tight timelines, and aligning stakeholders are all predicated on understanding the work your de...
35
143 reads
Being technically literate can often mean the difference between being self-sufficient and getting delayed by engineering resources.
34
115 reads
Marketing: Even if your product isn’t explicitly focused on developers, every startup eventually needs to build a developer program (see Slack and Twitter). Without technical literacy, marketers will be in the dark on how to effectively speak to and engage with this potentially l...
34
108 reads
Start by taking a look at your company and your role, and where you think being more technical could give you an edge. Earlier we identified a couple of areas:
If you’re a m...
34
72 reads
What’s a computer?
What’s the internet?
What’s a database?
What products are we building, selling, and...
35
210 reads
Understanding how programming works, what a language is, and basic patterns like packages and version control will help you across the board:
34
84 reads
Related collections
More like this
Read & Learn
20x Faster
without
deepstash
with
deepstash
with
deepstash
Access to 200,000+ ideas
—
Access to the mobile app
—
Unlimited idea saving & library
—
—
Unlimited history
—
—
Unlimited listening to ideas
—
—
Downloading & offline access
—
—
Personalized recommendations
—
—
Supercharge your mind with one idea per day
Enter your email and spend 1 minute every day to learn something new.
I agree to receive email updates