#Software-Development
78 notas · última:
The ultimate checklist to becoming a development team leader
The article lays out a checklist for developers moving into team lead roles, centered on mastering the domain, handling production, onboarding others, taking on large tasks, and joining or leading important meetings.
Why ORMs Aren't Always a Great Idea
The post argues that ORMs can speed up development and help beginners, but they also hide database behavior, limit control, and can hurt performance and maintenance as systems grow.
Hard Things in Computer Science
The post argues that computer science has many hard problems beyond cache invalidation and naming things, including timezones, estimates, distributed systems, and proving code is bug-free.
What senior developers DO and DO NOT want to see in your resume
Senior developers screen resumes for relevance, readability, and signs the applicant read the role. The article recommends a master document, selective tailoring, and writing like a human.
A Better Way To Code: Documentation Driven Development
The article argues that writing documentation first can clarify API shape and project scope before code is implemented, often reducing later refactors and helping teams communicate requirements more clearly.
A ‘wise’ guy tactic for effective code review practice? Use checklist templates!
The article argues that code review works better with short checklist templates. It covers automated checks, merge conflicts, commit messages, PR size, requirements, readability, coding standards, libraries, duplication, tests, and documentation.
Books to Read as a Developer
The post lists books a developer should read for programming practice, code quality, design patterns, legacy code, team work, and software design principles across languages.
How to Be Lazy and Stay Calm
The post argues that, when a bug sits in unfamiliar legacy code, developers should avoid self-blame, report the codebase’s weaknesses through tickets, and narrow the scope until the work fits a short paid task.
Are you a good developer already?
The post says a good developer writes working code, keeps solutions simple, avoids unnecessary repetition, keeps learning, works well in teams, seeks feedback, and communicates problems early.
Exploring the path of a new and unfamiliar codebase
The author outlines a practical way to get comfortable in a new codebase: explore the product, set up the environment, pick simple bugs, debug systematically, and ask for help when needed.
Top websites to find a remote programming job in 2020
The page lists websites where software developers can look for remote jobs and says it is a work in progress. It also invites readers to suggest which sites are best.
How I landed a dev job that didn't exist
John Sonmez says he turned a QA lead opening at HP into a developer role by working closely with developers, earning their support, and creating a role the company had not posted.
How to "opt out" of the job hunt meat grinder
John Sonmez argues that chasing job postings puts developers in a brutal hiring funnel, while building expertise and visibility can make opportunities come to them and improve salary leverage.
The software developer hourly rate moonwalk
John Sonmez says his hourly rate rose to $75, then fell to $56, $45, and $35 after his first real programming job ended. He says he later found a process that improved his career and brought job offers.
Trunk-based Development vs. Git Flow
The article compares Git flow and trunk-based development, showing how each workflow shapes branching, review, speed, and control, and when each fits open source, junior teams, startups, or senior teams.
Métricas para Projetos Agile #4
O texto explica por que medir WIP ajuda a enxergar gargalos, prever capacidade e reduzir trabalho quase pronto, e defende limites de WIP para melhorar o fluxo do time.
Why software is a craft [and also an industry]
Software development is presented as neither pure craft nor fully rule-driven industry. It needs basic methods and planning, but still depends on context, judgment, and adaptation as unknowns appear.
ShuHaRi
Shu-Ha-Ri describes learning a technique in three stages: precise imitation of one master, learning principles from other sources, and then adapting practice through one’s own experience.
Developers Who Can Build Things from Scratch
The article describes the kind of developer needed for early product work: someone who can turn ideas into a product, choose tools pragmatically, learn as requirements change, and explain tradeoffs clearly.
4 Reasons to Employ Older Developers
The article argues that older developers are a strong hiring choice because they are available, stable, bring specialist knowledge, and handle office politics well.
The thing with code clarity: you can't be proud of something I can't read
The post argues that code clarity matters because code must communicate to people as well as computers, and that readable, maintainable code comes from naming, structure, spacing, comments, and refactoring.
Nobody cares about your code
The article argues that code is only a tool: programmers are judged by the product and its features, while code quality matters because it helps deliver that product well.
Consensus-Driven Development
The article argues that software teams should use consensus, not majority voting, to make decisions. It outlines ways to build agreement, handle dissent, and know when a group decision is appropriate.
Developers Shouldn’t Measure Twice, Cut Once
The post argues that the “measure twice, cut once” rule fits construction, but not software work. In programming, rough estimates and early coding are more useful than long planning and estimation meetings.
7 reasons why frameworks are the new programming languages
The piece argues that modern coding centers on frameworks because most work now means using APIs, inheriting existing code, relying on algorithms, and letting tools handle syntax.
11 Rules All Programmers Should Live By
The article lays out 11 guidelines for programmers: treat technology as a tool, favor clarity over cleverness, write only necessary code, test work before shipping, keep learning, and simplify.
Should you hire a software developer talent agent?
The article says some developers can benefit from agents or recruiters because project-based work, negotiation, and job hunting take time. It weighs representation against the fees and the type of work you want.
Three Reasons Why Your Software Is So Far Behind Schedule
The article says delayed software projects often share three signs of technical debt: new developers take too long to onboard, test suites grow unwieldy or break down, and teams keep running their own servers instead of moving to the cloud.
What Makes a Great Software Developer?
The page collects advice for software developers: learn on the job, manage your career, avoid fads, and value autonomy. It also argues that durable, maintainable software matters more than speed.
What I Wish I Knew When I Started My Career as a Software Developer
A software developer reflects on career management, politics, autonomy, salary moves, and technical growth, urging young developers to learn continuously and avoid costly professional mistakes.
Why I Left the .NET Framework
The author says .NET was strong, but its defaults narrowed choice, pushed developers inward, and kept implementation details ahead of the model and business behavior.
Don’t Overwhelm Yourself Trying to Learn Too Much
The post argues that software developers should avoid trying to master too many technologies at once, and instead rely on just-in-time learning, a solid base, and one or two areas of focus.
Developers Need to Broaden Their Range
Mike Loukides argues that full-stack work means broad familiarity with the stack, design, hardware, networking, cloud, data, and tooling, so developers can collaborate well across specialties.
Three Types of Interview Questions Software Developers Should Expect
The article groups technical interview questions into computer science and algorithms, project and puzzle, and behavioral and informational, and says candidates should prepare to explain their reasoning clearly and specifically.
Agile Is Dead (Long Live Agility)
Dave Thomas argues that “agile” has been emptied out by consulting, marketing, and misuse as a noun, and that software teams should return to the manifesto’s values as practical agility.
It's Not A Bug, It's....
The page argues that a defect exists only when code differs from the requirements specification, and that many “defects” are really missing, incomplete, or inconsistent requirements that should be tracked as change requests.
4 Things I Wish I Would Have Known When I Started My Software Development Career
The author says his career improved only after he stopped chasing one right way, learned by building, focused on broader skills, joined community, and made side projects a priority.
The Real Pain of Software Development [part 2]
The author describes coding-related pain, what treatment and workplace changes helped him, and why breaks, posture, stress management, and movement matter more than one perfect fix.