• 0 Posts
  • 133 Comments
Joined 3 years ago
cake
Cake day: July 6th, 2023

help-circle

  • It was a college flavor of the month film that basically had 3 sections iirc. First was that Christianity is bullshit and how most religions have a bunch of common threads like the trinity, 3 day ressurection and how they lined up with astrology; Orion’s belt and the winter equinox. Second was that the government are trying to collect intelligence on you, and how you will happily start tracking yourself soon and how they are training you to want that. This one is true about cell phones to some extent but was written in a time when the original RAZR fliphone was a technological marvel. And the third was pretty much bullshit iirc and op thinks it was that 9/11 was a false flag operation. But zeitgeist likely explained what they are and how they are effective. Widely available on the seas, and it was part of the social conversation. Which was in person Or rly smol txt limit





  • I’ve been using copilot. Potential is there but getting a result is more art than science. I’ve found it helpful to document desired workflows in readmes and ask for unit tests then run unit tests until it works out.

    • use a premium model like sonnet and put it in agent mode
    • Ask it to review the project
    • ask it to review the ticket/requirements
    • ask it to research existing solutions and write a design document that meets the requirements with high certainty
    • Let it write the document and make sure it stays on task
    • review the output and send build errors back, roll forward or undo the code and re-submit
    • identify what works and reduce scope








  • US Sr SRE (devops) checking in: I would personally recommend the networking path. Caveat: A good engineer will know the background of both (curl, telnet, Iam, security groups, cidrs, domains)

    Devops was mostly automating the stuff in between the other teams; and most of that is working out of the box these days. Most repos already have their Jenkins and docker files. How much admin are you expecting on serverless? Most people are pivoting to app support (ticket queues) or supporting managed services (on call).

    As far as my day to day:

    • Troubleshooting incidents and walk ups
    • Answering pages (read restarting things)
    • Groovy Jenkins build pipelines
    • Cdk applications
    • Ruby configuration management
    • Parameter/secret management
    • Reading error messages for devs
    • Yaml/xml linting
    • Assisting in load testing
    • Changing settings to make the application more stable. Ex: db connections, memory
    • Cloud UI/clis

    Pros: I do a lot of different things, we get downtime because we need to respond to things immediately, I don’t have normal project/sprint planning. I have the keys to the kingdom. Higher pay than most other devs. I hack things together, I don’t need to design workflows.

    Cons: I am on call, I am the silliest clown (I get hardest problems), I need to understand a lot of moving pieces, sometimes when things break, there is a lot of pressure on you to find something hard. I regular have to Google “bash variable syntax” because I’m coding in 15 languages. Interviewing for jobs is impossible because no 2 positions are the same