Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
| var e1start = e1.start.getTime(); | |
| var e1end = e1.end.getTime(); | |
| var e2start = e2.start.getTime(); | |
| var e2end = e2.end.getTime(); | |
| return (e1start > e2start && e1start < e2end || e2start > e1start && e2start < e1end); |
| $ git clone git@github.com:xxxxx/xxxx.git my-awesome-proj | |
| Cloning into 'my-awesome-proj'... | |
| ssh: connect to host github.com port 22: Connection timed out | |
| fatal: Could not read from remote repository. | |
| $ # This should also timeout | |
| $ ssh -T git@github.com | |
| ssh: connect to host github.com port 22: Connection timed out | |
| $ # but this might work |
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <title>4k website tester</title> | |
| <style> | |
| iframe:focus { | |
| outline: none; | |
| } | |
| iframe{ |
The only way I've succeeded so far is to employ SSH.
Assuming you are new to this like me, first I'd like to share with you that your Mac has a SSH config file in a .ssh directory. The config file is where you draw relations of your SSH keys to each GitHub (or Bitbucket) account, and all your SSH keys generated are saved into .ssh directory by default. You can navigate to it by running cd ~/.ssh within your terminal, open the config file with any editor, and it should look something like this:
Host * AddKeysToAgent yes
> UseKeyChain yes
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.
| <?php | |
| /* | |
| * Template Name: Home | |
| * Author & Copyright: VictorThemes | |
| * URL: https://victorthemes.com | |
| */ | |
| $brixey_id = ( isset( $post ) ) ? $post->ID : 0; | |
| $homepage_layout = get_post_meta( $brixey_id, 'homepage_layout_metaboxes', true ); | |
| if ($homepage_layout) { | |
| $home_layout = $homepage_layout['home_layout']; |
| import React from 'react'; | |
| import {storiesOf} from '@kadira/storybook'; | |
| import mockRedux from '<path-to>/js/mocks/redux'; | |
| import {Component} from '../'; | |
| const storeState = { | |
| list: ['foo', 'bar', 'baz'], | |
| someData: { | |
| foo: true, | |
| bar: false |
| import React, { FunctionComponent } from "react"; | |
| import { useSelector, useDispatch } from "react-redux"; | |
| import { selectCurrentSet, zoomImage } from "../dataLayer"; | |
| export const LegoSetImage: FunctionComponent = () => { | |
| const set = useSelector(selectCurrentSet); | |
| const dispatch = useDispatch() | |
| const zoomHandler = () => dispatch(zoomImage(set.set_img_url)) | |
| return ( | |
| <div className="legoSetImageContainer"> |