Nicolás Silva nicolascine

Nuevo: SCLTransit

Ignacio Hermosilla implementó un servicio web de acceso público usando los feeds GTFS de Transantiago y los puntos de acceso oficiales que normalmente requieren acuerdos con el DTPM, para que tú no tengas que hacerlo.

Está toda la información de Transantiago que puedas necesitar, con formatos de alta calidad y sin trámites. Estas APIs son las que ahora alimentan a Cromi.

Revisa los endpoints y la documentación en scltrans.it

APIs internas de Transantiago (no recomendadas)

Transantiago implementó estas APIs para uso interno, por lo que no hay ninguna garantía sobre su funcionalidad, mantenimiento o futura existencia. Úsalas bajo tu propio riesgo. (Probablemente no es aconsejable que las uses para nada crítico.)

How to calculate your hourly rate as a freelancer?

Many people struggle with this question. Some just try to make as much as a full-time employee makes (and ignore that they won't be able to bill as many days). Others follow tips on startup related websites that suggest to ask for 20% to 50% more than an salary would yield (and ignore the additional risk and expenses they have).

Below you will find some numbers to help you calculate how high your hourly or daily rate should be.

Your yearly income should be higher than an average salary

You take more risk than full time employees, phases without income are likely

Concurrency in JavaScript

Javascript is a programming language with a peculiar twist. Its event driven model means that nothing blocks and everything runs concurrently. This is not to be confused with the same type of concurrency as running in parallel on multiple cores. Javascript is single threaded so each program runs on a single core yet every line of code executes without waiting for anything to return. This sounds weird but it's true. If you want to have any type of sequential ordering you can use events, callbacks, or as of late promises.

Python3 Virtualenv Setup

Requirements

Python 3
Pip 3

$ brew install python3

Vagrant error :NFS is reporting that your exports file is invalid

==> default: Exporting NFS shared folders...
NFS is reporting that your exports file is invalid. Vagrant does
this check before making any changes to the file. Please correct
the issues below and execute "vagrant reload":

exports:2: path contains non-directory or non-existent components: /Users/<username>/path/to/vagrant
exports:2: no usable directories in export entry
exports:2: using fallback (marked offline): /

	@mixin for-size($range) {
	$phone-upper-boundary: 600px;
	$tablet-portrait-upper-boundary: 900px;
	$tablet-landscape-upper-boundary: 1200px;
	$desktop-upper-boundary: 1800px;

	@if $range == phone-only {
	@media (max-width: #{$phone-upper-boundary - 1}) { @content; }
	} @else if $range == tablet-portrait-up {
	@media (min-width: $phone-upper-boundary) { @content; }

	FROM python:3.5.2

	RUN apt-get update \
	&& apt-get install -y gettext curl sudo \
	&& curl -sL https://deb.nodesource.com/setup_6.x \| sudo -E bash - \
	&& apt-get install -y nodejs \
	&& apt-get install -y libpng-dev libtiff5-dev libjpeg62-turbo-dev zlib1g-dev \
	libfreetype6-dev liblcms2-dev libwebp-dev tcl8.6-dev tk8.6-dev python-tk \
	libopenjpeg-dev pngquant libmagickwand-dev imagemagick \
	&& apt-get autoremove -y --purge \

	import { Component, Injectable, Directive, TemplateRef } from '@angular/core';
	import { NgbModal, NgbModalRef, NgbModalOptions } from '@ng-bootstrap/ng-bootstrap';

	/**
	* Options passed when opening a confirmation modal
	*/
	interface ConfirmOptions {
	/**
	* The title of the confirmation modal
	*/

	import {Injectable,Inject,ElementRef, Renderer} from '@angular/core';
	//import { DOCUMENT } from '@angular/platform/common_dom';
	import {DOCUMENT} from '@angular/platform-browser';

	@Injectable()
	export class SeoService {
	private _r: Renderer;
	private _el: ElementRef;
	private _document: any;
	/**

	# Sample Nginx config with sane caching settings for modern web development
	#
	# Motivation:
	# Modern web development often happens with developer tools open, e. g. the Chrome Dev Tools.
	# These tools automatically deactivate all sorts of caching for you, so you always have a fresh
	# and juicy version of your assets available.
	# At some point, however, you want to show your work to testers, your boss or your client.
	# After you implemented and deployed their feedback, they reload the testing page – and report
	# the exact same issues as before! What happened? Of course, they did not have developer tools
	# open, and of course, they did not empty their caches before navigating to your site.