Bikey Bonn Kleiford Seranilla - Queuing Theory
Liz Thompson - Queueing theory (simple)
SREcon24 Americas - System Performance and Queuing Theory - Concepts and Application
Python is one of the tools in my toolbox, so I never used it exclusively. This means i need to get an update, occasionally.
Rant mode on
They want to have an expressive language, so they keep adding features upon features to it, instead of caring too much about performance (which means that no JIT - just-in-time compiler - has been added to cpython).
I would have thought that typescript is gaining over python on github, because node.js is JIT based, unlike cpython, but that guess was wrong: github article. The github article suggests a different reason:
Major 2025 Update: PostgreSQL now recommends identity columns over serial types. Drizzle has fully embraced this change.
import { pgTable, integer, text, timestamp, varchar } from 'drizzle-orm/pg-core';| import React, { useEffect, useState } from "react"; | |
| import Animated, { | |
| useSharedValue, | |
| useAnimatedStyle, | |
| runOnJS, | |
| } from "react-native-reanimated"; | |
| import Ionicons from "@expo/vector-icons/Ionicons"; |
| MIT License | |
| Copyright (c) 2022-present, cayter | |
| Permission is hereby granted, free of charge, to any person obtaining a copy | |
| of this software and associated documentation files (the "Software"), to deal | |
| in the Software without restriction, including without limitation the rights | |
| to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
| copies of the Software, and to permit persons to whom the Software is | |
| furnished to do so, subject to the following conditions: |
| // Based on https://walkthrough.so/pblc/QCawSCKwOQLn/creating-a-custom-editorjs-block-tool-with-react | |
| import type { | |
| API, | |
| BlockAPI, | |
| BlockTool, | |
| BlockToolConstructorOptions, | |
| } from '@editorjs/editorjs' | |
| import ReactDOM from 'react-dom' |
This document is a reference for common testing patterns in a Django/Python project using Pytest.
Contents:
| from alembic import config | |
| from alembic import script | |
| from alembic.runtime import migration | |
| import sqlalchemy | |
| import exceptions | |
| engine = sqlalchemy.create_engine(DATABASE_URL) | |
| alembic_cfg = config.Config('alembic.ini') |
Concurrency is a domain I have wanted to explore for a long time because the locks and the race conditions have always intimidated me. I recall somebody suggesting concurrency patterns in golang because they said "you share the data and not the variables".
Amused by that, I searched for "concurrency in golang" and bumped into this awesome slide by Rob Pike: https://talks.golang.org/2012/waza.slide#1 which does a great job of explaining channels, concurrency patterns and a mini-architecture of load-balancer (also explains the above one-liner).
Let's dig in: