Notas
Índice cronológico de todas as notas do Scholion.
5359 notas · última:
Software Architecture and the Art of Experimentation
The article argues that architectural decisions should be treated as experiments. Minimum Viable Architectures test viability, supportability, and future change so teams can catch wrong assumptions before costs grow.
Why Bad Code Exists
The article says bad code usually comes from process and context: no active review, no editing or refactoring, weak technical knowledge, time pressure, fear, and lack of care or investment in quality.
How to Kill the Code Review
The essay argues that manual code review no longer scales with AI-generated code, and that human approval should move upstream to specs, constraints, and deterministic verification.
Design Docs at Google
Explains how Google uses design docs to capture high-level implementation strategy, surface trade-offs early, align teams, and preserve design decisions through review and iteration.
If You Want to Get in the Tech Space: Become A Software Developer
The article argues that software development remains in demand despite AI tools and layoffs, and says the path in starts with computer science knowledge and practical projects.
What’s Your Superpower? Understanding Its Strengths, Shadow Sides & How to Use It in the Workplace
The article explains superpowers at work as individual strengths that help teams, warns that each strength has a shadow side, and argues that team building should combine different abilities and perspectives.
What is a Systems Map?
A systems map lays out relationships and interactions among stakeholders in a system. It helps people zoom out, spot gaps and opportunities, and decide where to look more closely.
Creative Problem-Solving Skills: The Value of Curiosity and Play
The page argues that curiosity helps you stay with a problem long enough to understand people and context, systems thinking reveals layers beneath visible behavior, and play opens space for new solutions.
Among the Agents
The author argues that coding agents have become capable enough to do substantial real work, but the real shift is using them well. He sketches practical limits, risks, and likely effects on software, data, jobs, policy, and growth.
How to Think in Systems for Greater Impact
The article argues that human-centered systems thinking combines systems analysis with design methods to solve complex problems by considering stakeholders, constraints, zooming in and out, and systems mapping.
Become a Better Programmer: 7 Habits to Grow
The article says better programming comes from strong basics, deliberate problem-solving, clean code, debugging, documentation, networking, and building real projects.
Out-of-the-box Elixir telemetry with Phoenix
The article explains Phoenix’s built-in telemetry, how metrics are defined in telemetry.ex, how events feed multiple metrics, and how clustered Elixir lets the dashboard attach to other nodes.
How to think in writing
The essay argues that writing makes thoughts rigid enough to inspect, exposes cracks in vague ideas, and helps refine them by making claims, stretching explanations, and testing counterexamples.
Establishing a Culture of Storytelling
IDEO explains how storytelling became part of its culture, using it to make abstract work clearer, connect teams across silos, and create positive influence around ideas.
Procrastinating? Read this. (Right now.)
The post links procrastination to the desire to avoid suffering and says that noticing the impulse, pausing, and sitting with discomfort can make the urge fade; meditation helps create that pause.
Systems Thinking vs Design Thinking, What’s the Difference?
The page contrasts systems thinking and design thinking, outlining each approach, their strengths and limits, and how human-centered systems thinking combines both to address complex problems more effectively.
Build Confidence in Your Strategy with Small Tests
The page argues that strategy should be tested before implementation, using small, creative, evidence-gathering experiments to reduce uncertainty and build confidence in choices.
How to effectively lead leaders in game development
Charity Joy outlines how to lead managers by using curiosity, clear communication, coaching, facilitation, trust, and consistency to support leaders and keep teams aligned.
What Is Systems Thinking? A Beginner’s Guide to Mindsets, Tools, and Examples
Systems thinking is presented as a holistic way to understand complex problems by seeing connections, using reframing, and applying three mindsets to move across scales, perspectives, and assumptions.
Why are senior developers learning low-code and AI tools? [Adrian Twarog Interview #129]
Interview with Adrian Twarog about how he built his skills through work projects, design tutorials, early GPT content, and staying current with AI and low-code tools while working in Perth.
9 Skills You’ll Need to be Resilient This Year
The page argues that resilience comes from a growth mindset and names nine skills professionals should cultivate: curiosity, tension, better questions, empathy, creative options, reflection, metacognition, iteration, and fun at work.
Skills You Need to Become a Backend Developer – A Roadmap for Beginners
The article maps a backend learning path from databases and server-side languages to APIs, debugging, cloud deployment, and advanced projects, while listing common tools like MySQL, MongoDB, Node.js, and Git.
React Best Practices Ever Developer Should Know
The guide recommends keeping React state immutable, avoiding useState for everything, deriving and computing values during render when possible, using unique keys, and leaving useEffect for real side effects.
4 Tips for Navigating Ambiguity
IDEO U says teams handle ambiguity better with high trust, shared naming of unknowns, curiosity about alternatives, and small experiments instead of fixed plans.
How to Help Someone with Their Code Using the Socratic Method
The article argues that giving direct answers blocks learning, while Socratic questioning helps learners reach conclusions themselves and strengthens debugging, assumptions-checking, and long-term reasoning.
Microsoft Donates Mono To WineHQ
Microsoft donated Mono to WineHQ, which will steward the project upstream while Microsoft keeps a modern fork in dotnet/runtime and tells active users to move to .NET.
How to Create Software Architecture Diagrams Using the C4 Model
The page explains the C4 model as four zoom levels for describing software architecture and shows how Structurizr DSL and GitHub Actions can automate diagram creation and publishing.
How to Build Good Coding Habits as a New Python Developer
The article lists six habits for new Python developers: follow PEP 8, use the newest supported Python version, comment code clearly, use a linter, rely on built-in tools, and fix issues quickly.
Atualização da AOR: Recessão ou vibecessão?
O texto diz que a queda nos dados de sentimento pode ou não virar fraqueza real, mas que a balança de risco hoje pesa contra a economia. O painel segue verde, embora margens e comércio exijam atenção.
Software Engineering Job Market 2026: Data, Trends and Outlook
The market splits between fast-growing AI roles and weaker entry-level generalist hiring. Pay rises with level and AI skills, while interviews now test AI systems, cloud, and deployment experience.
How to Know You’ve Become a Senior Programmer
The article argues that senior programmers become more cautious because they better see the costs, risks, and side effects of every change, especially after years on the same codebase and through maintenance work.
From Chaos to Efficiency: How to Minimize Distractions in Software Development
The page argues that software developers need time management, focus blocks, clear boundaries, automation, and regular adjustment to reduce interruptions, protect quality, and limit task buildup.
The types of companies you can work for and what they do for your career
The post breaks down common company archetypes by size, growth, pressure, and autonomy, and shows how each one shapes learning, visibility, pay, stability, and career growth.
Losing a dev means losing a treasure
The article argues that programmers accumulate knowledge, autonomy, and project context over time, so losing one can disrupt delivery. Retention depends on tools, autonomy, and real involvement in decisions.
How to build modern gaming services — with reference architecture
The page argues that modern gaming backends should separate game content from shared plumbing and meet five demands: near-instant consistency, high availability, elastic scaling, low latency, and minimal complexity.
Meta planning sweeping layoffs as AI costs mount
Reuters reports that Meta is preparing layoffs that could hit 20% or more of staff as it tries to offset heavy AI infrastructure spending and adjust to AI-assisted work.
The Decline Of Mobile Development
The page argues that Android and iOS development has become harder because of OS mandates, abstraction, long build times, testing difficulty, and platform control, pushing many developers toward the web.
Write Down the Plan
The post argues that writing down and sharing a plan improves thinking, creates alignment, and increases visibility, making it a useful habit for software engineers and career growth.
Why external authorization is essential for modern software architecture
The page argues that external authorization separates access-control logic from application code, reducing duplication, easing updates, improving testing, auditing, and deployment across changing systems.
How To Get Promoted (Without Getting Lucky)
The piece argues that promotion to Staff comes from sustained impact, leverage, strong internal visibility, collaboration, and clear communication with your manager, not from luck or effort alone.