- Python 3.7
- Pipenv (or plain pip)
- Docker
Create a csv file located in the same place of the gist, the csv should follow a format like this one.
Create a csv file located in the same place of the gist, the csv should follow a format like this one.
| import asyncio | |
| import csv | |
| import logging | |
| import os | |
| import aiohttp | |
| MEMORY_COMMAND = 'head -n 1 /proc/meminfo | awk \'{print $2}\'' | |
| PROCESS_INFORMATION = 'ps -o pid,uid,%mem,command ax' | |
| SSH_COMMAND_TO_RETRIEVE = "ssh " \ |
OSS it's one of the most important assets for innovation inside the software industry; many projets are the foundations of huge enterprises, banks, startups and freelancers accross the world. For our organization it's a huge value to bring back knowledge to the community; sharing with them part of our implementations and solutions making them open source.
We've considered a few questions to be considered before making an open source project.
Using the current resources (Linkedin Learning), We've choosen some courses for getting started and ready to start working with k8s and some useful resources about Microservices and Cloud Native Ecosystem.
These are the recommended courses:
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real
This list is meant to be a both a quick guide and reference for further research into these topics. It's basically a summary of that comp sci course you never took or forgot about, so there's no way it can cover everything in depth. It also will be available as a gist on Github for everyone to edit and add to.
| // See http://en.wikipedia.org/wiki/Kruskal's_algorithm | |
| // and http://programmingpraxis.com/2010/04/06/minimum-spanning-tree-kruskals-algorithm/ | |
| var _ = require('underscore'); | |
| var nodes = ["A", "B", "C", "D", "E", "F", "G"]; | |
| var edges = [ | |
| ["A", "B", 7], ["A", "D", 5], |
| /** | |
| * Created by alberto on 1/24/15. | |
| */ | |
| /*! | |
| * Snowball JavaScript Library v0.3 | |
| * http://code.google.com/p/urim/ | |
| * http://snowball.tartarus.org/ | |
| * | |
| * Copyright 2010, Oleg Mazko | |
| * http://www.mozilla.org/MPL/ |
| /* | |
| Using Groovy to read email form GMail. | |
| Just for development purposes, GMail will not allow in first time the login, so I enabled the option to log from non secure apps | |
| SSL it's necessary | |
| Another good tutorial coudl be find here using SSL: | |
| http://agileice.blogspot.mx/2008/10/using-groovy-to-connect-to-gmail.html |
| def xmlContent = new File("your-sat-xml-file.xml").getText() | |
| def xml = new XmlSlurper().parseText(xmlContent).declareNamespace( | |
| cfdi:"http://www.sat.gob.mx/cfd/3", | |
| xsi:"http://www.w3.org/2001/XMLSchema-instance")}} | |
| //Getting xml information. | |
| //this will work for other xml files with other namespaces if needed | |
| //@ for reading xml attributes, if there's no attribute just . operator will be fine | |
| println xml.'cfdi:Receptor'.@rfc |