|
|
|
#CareerAdvice
tl;dr: (1) Don’t fight the tools: libraries, language, platform, etc. Use as much native constructs as possible. (2) You don’t write the code for the machines, you write it for your colleagues and your future self. (3) Deprecate yourself. Don’t be the go-to person for the code. (4) Any significant and rewarding piece of software is the result of collaboration. And more.
|
|
Migrations Done Well
- Gergely Orosz
#Management #Migration #Guide
tl;dr: "If you do some groundwork before starting the migration, you’ll reduce risk, gain confidence and understand the scope of the migration better." Gergely breaks the migration process into the following steps: (1) Preparation for migrations. (2) Pre-migration steps, such as monitoring and validation. (3) The migration itself, covering downtime, strategies & toolset. (4) After the migration. (5) The migration long-tail.
|
|
Stop Asking Your Developers The Three Standup Questions
- James McGill
#Leadership #Management
tl;dr: Code Climate VP of Engineering, James McGill, thinks you should stop asking your team the three classic standup questions. In this two-post series, he 1) demonstrates how you can answer those questions with engineering data and 2) proposes three new, more impactful questions to ask instead.
Promoted by Code Climate.
|
|
Organizing And Scaling An Effective Data Team
- Rob Dearborn
#Leadership #Management #DataScience
tl;dr: The scope of a data team should include: (1) Ensuring focus on the right hierarchy of input & output metrics. (2) Steering the roadmap through insightful analysis & research. (3) Driving optimization through experimentation and ML. (4) Developing and maintaining data infrastructure. Rob outlines how the data team should evolve, and it's function within a startup, as it grows.
|
|
|
"Some problems solve themselves if you are patient enough."
– Jaana Dogan
|
|
|
Architecture Patterns: Caching
- Kislay Verma
#Scale #Caching
tl;dr: "Depending on the type of application, the type of data, and the expectation of failure, there are several strategies that can be applied for caching." Kislay discusses the levels in a systems architecture where caching commonly occurs and various caching strategies, such as read through, write through, write behind.
|
|
|
#Mozilla
tl;dr: Mozilla has 3 basic values for the web: (1) Openness, so everyone can use it. (2) Agency, empowering individuals to accomplish goals. (3) Safety, the web must not put individuals in danger. They highlight several things they can make better, such as protect users from malicious code, protect user privacy, improve accessibility for those with disabilities, and more.
|
|
Why Don't You Use...
- Brendan Gregg
#Management
tl;dr: "Working for a famous tech company, I get asked a lot "Why don't you use technology X?" X may be an application, programming language, operating system, hypervisor, processor, or tool." Brendan provides a list of common reasons.
|
|
An Introduction To Generics
- Robert Griesemer, Ian Lance Taylor
#Go #Generics
tl;dr: Generics adds 3 new things to Go: (1) Type parameters for function and types. (2) Defining interface types as sets of types, including types that don’t have methods. (3) Type inference, which permits omitting type arguments in many cases when calling a function.
|
|
Meilisearch
Powerful, fast, and an easy to use search engine.
|
The Fuck
Magnificent app which corrects your previous console command.
|
|
Partytown
Relocate 3rd-party scripts off the main thread & into a web worker.
|
Clash
A rule-based tunnel in Go.
|
|
How did you like this issue of Pointer?
1 = Didn't enjoy it all // 5 = Really enjoyed it
1 2 3 4 5
|
|
|
|
|
|
|
