Programming
Software development: programming languages, coding, libraries and frameworks, software engineering and architecture, source control, developer tools, databases, and infrastructure.
-
Sonar sonarsource.com
-
Railway railway.app
-
Prisma Postgres prisma.io
-
Loops loops.so
-
Lingo.dev lingo.dev
-
Kilo Code kilocode.ai
-
JetBrains AI jetbrains.com
-
GitLab gitlab.com
-
Fine fine.dev
-
Encore encore.dev
-
Digital Ocean App Platform digitalocean.com
-
DeveloperHub developerhub.io
-
daily.dev daily.dev
-
Coval coval.dev
-
CodSpeed codspeed.io
-
CodeSquire codesquire.ai
-
CodeParrot codeparrot.ai
-
Fern buildwithfern.com
-
Better Stack betterstack.com
-
source x.com
).
-
sacrificial lamb product x.com
a massive unpopular re-architecture required to pave the way for future innovative release. That's the cautionary tale of why you should be ready for intense criticism and adversity, if by chance or fate your wander down the path of monumental changes in a business software.
-
Devs I really enjoy pairing with x.com
“Don't act like know-it-all; Openly admit if they don't know something; Try to figure stuff out together”.
-
source x.com
).
-
Fizz Buzz Test wiki.c2.com
“Designed to help filter out the 99.5% of programming job candidates who can't seem to program their way out of a wet paper bag.”
-
Detecting Agile Bullshit web.archive.org
US Department of Defense guide to detect software projects that are really using agile development versus those that are simply waterfall or spiral development in agile clothing (“agile-scrum-fall”).
-
How to Freaking Find Great Developers By Having Them Read Code web.archive.org
“Instead of writing code, consider having the candidate read existing code and talk about how it works. 1) Reading code is 95% of what a developer does as part of their job. 2) A candidate can tell you a lot about their programming skill in the first five minutes of reading. 3)…
-
The Technical Interview is an Ego Trip web.archive.org
Starts with anecdote of developers using a job interview as a vehicle to demonstrate their superiority. Then the author details a reasonable interview process that is trying to not waste anyone's time.
-
Industry Data Models web.archive.org
A huge list of database templates collected over 25 years by Barry Williams to represent any business process.
-
FizzBuzz 2.0: Pragmatic Programming Questions for Software Engineers web.archive.org
Five multiple-choice questions to easily separate the real software engineers from the rest.
-
The Horrifically Dystopian World of Software Engineering Interviews web.archive.org
The dark side on relying too much on algorithm challenges.
-
Developer Tropes: "Google does it" tomaytotomato.com
It's cargo-cultish to imitate the big names in our industry as a path to success. Instead, the take home from this article “would be that managers and other leaders should be like ecologists; who measure, observe and nurture their ecosystems. Doing so will help build a unique…
-
The principles of Amazon service-oriented collaboration theregister.com
A compilation of anonymous sources from AWS which ehoes the interview above: “teams are ostensibly autonomous and can make any important decision needed to meet their goals.”
-
Apple Aperture: Senior QA techreflect.net
How not to manage projects approaching deadlines: “cutting finished features, yelling at people, and working people to the point of nervous breakdowns. Then they came upon a brilliant idea: let's steal over a hundred engineers from other teams and then the project will…
-
The Most Important Performance Management Rule For Software Engineers staysaasy.com
“Merge code every week. That's what you should be saying to your new Software Engineering hire.”
-
StaffEng staffeng.com
Once you've reached the Senior Software Engineer level, you're at the crossroad. Either you pursue engineering management or continue down the path of technical excellence to become a Staff Engineer. This isa collection of guides about the later position.
-
Requirements volatility is the core problem of software engineering stackoverflow.blog
“Start by accepting that change is inevitable. (…) As a consequence of this, software is never finished, only abandoned. (…) This means that no software product is ever exactly, perfectly satisfactory.”
-
Avoiding burnout as an ambitious developer stackoverflow.blog
“Be willing to say no; Know what you don't want; Use your energy level realistically; Be kind to your future self”.
-
Write an Excellent Programming Blog speakerdeck.com
Tips on structure and style to produce great blog posts.
-
Software effort estimation is mostly fake research shape-of-code.com
“The NASA dataset contains 93 rows (that is not a typo, there is no power-of-ten missing), COCOMO 63 rows, Desharnais 81 rows, and (…) the China dataset contains 499 rows.”
-
Algorithm for writing a scientific manuscript sci-hub.st
A process to guide the preparation and refinement of manuscripts.
-
Developer Roadmaps roadmap.sh
💸 Very high-level guides and paths to learn different practice and tools.
-
The Evolution of Management: Transitioning up the ladder queue.acm.org
Describe the path and expectations at each management level.
-
A Conversation with Werner Vogels, Learning from the Amazon technology platform queue.acm.org
Scaling systems is not only a technical challenge. It has to be about teams and culture too. One lesson learned from the early days of AWS: “Giving developers operational responsibilities has greatly enhanced the quality of the services, both from a customer and a technology…
-
Psychology Today: How Programmers Can Avoid Burnout psychologytoday.com
“Veteran software developers often recommend to: 1. Work at a place where you can grow; 2. Build transferable skills; 3. Have creative outlets and create a space to focus on yourself, switch off, and relax; 4. Of course, there's always the nuclear option: make your money and…
-
Organizational Skills Beat Algorithmic Wizardry prog21.dadgum.com
“When it comes to writing code, the number one most important skill is how to keep a tangle of features from collapsing under the weight of its own complexity.”
-
Goodbye, Clean Code overreacted.io
“My boss invited me for a one-on-one chat where they politely asked me to revert my change. I was aghast. The old code was a mess, and mine was clean! (…) I see now that my 'refactoring' was a disaster in two ways: I didn't talk to the person who wrote it; My code traded the…
-
Essays on object-oriented software engineering openlibrary.org
.
-
How Big Tech Runs Tech Projects and the Curious Absence of Scrum newsletter.pragmaticengineer.com
There's an interesting table in this article on the strereotypes of companies, their funding models, main engineering actors, and their central methodologies.
-
source news.ycombinator.com
).
-
source news.ycombinator.com
).
- next page of items loading…
