A life cycle of a software developer

A life cycle of a software developer

·

2 min read

Egg: He's in the civil engineering class. His lecturer is talking about Fortran90. He has to do a retake;

program hello
  ! This is a comment line; it is ignored by the compiler
  print *, 'Hello, World!'
end program hello

Lava: He's back from the concrete factory. Sees an ad for a job where they teach how to code. Applies because he used Python in that retake he had. He doesn't go through;

print("Hello, World!")

Pupa: He sees an ad by the same people for free online courses. He applies, gets a Python refresher and learns HTML;

<!DOCTYPE html>
<html>
    <head>
        <title>Example</title>
    </head>
    <body>
        <p>This is an example of a simple HTML page with one paragraph.</p>
    </body>
</html>

Moth: Something clicked and he now sees the Languages for what they are, wings to an end. He gets in and writes React;

ReactDOM.render(
  <h1>Hello, world!</h1>,
  document.getElementById('root')
);

Death|Rebirth: That shadow of cold, of nothing, is ever present. He needs to change and so he tries ML

# NOTE: python itertools and collections are spells, abstracting away the labour needed to achieve somethins
# NOTE: this data is quite large. ah. pandas. is there a title for this? data engineer...
# NOTE: 4 revisits and I'm finally here, knock knock knockin' on heaven's door

🚪

image.png

Photo by Anne Lambeck on Unsplash

Â