(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.
| /* @import url(http://fonts.googleapis.com/earlyaccess/notosansmyanmar.css); */ | |
| /* @import url(http://fonts.googleapis.com/earlyaccess/padauk.css); */ | |
| @counter-style hyphen { | |
| system: cyclic; | |
| symbols: "-"; | |
| suffix: " "; | |
| } | |
| @counter-style myanmar-parens { |
| <?php | |
| # Cron job command for Laravel 4.2 | |
| # Inspired by Laravel 5's new upcoming scheduler (https://laravel-news.com/2014/11/laravel-5-scheduler) | |
| # | |
| # Author: Soren Schwert (GitHub: sisou) | |
| # | |
| # Requirements: | |
| # ============= | |
| # PHP 5.4 |
| failed (104: Connection reset by peer) while reading response header from upstream, client: | |
| If you are getting the above error in nginx logs running in from of upstream servers you may consider doing this as it worked for me: | |
| check the ulimit on the machines and ensure it is high enough to handle the load coming in. 'ulimit' on linux, I am told determines the maximum number of open files the kernel can handle. | |
| The way I did that? | |
| modifying limits: for open files: | |
| -------------------------------- | |
| add or change this line in /etc/systcl.conf | |
| fs.file-max = <limit-number> |
| # ... | |
| server { | |
| listen 80; | |
| server_name localhost; | |
| location / { | |
| root html; | |
| index index.html index.htm; | |
| } |
(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.
| <?php | |
| use Illuminate\Console\Command; | |
| use Illuminate\Filesystem\Filesystem; | |
| class ViewsCommand extends Command { | |
| /** | |
| * The console command name. | |
| * | |
| * @var string |
A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.
I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.
I'd love comments and suggestions about any of these.
I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.
I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".
| package main | |
| import ( | |
| "fmt" | |
| "image" | |
| "os" | |
| _ "image/jpeg" | |
| _ "image/png" | |
| ) |