| | It's not done if... (charemza.name) |
| 4 points by michalc 15 days ago | past |
|
| | It's not a hack to satisfy known requirements (charemza.name) |
| 52 points by michalc 30 days ago | past | 58 comments |
|
| | Ordering work: a skill and culture gap (charemza.name) |
| 2 points by michalc 31 days ago | past |
|
| | Rules when making data dashboards (charemza.name) |
| 1 point by michalc on Feb 4, 2024 | past |
|
| | Questions to ask yourself when talking with users (charemza.name) |
| 3 points by michalc on Aug 14, 2022 | past |
|
| | How to offer better downloads: 4 sets of HTTP headers (charemza.name) |
| 2 points by michalc on Feb 28, 2021 | past |
|
| | S3 is not a filesystem, and that's OK (charemza.name) |
| 2 points by michalc on Feb 14, 2021 | past |
|
| | Django's transaction.atomic(): It may not be as atomic as you think (charemza.name) |
| 1 point by michalc on Oct 10, 2020 | past |
|
| | JavaScript FIFO task queue with limited concurrency (charemza.name) |
| 1 point by michalc on May 17, 2020 | past |
|
| | I admit it: I like Python’s asyncio (charemza.name) |
| 2 points by michalc on May 8, 2020 | past |
|
| | Streaming: a skill gap? (charemza.name) |
| 137 points by michalc on Feb 2, 2020 | past | 36 comments |
|
| | Questions to ask yourself when considering a dependency (charemza.name) |
| 1 point by zdw on Jan 16, 2020 | past |
|
| | Python generators: Neatly manage stream processing pipelines for medium data (charemza.name) |
| 4 points by michalc on Jan 12, 2020 | past |
|
| | Mini HTTP Guide for Developers (charemza.name) |
| 113 points by michalc on Jan 4, 2020 | past | 4 comments |
|
| | The core S3 API is beautiful (charemza.name) |
| 4 points by michalc on Dec 31, 2019 | past | 2 comments |
|
| | Questions to ask yourself when considering a dependency (charemza.name) |
| 1 point by michalc on Dec 29, 2019 | past |
|
| | You might not need a class (charemza.name) |
| 1 point by michalc on May 9, 2019 | past |
|
| | I admit it: I like Python’s ternary operator (charemza.name) |
| 34 points by michalc on March 9, 2019 | past | 19 comments |
|
| | Reducing risk of release day: Large changes do not have to fill you with fear (charemza.name) |
| 2 points by michalc on March 3, 2019 | past |
|
| | Python asyncio read/write lock (charemza.name) |
| 2 points by michalc on Nov 11, 2018 | past |
|
| | You might not need Boto 3 (charemza.name) |
| 1 point by michalc on Oct 30, 2018 | past |
|
| | Questions to ask yourself when handling exceptions (charemza.name) |
| 3 points by michalc on July 24, 2018 | past |
|
| | Arbitrary Mercator Projections (charemza.name) |
| 1 point by michalc on July 9, 2018 | past |
|
| | Structured data in environment variables (charemza.name) |
| 1 point by michalc on July 8, 2018 | past |
|
| | Programming design choices in the face of changing requirements (charemza.name) |
| 1 point by michalc on Feb 25, 2018 | past |
|
| | Type-simplicity: If you can't have type-safety, have the next best thing (charemza.name) |
| 2 points by michalc on Jan 4, 2018 | past |
|
| | Questions to ask yourself when writing tests (charemza.name) |
| 203 points by michalc on Jan 1, 2018 | past | 97 comments |
|
| | Long files are not the enemy (charemza.name) |
| 2 points by michalc on April 1, 2017 | past |
|
| | Non atomic deployments (charemza.name) |
| 2 points by michalc on Feb 7, 2017 | past |
|
| | Overriding methods is spaghetti in disguise (charemza.name) |
| 2 points by michalc on Jan 12, 2017 | past |
|
|
| More |
