Notas
Índice cronológico de todas as notas do Scholion.
5359 notas · última:
A roadmap to working with legacy code: Webinar highlights
The webinar says legacy code slows business goals, so teams should document systems, set clear modernization goals, use AI with deterministic tools, and align product with engineering.
Instagram’s latest feature is a digital business card for your profile
Instagram is rolling out profile cards that share profile details and a QR code, making it easier to send your account to others and present yourself to potential collaborators, brands, or new friends.
the senior engineer death spiral
The post describes how engineers can spiral after a promotion or big project by overworking in silence, then argues for rebuilding momentum, visibility, and trust through steady, reliable teamwork.
You don’t need long hours to be a TOP software engineer. Make technology your ally, not your enemy
The page argues that software engineers should focus on output, deep work, and AI-assisted automation instead of long hours, since focused work and recovery produce better results than clocking time.
The hottest programming language in 2025: English
The page argues that AI is turning coding into a more declarative, language-based workflow, raising the baseline for developers while making speed, judgment, and project experience more valuable than syntax recall.
The easy road to become a TOP performer software engineer: Simplifying productivity
The article argues that software engineers should focus each day on three high-impact tasks, align work with team priorities, track outcomes, and use simple systems to reduce decision fatigue.
I Worked More and Achieved Less. How To Get Your Team Engaged (Don't Make My Mistake)
The author says taking all the work on yourself made the team less engaged. People are more committed when they invest effort, and ownership grows when they help build the group from the start.
How Top Engineers Structure Their Day to Maximize Their Productivity Without Burnout
The page argues that engineers can ship more by managing energy instead of time, matching deep work to peak hours, batching shallow tasks, and using location and automation to protect focus and reduce burnout.
How the best software engineers write technical designs (the blueprint for consistent results)
The article argues that technical design helps software engineers work more consistently by reducing ambiguity, aligning teams, and making workstreams easier to parallelize. It also outlines what a design should cover and how to structure it.
How I'm advancing my career without neglecting my life. "New year's resolutions" done right.
The post argues that career growth needs intentional focus, but also balance, reflection, and stage-based priorities. It uses life areas and yearly review to avoid burnout and plateaus.
Goal setting for productive engineers
The post contrasts top-down goals with tiny experiments for engineers working in unstable environments, using the motivation equation to explain when each approach helps or fails.
From Tech Docs to Blog Posts: How Writing Can Transform Your Career
The post argues that writing online improves technical writing by forcing clearer reading, reflection, and outcomes. It also says exposure reduces fear and makes repeated practice easier.
From Code to Words: How to Write Well for Software Engineers
The post argues that writing is a core engineering skill because it aligns teams, reduces meetings, and creates a shared record. It frames good writing as a practice built through Identify, Iterate, and Invite.
Always negotiate your deadlines! (How to gain trust and prevent working overtime)
The post argues that when a deadline is fixed and team capacity cannot change, engineers should negotiate scope instead of trying to absorb the work alone or refusing outright.
How to turn AI from a random code generator into a reliable teammate
The article argues that engineers should steer AI instead of trusting it blindly, using clear rules, review, and a steering doc so AI speeds up work without replacing judgment.
The Future of Podcasting
Podcasting grew with smartphones and Apple, but discovery, distribution, data, and monetization remain hard. The piece argues publishers may need their own apps or a new platform model to make audio sustainable.
AI isn’t “just predicting the next word” anymore
The post argues that modern AI has moved beyond simple next-word prediction: newer systems solve problems through path-finding, use tools and feedback, and already show useful and risky abilities.
Problem Driven Development
The post argues that technical roadmaps should start from concrete problems in pages, SLOs, cost, failures, and wasted time. It also applies the same logic to tech debt and roadmap prioritization.
The real 10x developer makes their whole team better
The article argues that engineering success depends less on mythical 10x developers and more on social learning communities and communities of practice that help entire teams learn, share knowledge, and perform better.
The evolution of fullstack engineers
The episode traces how fullstack work widened from front end and back end split to broader, more flexible roles shaped by JavaScript, APIs, frameworks, security, and deployment needs.
The problem with the tech debt mindset
The episode argues that tech debt covers several different problems, from outdated choices to replatforming, and that teams need a clear, quantified way to balance maintenance against features.
Are remote workers more productive? That’s the wrong question.
The article argues that the productivity debate misses the main issues around remote work. Flexibility, happiness, accessibility, diversity, retention, and management quality matter more than a simple office-versus-home comparison.
Just laid off? Nervous about possible layoffs? Here’s what to do.
The article says to process a layoff first, then lean on your network, polish your resume, apply broadly, and keep perspective because tech skills remain in demand.
Code Review: A New Developer’s Guide
The article explains how new developers can write clearer pull requests, test code like users, and give feedback carefully so code review helps the team improve software and grow together.
What Do Programming and Crocheting Have in Common? These 3 Things.
The author compares crochet and programming through deliberate practice, problem-solving, and creative solutions, showing how each skill improves with attention, debugging, and adaptation.
You Can Grow Your Developer Intuition
The page argues that software development depends on intuition as much as analysis, and that developers can strengthen it through code review, pattern recognition, practice, and reflection.
Avoid Walking In Circles While Blazing Trails: Advice for Early Stages of Project Development
The article says early project work should accept uncertainty, focus on the most important requirements, build an MVP, choose tech with practical criteria, and keep team and client aligned.
Here’s Why Angular is the Better Choice for Long-Term Projects
The page argues that Angular is better than React for large, long-term projects because it includes built-in tools, enforces structure, scales more predictably, supports testing, and helps teams build maintainable code.
AI Coding Degrades: Silent Failures Emerge
The author says AI coding assistants have plateaued in 2025 and now fail more quietly, often producing code that runs but gives wrong results. He links this to training on user-accepted outputs.
“AI will replace all the jobs!” Is Just Tech Execs Doing Marketing
The post argues that claims about AI replacing 20-50% of jobs are not supported by history or current labor data. It says AI is more likely to shift hiring and create jobs than to eliminate work at scale.
The product manager role is a mistake
The article argues that putting career product managers in charge of software product decisions often replaces vision with process, politics, and mediocrity, while better results come from teams of strong specialists.
What is Functional Programming?
The article defines functional programming as building programs mainly by composing functions, supported by higher-order functions, first-class values, immutable data, ADTs, and limited effects. It also distinguishes casual from pure FP and argues most value comes from the casual form.
Preventing SQL injection in C# with Entity Framework
The page explains how SQL injection happens, why string concatenation is risky, and how Entity Framework reduces that risk with LINQ, FromSqlInterpolated, and explicit parameters in FromSqlRaw.
Stuck in a Rut as a Programmer? It’s Not Your Fault.
The page argues that programmers often feel stuck because their work becomes repetitive and their language or stack was not really chosen by them. To break the rut, it recommends learning, writing, researching, pet projects, sharing, and reading.
Why Developers Are Poor Testers and What Can Be Done About It
The page says developers often test poorly because they protect their own code, simplify problems, miss small flaws, focus on happy paths, and lack user perspective. It then suggests ways to improve testing.
Your job is to deliver code you have proven to work
Simon Willison argues that AI-assisted development still requires proving changes work through manual testing and automated tests, with humans accountable for the result and coding agents helping only if they can verify their own output.
Forget the resume, kill on the cover letter
The post argues that resumes mostly keep applicants from being rejected, while a strong cover letter is what gets attention, sets tone, and helps a candidate reach the interview.
Staff, principal, distinguished: Engineering career levels explained
The article outlines engineering career tracks, focusing on the individual contributor ladder from Engineer I to distinguished engineer, and explains why a clear hierarchy helps career growth, clarity, and motivation.
21 Frontend System Design Concepts for Software Engineers
The article frames frontend engineering as system design in the browser, covering rendering models, performance, state, data fetching, architecture, UX, security, and observability.
Top 10 Rules of Continuous Integration
The article lists ten CI practices to improve speed, reliability, and code quality, from version control and frequent commits to automated testing, checks, monitoring, and performance tuning.