1. The single most important thing is non-judgmental validation. Seek someone else’s thoughts and opinions without judging them. You don’t have to agree with everyone. The point is have the curiosity to understand what they mean, want, dream of, etc. 2. Suspend your ego. Focus on them. Don’t try to correct others. Don’t try to come up with something to show you can do better. You don’t want to create a fight-or-flight response. ...
This happened to me when doing a git pull from a coffee shop. ssh: connect to host github.com port 22: Operation timed out fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. The reason is because port 22 is blocked at the coffee shop wifi router. Turns out github allows https to do git operations. git config --local -e Change (or comment it out using #) ...
Forming, Storming, Norming, and Performing Ref: https://www.mindtools.com/pages/article/newLDR_86.htm
Finally, we are onto something useful now. This service creates image classifier without writing any code. That’s the right direction. Next step is to combine these classifiers to form a final classifier. https://www.seeme.ai/ https://www.zerotosingularity.com/blog/seeme-intro/
https://www.openshot.org/
I have python 3.7 installed but will need to run something with python 3.6. Here are the steps to do so. [code] brew unlink python brew install –ignore-dependencies https://raw.githubusercontent.com/Homebrew/homebrew-core/f2a764ef944b1080be64bd88dca9a1d80130c558/Formula/python.rb brew switch python 3.6.5 [/code] To switch it back to python 3.7 [code] brew switch python 3.7.0 [/code] Now with two versions installed, we can use virtualenv for projects. Notice that when you issue virtualenv –python=$(which python3) env, virtualenv may throw an error -bash: /usr/local/bin/virtualenv: /usr/local/opt/python/bin/python3.7: bad interpreter: No such file or directory. That’s because the virtualenv script has a shebang line referencing python 3.7. To fix that error, edit that file /usr/local/bin/virtualenv and change the version to 3.6. Then virtualenv will work fine. ...
When you just want to start fresh, you can always re-clone the repo. However, if you have local feature branches hanging around, then you may just want to clean up a particular branch. If you do a git status, you will see two sections. One is unstaged local changes (before commit), the other is local untracked files. For unstaged local changes (changes to files already checked in before) [code] # discard and save changes for possible re-use git stash ...
https://www.ted.com/talks/thomas_curran_our_dangerous_quest_to_perfect_ourselves#t-880530 We should strive to do best at school and work, so that we can achieve what our potential can reach. But that drive should not be limitless. Otherwise it would become the source of stress and internal looking down on oneself.
Who would have thought people’s names can be so complicated. https://shinesolutions.com/2018/01/08/falsehoods-programmers-believe-about-names-with-examples/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ People have exactly one canonical full name. People have exactly one full name which they go by. People have, at this point in time, exactly one canonical full name. People have, at this point in time, one full name which they go by. People have exactly N names, for any value of N. People’s names fit within a certain defined amount of space. People’s names do not change. People’s names change, but only at a certain enumerated set of events. People’s names are written in ASCII. People’s names are written in any single character set. People’s names are all mapped in Unicode code points. People’s names are case sensitive. People’s names are case insensitive. People’s names sometimes have prefixes or suffixes, but you can safely ignore those. People’s names do not contain numbers. People’s names are not written in ALL CAPS. People’s names are not written in all lower case letters. People’s names have an order to them. Picking any ordering scheme will automatically result in consistent ordering among all systems, as long as both use the same ordering scheme for the same name. People’s first names and last names are, by necessity, different. People have last names, family names, or anything else which is shared by folks recognized as their relatives. People’s names are globally unique. People’s names are almost globally unique. Alright alright but surely people’s names are diverse enough such that no million people share the same name. My system will never have to deal with names from China. Or Japan. Or Korea. Or Ireland, the United Kingdom, the United States, Spain, Mexico, Brazil, Peru, Russia, Sweden, Botswana, South Africa, Trinidad, Haiti, France, or the Klingon Empire, all of which have “weird” naming schemes in common use. That Klingon Empire thing was a joke, right? Confound your cultural relativism! People in my society, at least, agree on one commonly accepted standard for names. There exists an algorithm which transforms names and can be reversed losslessly. (Yes, yes, you can do it if your algorithm returns the input. You get a gold star.) I can safely assume that this dictionary of bad words contains no people’s names in it. People’s names are assigned at birth. OK, maybe not at birth, but at least pretty close to birth. Alright, alright, within a year or so of birth. Five years? You’re kidding me, right? Two different systems containing data about the same person will use the same name for that person. Two different data entry operators, given a person’s name, will by necessity enter bitwise equivalent strings on any single system, if the system is well-designed. People whose names break my system are weird outliers. They should have had solid, acceptable names, like 田中太郎. People have names.
Python API: https://github.com/googleads/googleads-python-lib/tree/master/examples/adwords/v201809/basic_operations Limits: https://developers.google.com/adwords/api/docs/appendix/limits