GDG DevFest Armenia 2025 | Programming Practices for Developing Quality Software (Eng)

Value of the Information & Strength of the Argument

The talk provides valuable, practical advice for software engineers, emphasizing principles that are widely recognized in the industry. The arguments are presented clearly and are supported by real-world examples, such as the JavaScript automatic semicolon insertion pitfall and the student’s factorial function. The speaker’s credibility is enhanced by his experience and his references to respected figures like Douglas Crockford and Uncle Bob. However, the talk is largely anecdotal and lacks empirical evidence or formal citations, which slightly weakens the scientific rigor. The advice is actionable and likely to improve code quality if followed.

Scientific Rigor, Source Quality, Title Accuracy

The talk is based on the speaker’s personal experience and does not cite specific sources. The only external reference is the DevFest Armenia website, which is not a source for the content. The title accurately reflects the content, which is a collection of programming practices. The talk is not a scientific study but an expert opinion, so the lack of citations is acceptable. The content aligns with established software engineering principles, such as those found in ‘Clean Code’ by Robert C. Martin, though these are not explicitly mentioned. The talk’s strength lies in its practical applicability rather than its academic rigor.

The title accurately reflects the content, which focuses on programming practices for developing quality software.

8/10

The talk is based on the speaker's 20+ years of experience in software development, presenting widely accepted best practices. The content is coherent and aligns with established software engineering principles, though it lacks formal citations or empirical evidence.

Markers derived by PSI from the transcript: the creator did not define chapters.

• 00:00Introduction: speaker introduces the talk as a 'brain dump' of lessons learned over 20 years in software development.
• 01:00Reference to Douglas Crockford: software is the most complicated thing people make; impossibility of testing for perfection.
• 03:00First recommendation: keep APIs as small as possible, as they are promises that are hard to keep.
• 05:00Importance of automated testing to ensure promises are kept after code changes.
• 07:00Discussion of coupling: strive for loose coupling; introduction to message queues and pub/sub for decoupling.
• 10:00Inheritance vs composition: inheritance creates tight coupling; prefer composition.
• 13:00Emphasis on writing readable and simple code; avoid complicated code.
• 16:00Minimize code size: eliminate dead code and avoid adding unnecessary functions.
• 19:00Follow coding conventions: example of automatic semicolon insertion in JavaScript.
• 22:00Functions should ask for only what they need; example of passing an ID instead of a manager object.
• 25:00Minimize variable scope: example of a student's factorial function with a leaked variable.
• 28:00Minimize side effects: prefer pure functions for easier debugging and testing.
• 31:00Be careful with recursion: tail call optimization and its absence in many languages.
• 34:00Importance of good naming: use intuitive names, avoid negatives, name magic values, keep names symmetric.
• 37:00Avoid nested if statements for clarity; conclusion with Uncle Bob's advice and Q&A.

• DevFest Armenia 2025 — The talk was presented at this conference, and the link is provided in the video description.

• Clean Code: A Handbook of Agile Software Craftsmanship — The talk's emphasis on readable code and avoiding bad code aligns with the principles in this book.