These are issues by the City of Cape Town which might cause service disruptions to multiple residents
#!/usr/bin/env bash | |
set -x | |
black=$1 | |
input_file=$2 | |
start_line=$3 | |
end_line=$4 | |
# Read selected lines and write to tmpfile |
// Very special thanks to Noel Berry | |
// A lot of this is borrowed from https://gist.github.com/NoelFB/778d190e5d17f1b86ebf39325346fcc5 | |
using System.Collections.Generic; | |
using System; | |
using System.IO; | |
using System.IO.Compression; | |
using System.Text; | |
using System.Linq; | |
using Microsoft.Xna.Framework; |
using System; | |
using System.Collections.Generic; | |
using System.IO; | |
using System.IO.Compression; | |
using System.Text; | |
// File Format: | |
// https://github.com/aseprite/aseprite/blob/master/docs/ase-file-specs.md | |
// Note: I didn't test with with Indexed or Grayscale colors |
Uncle Bob, the well known author of Clean Code, is coming back to us with a new book called Clean Architecture which wants to take a larger view on how to create software.
Even if Clean Code is one of the major book around OOP and code design (mainly by presenting the SOLID principles), I was not totally impressed by the book.
Clean Architecture leaves me with the same feeling, even if it's pushing the development world to do better, has some good stories and present robust principles to build software.
The book is build around 34 chapters organised in chapters.
Bucket policy is an access policy available for you to grant anonymous permissions to your Minio resources. Bucket policy uses JSON-based access policy language.
This section presents a few examples of typical use cases for bucket policies. The policies use testbucket
strings in the resource value. To test these policies, you need to replace these strings with your bucket name. For more information please read Amazon S3 access policy language
The following example policy grants the s3:GetObject
permission to any public anonymous users. This permission allows anyone to read the object data under testbucket
, which is useful for when you have publicly readable assets. A typical example is a website assets stored in testbucket
.
Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.
This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would
Blog post: Ryan Huber - Distributed Security Alerting | |
https://medium.com/several-people-are-coding | |
Video: Zane Lackey - Building a Modern Security Organization | |
https://duo.com/blog/duo-tech-talk-building-a-modern-security-engineering-organization | |
Krebs on Security Blog | |
https://www.krebsonsecurity.com | |
Sony Breach |
I think we should have all our code in a monolithic repository.
I've detailed the big benefits to having one, addressed possible issues to having one, and mentioned a few risks to not moving to a monorepo below.
Golang package dependencies
- Single
vendor/
dir at the top level ofdeis/deis
- All internal packages use the same external dependencies