|
|
|
#Leadership #CareerAdvice
tl;dr: We assume attitude drives behavior but, in fact, our behavior also shifts our attitude. A misalignment of behavior and attitude i.e. you should do something but don't feel like it results in cognitive dissonance. Ed outlines strategies to counter this (meditation, journaling, etc...) but states they should come from a sense of authenticity and agency.
|
|
#ProductManagement
tl;dr: The concept of a user "pigeonholes us into ideas that mislead our product direction and corrupt our technical choices." Chelsea notes three fundamental issues with the term "user:" (1) It doesn't describe how someone uses the product - reading, listening, playing, etc... (2) It implies addiction or manipulation (3) Inevitably screws the data model. Chelsea highlight this with examples.
|
|
Finding Collective Ownership of the Codebase
- Britton Broderick
#Management
tl;dr: Software engineering is a social activity, not an individual activity. Enabling that social element is key and making sure that the team writes and owns code collectively, as opposed to one individual, is crucial. Britton showcases how and why this is true.
|
|
|
#ThoughPiece
tl;dr: Simon cites how biographies of successful people indicate a form of self-created agency that allowed them to explore their passion, at an early age. Our current educational system creates the opposite system - it cannot "conceive of what to do with children." However, the internet is a new opportunity to learn without permission. It allows for learning by doing.
|
|
Finding the Bottom Turtle
- David Anderson
#ThoughtPiece
tl;dr: "Turtles all the way down" is an expression of the problem of infinite regress, and the post asks "do we know for sure that the programs we’re running correspond to the source code we have access to?"
|
|
|
A Note From The Editor:
Pointer will resume a twice a week, on Tuesday and Friday at 9am EST.
Thank you for subscribing, please reply to this email to share feedback, any thoughts you have on the issue, or to just to say hello.
|
|
|
AuthZ: Carta’s Highly Scalable Permissions System
- Aaron Tainter
#SystemDesign
tl;dr: Aaron had to build a system that was scalable, fast & generic enough for any new products. Permission systems that are too simple lack the features to "support fine-grained access on single resources," and too complex the system might unravel a "whole policy of attribute-based permissions." Aaron runs through the creative approach taken.
|
|
|
#Testing
tl;dr: "Pyramids, honeycombs, trophies, and the meaning of unit testing." Martin discusses the recent twitter discussions on various testing strategies, and the balance between unit and integration tests.
|
|
#Python
tl;dr: Nikita introduces typeclasses - a concept behind the dry-python library - that solves the problem of how functions behave differently for different types of inputs, with examples.
|
|
|
#GitHub #AI
tl;dr: "Get suggestions for whole lines or entire functions right inside your editor."
|
|
#JS
tl;dr: "In this quiz, you'll be shown 25 quirky expressions and will have to guess the output. Even if you're a JS developer, most of this syntax is probably, and hopefully, not something you use in your daily life."
|
|
|
|
|
|
|