| name | govuk-style | |||||||
|---|---|---|---|---|---|---|---|---|
| description | Write and edit in GOV.UK / GDS house style — plain English, active voice, front-loaded content, sentence case, and no bold or italics for emphasis. Use when writing or editing reports, research write-ups, guidance, documentation, summaries, or any prose where clarity and accessibility matter. | |||||||
| user-invokable | true | |||||||
| args |
|
This is ECE advice on how to study and succeed in school. This is a long list (copied from my Reddit post on r/ece) of things I learned over 6 years as an ECE undergraduate and masters student. Some tips are pulled from other places on this sub and around Reddit. This list is not comprehensive, has typos, and is obviously biased by personal taste... so if you have something to add please do so!
I am currently an electrical engineer at a large aerospace company, and am finishing finished my master's in ECE. I am was a TA for an introductory circuits course and want to give the students some tips. These are things I wish I knew when I was at their stage.
I am on Twitter nowadays, hit me up if you are struggling and I'll try to help out!
If you do some of these, you'll be better off. It's not a laundry list of everything you should do, it's just a reference if you need some tips. H
| before 'deploy', 'deploy:good_luck' | |
| before 'deploy:migration', 'deploy:good_luck' | |
| task :good_luck, roles: :app, except: { no_release: true } do | |
| if Time.now.wday == 5 | |
| logger.debug('') | |
| logger.debug('┓┏┓┏┓┃') | |
| logger.debug('┛┗┛┗┛┃\○/') | |
| logger.debug('┓┏┓┏┓┃ / Friday') | |
| logger.debug('┛┗┛┗┛┃ノ)') |
- Chatham House Rule, so no attribution of ideas to people or companies
- bootstrapping environments (without object stores)
- service discovery
- removing spofs
| /* | |
| * Copyright (c) 2014 Scott Vokes <vokes.s@gmail.com> | |
| * | |
| * Permission to use, copy, modify, and/or distribute this software for any | |
| * purpose with or without fee is hereby granted, provided that the above | |
| * copyright notice and this permission notice appear in all copies. | |
| * | |
| * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES | |
| * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF | |
| * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR |
#Devops and Networking
Proposal: Native Docker Multi-Host Networking #8951 Proposal: Native Docker Multi-Host Networking #8951
DevOps Road Blocks DOES14 - John Willis - DevOps Road Blocks
Managing Open vSwitch across a large heterogenous fleet Managing Open vSwitch across a large heterogenous fleet - Rackspace Openstack Summit Paris
Hi there!
The docker cheat sheet has moved to a Github project under https://github.com/wsargent/docker-cheat-sheet.
Please click on the link above to go to the cheat sheet.
- Measure time spend on index, flush, refresh, merge, query, etc. (TD - done)
- Take hot threads snapshots under read+write, read-only, write-only (TD - done)
- Adjust refresh time to 10s (from 1s) and see how load changes (TD)
- Measure time of a rolling restart doing
disable_flushanddisable_recovery(TD) - Specify routing on query -- make it choose same node for each shard each time (MD)
- GC new generation size (TD)
- Warmers
- measure before/after of client query time with and without warmers (MD)
| input { | |
| syslog { | |
| type => "haproxy-access" | |
| port => 514 | |
| } | |
| } | |
| filter { | |
| grok { | |
| type => "haproxy-access" |