Avoid these things:

• Asking the developer how things should work: It’s your responsibility to know how a feature should work; if you don’t, how can you test it?

• Reporting bugs outside of the ticket: Avoid informal bug discussions, as they waste time for you and your team.

• Using vague phrases like “This does not work properly”: ‘Properly’ is unclear—specify exactly what’s wrong.

Егор рассказывает про ООП и его анти-паттерны

Instead of trying to shorten the time that our builds take, we order and chain them by complexity, thus gradually reducing the risk.

PostgREST is a standalone web server that turns your PostgreSQL database directly into a RESTful API. The structural constraints and permissions in the database determine the API endpoints and operations.

Sounds like a way to write less code. I skimmed through the reference, looks cool. PostgREST is written in Haskell for some reason though.

A story of a Julius who lacks knowledge but has good charisma. There's a lot to learn from such Julii.

Если код работает, это не значит, что задачу пора закрывать. От двадцати минут, потраченных сверху, вреда не будет — прод не сгорит, менеджер подождет. Зато спасет день коллеги, который вкатывается в проект.

We all know that naming things in programming is hard. If you’ve read this entire post it just got a little bit harder.

We are adding a new generated code API to Go Protobuf.

Software Carpentry is a volunteer project dedicated to teaching basic computing skills to researchers.

Не люблю, когда для обхода данных нужна пагинация. Всякие LIMIT/OFFSET,nextToken и прочие костыли.

Да!

PostgreSQL Query Plan Visualizer add new plan

Идемпотентность — звучит сложно, говорят о ней редко, но это касается всех приложений, использующих API в своей работе. Меня зовут Денис Исаев, и я руковожу одной из бэкенд групп в Яндекс Такси. Сегодня я поделюсь с читателями описанием проблем, которые могут возникнуть, если не учитывать идемпотентность распределенных систем в своем проекте.

Сборник различных сценариев автоматизации и справочных материалов

Есть инструкция для почтового сервиса в кластере

There is a single advice I would give to anyone writing software, and specially to great devs : Always optimize your code for your most junior developers. I agree that it is not a very popular advice, but it is the one that, in my experience, give the biggest bang for the buck.

any variable named SECONDS will automatically increment every second. Bash is bonkers

используйте неизменяемые объекты, не допускайте частичной инициализации, требуйте обязательные поля сразу – не надейтесь, что кто-то заполнит их позже

A specification for adding human and machine readable meaning to commit messages

Skip brings Swift app development to Android

It is very important to conduct regular code reviews within every software team, but it is not so easy to do them right; here are a few typical pitfalls.

When project scope is perfectly decomposed and management rules are clear and strict, speed of delivery is the virtue, not the quality.

The concept of feature flags is simple – it’s essentially just an if. This makes it a very powerful concept!

Жетбрейнсы рассказывают о концепции фича-флагов

Гайд, как правильно писать сообщения для коммитов. О важности упоминания не просто того, что делает изменение, а зачем оно это делает. Очень мудро.

A properly configured distributed team of programmers can and must deliver a higher quality of code than a co-located one.

Equity or cash? These days, it seems that working for equity is the way to become a millionaire. I don't think it's true.

I often hear the question of how to become a senior developer; this is my story and my advice; hope it helps you.

If you actively use Stack Overflow as a coding instrument, your reputation will be lofty; if you don't use it, you're not really a professional software engineer.

Twenty years ago we worried about performance. Now it is time to worry about maintainability, even though it often compromises performance.

An active open source contribution is a good habit for a software developer who is passionate about his or her job.

In XDSD everybody is motivated to produce tangible and meaningful results. That's why we don't use emails, Skype, HipChat or phone calls.

Patent-pending methodology of breaking down big tasks into smaller ones is explained in the article, by example in Java

Programmers are expensive and difficult to control; here are a few tricks to keep them underpaid and happy, for a while.

How about we measure the amount of times programmers touch the lines. Instead of counting the number of lines we’ll count how many times they were actually modified—we can get this information from Git (or any other SCM). The more you touch that part of the aircraft—the more effort you spent on it, right?

I called it Hits-of-Code (HoC) and created a small tool to help us calculate this number in just one line.

What a nice idea! I installed this program and ran it on Betula and Mycorrhiza codebases. For Betula it's 26350 HoC, for Mycorrhiza it's 137208 HoC. Yeah, Betula is still comparatively young! Hey, what about Mycomarkup? 23443. Oh wow, just a little less than Betula. I expected a small number.

Никита рассказывает про оптимизации в Го.

Треш, конечно. Язык приколов

Uiua (wee-wuh) is a general purpose, stack-based, array-oriented programming language with a focus on simplicity, beauty, and tacit code

Список игр, которые учат компьютер сайенсу

In many other languages, you have to not only evaluate testing libraries, but also write your tests in a style that complies with that library’s expectations. Gophers are blessed to have a thoroughly adequate solution out-of-the-box, and even further blessed to have an active ecosystem where folks are making in-depth testing a walk in the park.

A source-control branching model, where developers collaborate on code in a single branch called ‘trunk’ *,
resist any pressure to create other long-lived development branches by employing documented techniques. They
therefore avoid merge hell, do not break the build, and live happily ever after.

Redict is a distributed key/value store (a remote dictionary, if you will).

Redict is an independent fork of Redis®1 OSS 7.2.4 licensed under the Lesser GNU General Public license (LGPL-3.0-only). Redict is not affiliated with Redis®.

Достаточно ли отдельных энвайрментов, или нужно тестировать в продакшене, и как это делать безопасно.

Узнал про дебаггер много нового

Innovation tokens and whatnot.

Я согласен с тем, что логику нужно разносить по сервисам. Но сервисы должны использовать общую шину данных: базу, очередь сообщений, файлы в S3 в конце концов. Гонять друг другу JSON выглядит хорошо в теории, но на практике — фу.

Условный Постгрес выплюнет миллион записей за доли секунды. Забрать этот же миллион из другого сервиса — приключение на неделю. Тут и метрики, лимиты, квоты, сетевые спайки, etc… А когда таких запросов несколько, сервис ложится спать.

Fast, powerful, yet easy to use template engine for Go. Optimized for speed, zero memory allocations in hot paths. Up to 20x faster than html/template

SQL Polyglot is a quick way to see if a particular SQL feature is supported in different database systems. Write a query and see it run anywhere from PostgreSQL to DuckDB without leaving your browser.

package src

type config struct {
    // Required
    foo, bar string

    // Optional
    fizz, bazz int
}

// Each optional configuration attribute will have its own public method
func (c *config) WithFizz(fizz int) *config {
    c.fizz = fizz
    return c
}

func (c *config) WithBazz(bazz int) *config {
    c.bazz = bazz
    return c
}

// This only accepts the required options as params
func NewConfig(foo, bar string) *config {
    // First fill in the options with default values
    return &config{foo, bar, 10, 100}
}

func Do(c *config) {}

You’d use the API as follows:

package main

import ".../src"

func main() {
    // Initialize the struct with only the required options and then chain
    // the option methods to update the optional configuration attributes
    c := src.NewConfig("hello", "world").WithFizz(0).WithBazz(42)
    src.Do(c)
}