# Work: about me

## General truths

* [I keep (re)learning this](https://twitter.com/tottinge/status/1329066180733251585)
* [Reflections After 15 Years of Working as a Software Developer](https://medium.com/better-programming/reflections-after-15-years-working-as-a-software-developer-cabf610f51a0)
* [A few rules](https://www.collaborativefund.com/blog/a-few-rules/)
* [68 Percent of Employees Are Disengaged, But There Is a Scientifically Proven Way to Boost Engagement](https://www.inc.com/sonia-thompson/68-percent-of-employees-are-disengaged-but-there-i.html)

## Bias

* [If You’re So Successful, Why Are You Still Working 70 Hours a Week?](https://hbr.org/2018/02/if-youre-so-successful-why-are-you-still-working-70-hours-a-week)
* [I could build this during the weekend](https://world.hey.com/joaoqalves/i-could-build-this-during-the-weekend-aa093c5e)
* [Code-wise, cloud-foolish](https://newsletter.goodtechthings.com/p/code-wise-cloud-foolish)

## Perfomance

* [Welcome to Your 1:1s Repo](https://github.com/sophshep/one-on-one)
* [Becoming a High-Performance Software Engineer](https://medium.com/riskified-technology/becoming-a-high-performance-software-engineer-895ec6949782)

## Growing

* [Career Ladders](https://career-ladders.dev/engineering/)
* [Scaling Yourself • Scott Hanselman • GOTO 2012 (YouTube)](https://www.youtube.com/watch?v=FS1mnISoG7U\&ab_channel=GOTOConferences)
* [Early work - Paul Gaham](http://paulgraham.com/early.html)
* [How to achieve career growth: opportunities, skills & sponsors](https://yenkel.dev/posts/how-to-achieve-career-growth-opportunities-skills-sponsors)
* [Career advice for people with bad luck](https://chiefofstuff.substack.com/p/career-advice-for-people-with-bad)
* [Choosing the management track](https://blog.danielna.com/choosing-the-management-track/)
* [Short Fat Engineers Are Undervalued](https://nested.substack.com/p/short-fat-engineers-are-undervalued)
* [Software Engineering Leadership is not (Only) About Coding Well](https://gadon.medium.com/software-engineering-leadership-is-not-only-about-coding-well-1d5d1e43029)
* [Developer progression as a function](https://www.siddharthsarda.com/p/developer-progression-as-a-function)
* [The engineer/manager pendulum](https://charity.wtf/2017/05/11/the-engineer-manager-pendulum/)
* [Ask HN: Managing career progression for those with no interest in progressing? | Hacker News](https://news.ycombinator.com/item?id=28287617)

## Daily work

* [Being visible](https://lethain.com/being-visible/)
* [Things to know about engineering levels](https://charity.wtf/2020/09/14/useful-things-to-know-about-engineering-levels/)
* [Your first day as a new engineering manager](https://pragmaticlead.com/posts/your-first-day-as-new-software-engineering-manager)
* [Maximixing developer effectiveness](https://martinfowler.com/articles/developer-effectiveness.html)
* [My Leadership Document — 2021 Edition](https://www.subbu.org/articles/2021/my-leadership-document-2021-edition/)
* [Decision Tree Analysis: How to Make Effective Decisions](https://fellow.app/blog/productivity/decision-tree-analysis-how-to-make-effective-decisions/)

## Health

* [Burnout in Software Development Demystified](https://thevaluable.dev/burnout-software-developer/)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://arielgerardorios.gitbook.io/personal-wiki/work_me.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.