761 karma · joined May 27, 2019
LinkedIn: https://www.linkedin.com/in/johnlmitchell/
- fleshed out modules: functools, itertools -- love them; also bisect, collections, decimal, math, random, and type aliases
- enhanced the dictionary and set types, used by 100% of programs
His talks are high-energy and very useful. I just found one on "Pro tips for writing Unit Tests" <3 -- https://www.youtube.com/watch?v=jSIsyMd2-RY
Pythonmorsels is a great subscribe.
Remote: yes, or hybrid or onsite
Willing to relocate: no
Technologies: DEV: Python, Django, Typescript, Postgres; DEVOPS: AWS/GCP, Ansible, CDK, Kubernetes/Docker, Pulumi, Terraform; CICD: GitHub Actions, CircleCI, ArgoCD
Résumé/CV: https://www.linkedin.com/in/johnlmitchell/
Email: johntellsall@proton.me
I'm a seasoned Senior/Staff Engineer with lots of DevOps and Development experience. Adept at high-level architecture, down to CLI and low-level languages and systems.
* Varied projects including ecommerce, healthcare, and API-driven
* Cloud Architecture and Observability
* DevEx / Velocity Expert
* Financial and Security: ISO-27001/SOC2, Sentinel, Guardrails
I'd love to chat -- please reach out!
Blog: https://dev.to/johntellsall
Youtube channel: https://www.youtube.com/channel/UC0PGaH-sVPGIdFUC88FgMmw
I've never used eval.
Make's use of Bash can lead to hairy quoting/escaping. I use Make as a "dumb high-level runner" and put any sort of intelligence, like conditionals or loops or networking, in lower-level scripts or programs.
Make is an orchestrator.
In college I wrote an assembler, interpreter, and simulator for an 8-bit chip, the 8048. Got a four-credit "A" :-D
Later I read the C code for a Scheme interpreter -- Scheme 9 in Empty Space -- highly recommended! I bought the book. https://t3x.org/s9book/index.html
Remote: yes
Willing to relocate: no
Technologies: DEV: Python, Django, Typescript, Postgres; DEVOPS: AWS/GCP, Ansible, CDK, Kubernetes/Docker, Pulumi, Terraform; CICD: GitHub Actions, CircleCI, ArgoCD
Résumé/CV: https://bit.ly/jta-resume-se
Email: johntellsall@proton.me
I'm a seasoned Senior/Staff Backend Developer with 20 years experience. In addition to substantial web skills I bring a lot of Infrastructure experience to the table. Adept at CLI and low-level languages and systems.
* Varied projects including ecommerce, healthcare, and API-driven
* Cloud Architecture and Observability
* DevEx / Velocity Expert
* Financial and Security: ISO-27001/SOC2, Sentinel, Guardrails
I'd love to chat -- please reach out!
Blog: https://dev.to/johntellsall
Youtube channel: https://www.youtube.com/channel/UC0PGaH-sVPGIdFUC88FgMmw
Build time, like other sorts of feedback loops is critical for team level success. This means the team should measure and review build time, and invest in it when needed. CI/CD doesn't magically fix itself.
Current database is a bit light: it didn't have "Science Vs", a popular podcast. Added.
For comparison, https://www.podchaser.com/ only has podcasts but it's more fleshed out.
Nothing to do with Zig. Just a nice debugging story.
I have 20+ YOE, aced a take-home technical, had good rapport with team lead... but they didn't move forward with hiring me.
Take care of yourself! Go outside! Get a hobby! Mental health is so important. Tomorrow morning I'm meeting my buddy to drink too much coffee and swap stories before coming home to work on my business card for next week's multi-day job conference. It's... a lot.
I have two niches: DevOps (build resources with code, facilitate the Feature Devs) and DevEx/Velocity Coach (drop in and do focused training). A tool to focus my pitch to the opportunity would be great!
Remote: yes, or hybrid Willing to relocate: no
Technologies: DevOps, Backend Web, Security
- Cloud Tech: AWS, Terraform, Kubernetes, Ansible, Lambda, GitHub Actions
- Dev Tech: Python, Django, Postgresql, Docker, Serverless, JavaScript
Résumé/CV: https://bit.ly/jta-resume
Email: johntellsall@proton.me
GitHub: https://github.com/johntellsall
YouTube channel: https://www.youtube.com/watch?v=zd7VlmClTDs
Seasoned Software/DevOps Engineer with 20 years experience. Delivered products to production in 10-person and Fortune-50 companies. Passionate about speed and quality (DevEx), using a product-minded, pragmatic approach to TDD.
Companies benefit from my unique combination of development, DevOps, and security skills. Past projects:
- "guardrails" event-driven security stack, for a bank
- built tools so devs work at higher level of abstraction
- ISO certification at fintech startup
- fullstack software including infra for ecommerce sites
- simplify and speed up CICD, increasing business-critical velocity
Teaching/Volunteer work: Current workshop is "Fast Development" on maximizing software impact and velocity -- contact me for a free preview! Gave dozens of talks at Socal Python, Girl Develop It, and other groups. Happy to mentor engineers at any phase of career.
Are you looking for a senior IC? Hire me!
[ Southern California: I'll be at the SCALE conference March 14-17 volunteering at the Python booth or wandering around. Come say hi! ]
Note the first season was not about new aliens per episode. It was all about atmosphere and character development and relationships.
For money/political reasons, Season 2 turned into monster-of-the-week.
And here's their work on the micro animation blog Dwitter: https://www.dwitter.net/u/KilledByAPixel
Youtube explanation: https://www.youtube.com/watch?v=HV7Dmo277Rs
Location: Los Angeles, CA, USA
Remote: yes, or hybrid
Willing to relocate: no
Technologies: DevOps, Backend Web, Security. Dev Tech: Python, Django, Postgresql, Docker, Serverless, JavaScript. Cloud Tech: AWS, Terraform, Kubernetes, Ansible; Lambda, GitHub Actions
Résumé/CV: https://bit.ly/jta-resume
Email: Find my email here: https://veilmail.io/e/49tXFe
GitHub: https://github.com/johntellsall
YouTube channel: https://www.youtube.com/watch?v=zd7VlmClTDs
Seasoned Software/DevOps Engineer with 20 years experience. Delivered products to production in 10-person and Fortune-50 companies. Passionate about speed and quality (DevEx), using a product-minded, pragmatic approach to TDD.Companies benefit from my unique combination of development, DevOps, and security skills. Past projects:
- "guardrails" event-driven security stack, for a bank
- built tools so devs work at higher level of abstraction
- ISO certification at fintech startup
- fullstack software including infra for ecommerce sites
- simplify and speed up CICD, increasing business-critical velocity
Teaching/Volunteer work: Current workshop is "Fast Development" on maximizing software impact and velocity -- contact me for a free preview! Gave dozens of talks at Socal Python, Girl Develop It, and other groups. Happy to mentor engineers at any phase of career.
Are you looking for a senior IC to mentor your team and deliver results? Hire me!
- every system has a bottleneck
- fixing things _after_ the bottleneck will have no effect
- fixing things _before_ the bottleneck will make the bottleneck worse
Caches can be horrible:
- adds complexity of code and architecture
- adds run-time complexity, with new failure modes
- adds semi-random delays
- see also: Buffer Bloat
There's a reason it's one of the Two Hard Problems in Computer Science! https://martinfowler.com/bliki/TwoHardThings.html
Logically, we want a Plan to move towards our Goal. As Engineers we often suffer from Analysis Paralysis: lots of paths to the goal with no clear winner. We also slow down from Impostor Syndrome: surely a smarter/more talented person knows the one true Plan forward to the goal.
> I make a plan, then do the plan, then learn from my efforts by reviewing my progress. I do this every day of the year, going on half a decade now. [At many time scales: three hour cycles going up to three-month cycles.]
I believe OP would agree that the Plan should be low quality, at least at the beginning. This encourages forward movement, and learning, vs just planning in circles and without using real-world data.
Source: writing a book on Feedback Loops
https://witandwisdomofanengineer.blogspot.com/2010/07/engine...
TLDR: McDonald's customers buy milkshakes. Marketing people ask customers how they can make milkshakes better... to sell more. They make changes with zero change in sales.
A researcher asks people who buy milkshakes: what is the job that the shake fills for you? Why do you "hire" the shake?
Answer: early morning commuters want something to eat while driving to work. A shake isn't a good breakfast, but it's quick and easy to buy then consume while driving to work. Satisfying.
The point is making a shake "better" won't help anyone! "How can we make it better" is the wrong question!
This is a business challenge because it's hard for the business to see. Devs are working hard, they say they're making progress, but it's slow. The business looks anxious about time/money but they can't see the reasons things take so much time-effort.
Similarly, tech leads fail to, err, lead. They should clearly draw a line between business value and the team's output. Then they should review this connection again and again, e.g. monthly. Devs aren't stupid: if they repeatedly see the same goal and the same road towards the goal, they'll move towards it. The risk is that devs understand _more or less_ the goal and direction, and _more or less_ deliver code that is an approximation of the business goal. Sometimes this is fine, sometimes it needs rework, and occasionally it's a huge waste of time and energy. Code obsolete before it's even completed.
> “If you cannot do great things, do small things a great number of times”.
People want to "plan" themselves into being Great. So they go into a spiral of "I'm not good enough" and don't actually complete anything. They don't produce anything, no one sees their work, so it's much harder to improve.
In practice, if we produce a lot of stuff, and pay attention, the quality will increase over time. We'll become Great according to the article...
... I'd call it "Good Enough". Producing and analyzing and getting better takes time, energy, and focus. It's not fun. Once our result is Good Enough we move on and focus on another thing we want to produce.
Source: writing a book on (Developer) Feedback Loops