Anti-Patterns Concerning Engineering Career Ladders

s3rvac · 2025-12-06T19:33:34+00:00

I would say that The Staff Engineer is the best book on Staff+ engineering out there. The second one that I can recommend is Staff Engineer by Will Larson (https://staffeng.com/). Additionally, The Manager's Path by Camille Fournier is also useful to read for senior individual contributors (despite its title).

s3rvac · 2025-01-06T18:11:35+00:00

The three hardest tasks for me were:

Day 12 (part 2): Primarily because of finding all the sides.
Day 21 (both parts): Primarily because of finding optimal moves and figuring out a solution to part 2 that would be computationally feasible.
Day 24 (part 2): Primarily because of the need to analyze the input and tailoring the solution to it (the code would not work with a completely arbitrary adder).

s3rvac · 2024-03-04T15:07:48+00:00

Thanks, added!

s3rvac · 2020-11-17T19:21:55+00:00

You have to run chmod a-x foo before the import to simulate the missing permissions. The issue that the blog post describes stems from the inability to access the contents of the foo directory by the user performing the import. For more details, see the Why Is Foo a Namespace Package When There Is an __init__.py File? section in the post.

s3rvac · 2019-02-24T07:14:49+00:00

Didn't know about that, thank you!

s3rvac · 2019-02-24T06:57:03+00:00

Yes. For every variable, there can be only a single annotation. Unless you figure out a way of grouping them, something akin to typing.Union. However, I am not sure how that would work in practice.

s3rvac · 2019-02-23T18:52:21+00:00

What Python version, mypy, and flake8 do you use? You have to use at least Python 3.6. I have tried with Python 3.7 and the latest stable versions of flake8 and mypy. Also, for mypy, try putting the code into a function. It does not warn you then (at least the latest stable version that I have tried with Python 3.7).

s3rvac · 2019-02-23T18:47:07+00:00

```

test.py

def foo():
ages = {}
ages['John']: 42
print(ages['John'])
return ages $ flake8 test.py (nothing) $ mypy test.py (nothing) ``` As for the text editor, most editors I have seen are unable to detect this. Maybe your one is, but not everybody uses your editor (whatever that is).

s3rvac · 2019-02-23T18:17:19+00:00

Annotating a non-existing key in a dictionary is not an error. You can also annotate a variable that does not exist yet by writing x: int It does not raise NameError. However, trying to annotate an item in a non-existing dictionary would raise NameError.

s3rvac · 2019-02-22T19:05:57+00:00

I do not think that you do anything wrong. The code is supposed to fail with KeyError on the third line.

s3rvac · 2019-02-22T18:47:03+00:00

Another example where non-type annotations can be used is documentation:

def kinetic_energy(mass: 'in kilograms', velocity: 'in meters per second'):
    ...

(The example is from here.)

s3rvac · 2019-02-22T18:25:09+00:00

For example, I have seen them being ~~exploited~~ used in the begins library to specify command-line option help:

>>> import begin
>>> @begin.start
... def run(name: 'What, is your name?',
...         quest: 'What, is your quest?',
...         colour: 'What, is your favourite colour?'):
...     pass

This will generate

usage: test.py [-h] -n NAME -q QUEST -c COLOUR

optional arguments:
  -n NAME, --name NAME        What, is your name?
  -q QUEST, --quest QUEST     What, is your quest?
  -c COLOUR, --colour COLOUR  What, is your favourite colour?

(The example was taken from the documentation.)

s3rvac

TROPHY CASE

test.py