Peter Naur's classic 1985 essay "Programming as Theory Building" argues that a program is not its source code. A program is a shared mental construct (he uses the word theory) that lives in the minds of the people who work on it. If you lose the people, you lose the program. The code is merely a written representation of the program, and it's lossy, so you can't reconstruct
I had a bit of trouble trying to configure permissions to upload files from my Google Compute Engine instance to my Google Cloud Storage bucket. The process isn't as intuitive as you think. There are a few permissions issues that need to be configured before this can happen. Here are the steps I took to get things working.
Let's say you want to upload yourfile.txt
to a GCS bucket from your virtual machine.
You can use the gsutil
command line tool that comes installed on all GCE instances.
If you've never used the gcloud
or gsutil
command line tools on this machine before, you will need to initialize them with a service account.
Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.
My 3 developers team has just developed React.js application with 7668
lines of CSS (and just 2 !important
).
During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.
Here are main principles we use to write CSS for modern (IE11+) browsers:
- SUIT CSS naming conventions + SUIT CSS design principles;
- PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
- Flexbox is awesome. No need for grid framework;
- Normalize.css, base styles and variables are solid foundation for all components;
Implement a help
field on your project's package.json
listing all the scripts you want to display information about. Just make sure to use the same keys.
$ npm run help -s
> [email protected] help /Users/gordon-freeman/dev/project-sample
print("UPDATE AUG 2023: this script is beyond old and broken") | |
print("You may find interesting and more up to date resources in the comments of the gist") | |
exit() | |
from slacker import Slacker | |
import json | |
import argparse | |
import os | |
# This script finds all channels, private channels and direct messages |
# This monkey patches the PostgreSQL adapter to use asynchronous | |
# communication when doing its "SELECT 1" check for is-connection-active. | |
# One symptom of this problem is stalled processing queues in Sidekiq. | |
# See also: | |
# | |
# https://github.com/rails/rails/issues/12867 | |
# | |
# At the time of writing we have seen indefinite blocking down in the C | |
# library's "poll()" method due to the out-of-box Rails code using blocking | |
# I/O, in multithreaded environments - one thread gets stuck in the I/O and |
http://www.conadev.com/fa190814.php | |
Assitido em 19/08/2014 | |
Destaques sobre o relato de como as coisas funcionam na Codeminer: | |
- O principal mérito dado ao uso de escritório físico é juntar juniors e seniors em um mesmo ambiente; | |
- Usam slack para comunicação unificada; | |
- Escritórios e equipes não tem gerentes; |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
git branch -m old_branch new_branch # Rename branch locally | |
git push origin :old_branch # Delete the old branch | |
git push --set-upstream origin new_branch # Push the new branch, set local branch to track the new remote |