A bit of inspiration most weekdays for exploring your mindset .

2024

Write code to compile -

Tools for tasks -

Developers and builders -

Deleting code -

Enablers -

Best Practices for Writing Good Commit message -

Writing good commit messages -

We need immutable systems -

Know if your OSS project is losing steam -

Positively inclined -

Ground-up or Top-down -

Rolling releases -

Productivity Hacks -

News - Recommended based on your interests -

FOSS Guardrails: Contribution Policy -

FOSS Guardrails: Security protocols and processes -

OpenSource Guardrails: License compliance -

OpenSource Guardrails - Governance -

Define OpenSource Guardrails -

Know your OpenSource (FOSS) consumption -

Decoding Silos -

Beware of Shortcuts -

InnerSource: Applying Open Source Practices in Enterprises -

Unintended opensource forks -

Picasso's Bulls -

Reducing software maintenance cost -

Maintenance is costlier than development -

Gratitude -

Room for failure -

Language -

Open Source mindset -

Software automation workflows -

Package managers -

Productivity Tools for Developers -

Compound developer productivity by code reuse -

Case for package management in programming languages -

Concurrency and parallelism are not same -

writing business plan is harder than writing code -

Code is last -

Compiler is your friend -

Code and readability -

Friction -

Biases -

Moving Mind -

Its Easy to start - But is it? -

Lost Art of Asking Questions - Saying No -

Lost Art of Asking Questions - Evermore important today -

Lost Art of Asking Questions - Who drives the conversation? -

Lost Art of Asking Questions - The Broken Build Problem. -

Lost Art of Asking Questions - Working with in constraints. -

Lost Art of Asking Questions - Don't ask don't get. -

Lost Art of Asking Questions - Henrietta Leavitt's yardstick to the universe. -

Lost Art of Asking Questions - Go Concurrency Model -

Lost Art of Asking Questions - Neti Neti -

Lost Art of Asking Questions -

OpenSource and Art -

Doubt -

Introduction -