Like basically any rocket attack I assume happened in like 2006 and between completely different belligerents than whatever a post claims at this point
1,829 karma · joined December 13, 2021
Like basically any rocket attack I assume happened in like 2006 and between completely different belligerents than whatever a post claims at this point
Topological defect. The unpictured thing the contour lines are swirling around. It's influence is only felt by seeing the effects on higher dimensional space, but you can never see the ghost itself.
What I meant by this is, in my personal opinion, there were a bunch of half baked products they should have just not mentioned at reinvent because said products never really materialized or had significant usage oncerns for a long, long time after the announcement.
The pressure to announce more and more at reinvent while the quality of what was being announced dropped was the specific feeling I'm talking about.
Sorry kind of on a caffeine high and brain isn't working too well right now. I'm also reluctant to throw shade on the products/teams I'm thinking of because I didn't work on them and I don't want to give them any heat, but I'll say it was in the 2017-2019 era I felt it start to change.
I think it contrasts with the really cool launches like Lambda, Aurora, API Gateway, Sagemaker, etc that has just come out before then.
That said, .... Really glad I quit smoking anything after seeing the damage a vape did to those poor guys
SQS and Cloud watch were legit to, although cloud watch metrics are a bit aged and logs were really difficult to use until insihhts came into place
Also Glue, while it has some tenancy issues and rough edges, takes a bunch of work out of managing a datalake
Oh and Aurora + Aurora serverless weren't as flashy but from an ops perspective game changing at the time
Cloudformation is definitely showing it's age and I hate writing it compared to CDK, but it was also pretty game changing at the time. I don't know if it was the first infrastructure as code language, but it definitely kick-started the revolution.
It's been a struggle, and I really should have gotten diagnosed with ADHD decades ago rather than years ago. I regret those that I've hurt (especially those that I love) and the times I was my own barrier to success or happiness.
I'm lucky to have a wonderful partner and manager at this stage in my life, and I've put a bunch of work into myself. It's been slow, but more and more of it seems to be "sticky", and that's incredibly encouraging.
Overall, satisfied with my life, especially in context of the world at large or relative to those with a similar background (makes me realize in some ways I'm pretty darn lucky after all).
Still, I feel the need to earn it. I don't feel like I deserve the nice things I do have, and I have a lot of anxiety of it going away. Therapy is currently helping me guide that and allow me to focus on the parts I can control while giving me the serenity to accept that there are things inherently uncontrollable, or even influencable.
Only thing I'd have to say is: never give up trying to get better. You're stuck with yourself for your entire life, one way or another. You owe it to your future, present, and past self to get better, and you owe it to those rays of sunshine that are the people you love or have given kindness, also past present, and future. You can't change the past, so don't dwell on it. Just try to do what you reasonably can. You've survived this long, which shows you're capable of endurance and survival at minimum. Have faith you can keep that, and use that as a rock to build a better life and a better (at least, local) world upon.
Unions aren't like the bar association, it's not obligatory across the industry, or even the same company. Literally today Boeing is on strike in WA but not in South Carolina, exactly because only the WA employees are union.
I don't think teachers, cops, sanitation workers, or iron workers can realistically do their jobs at home
This looks interesting and relevant:
- https://github.com/projen/projen
- https://aws.amazon.com/blogs/devops/getting-started-with-pro...
Looks Amazon official. Okay, I'm hype, this will be fun to play with.
Also keep in mind Amazon is headquartered in Seattle, which is far from a cheap area, and of the 5 submitters to levels.fyi for sde3 Seattle new hires in the last 6 months, the range is 250k-425k.
Take into account that an L6 who started from L4 normally has the scope and competence of a Staff engineer at Google, it makes sense to me.
If all you wanted was money, you could do even better by going into finance or OpenAI and work your life away until you can't anymore. It's just not sustainable for most people long term, no matter what the pay is, which itself is less than many contemporaries in the same "class".
It's basically panel 2 from this:
Beyond the initial publication of the doc, the peer review process is much more sane than trying to review a bunch of power point slides. Similarly, it's much much easier to refer to a well written document when it comes time to implement or reevaluate an idea than going over some power point slides and maybe an associated recording, to say nothing about searchability, discoverability, and maintainability of an actual written document vs PowerPoint slides.
Also, idle side speculation: I wonder how much (if any) one of the underappreciated early employees @ Amazon had a hand in proselytizing this, given she (MacKenzie) is an author.
There's definitely been some rot in AWS, which has been holding off the collapse in most other areas. Honestly it seems the more top down leadership, no matter who, gets their hands involved in thr sausage making process, thats when things start to go awry.
Engineering companies success because of their engineering culture. Amazon has some of the besr in class. Keep the accountability that many other top tier companies lack, but otherwise imo get out of the way and let the ICs do their job.
- 4 weeks (20 days) of PTO if you were there for 6 years or more, plus
- 6 "personal" days
- in Seattle at least, 3 sick days
Holidays were pretty bad (I don't think MLK jr day was a holiday until like 2021), but personally I'd rather be able to chose my own time off than have random enforced "rest days/development days" and enforced week long vacations when all the hotels and flights are full or pricey and traffic is terrible.
Come to think of it, some of my best work was done in the quiet times of Christmas/New Years when everyone else was gone and I was thus left without distractions. Lots of fun prototyping and project bootstrapping memories.
It's a heuristic, not a conviction. Generally I don't bother to listen to the TED talks anymore and I'm much more distrustful in my priors than "normal" for anyone I see giving one.
That said it's not like I'm going to dismiss someone with otherwise solid credentials out of hand just because they gave a TED talk, but it still lowers my trust.
Really depends on what you're trying to use the info for. I'm not a researcher so it's not like this affects my day job, and if I was I'd like to think I'd dive into the sources rather than ever just taking someone for their word. That's like the equivalent of copy pasting some code you found on discord into your production app.
Adding on thoughts:
One of my biggest gripes was that "make a good marketing opportunity at Re:Invent" seemed to become more important than "release beloved software that makes the lives of our customers easier" by the time I left (not that I was working on anything for reinvent in my final years there).
I will add that I learned a TON from AWS, and got to practice much of it too. It's the best boot camp one could ask for regarding general skill development imo (not particular frameworks etc but like, the theory and practice). There's also some things I miss like the weekly ops review and the general engineering culture, especially when it came to explicitly listing service limits, API specs, and cost up front in your design. Oh, and I honestly miss the docs culture. Quip wasn't as good as Google docs but the actual docs themselves and process of authoring them were SUPER valuable.
Coding wise, CDK was so much better than terraform (once we moved to CDK from lpt+cfn, which was way worse imo). Smithy and open API are neato too (@smithy externally everyone uses thrift it seems, but the overlap of functionality/use cases isn't identical).
Probably the biggest thing I miss was bones (kind of successor to octane), which is kind of like yeoman or create react app but would include so so much of the excellent internal tooling of ci/CD approval actions. I don't know of a real external equivalent, but would love to have one. If you ever see a Breland Miley or Ian Mosher apply to your company, HIRE THEM IMMEDIATELY. (There was another really solid guy on that team but their name escapes me at the moment, and here's hoping I got the spelling right)
Oh, also isengard is still easier to use than okta or AWS organizations to manage accounts imo.
(Come on you post a HW issue on hacker news, you know the peanut gallery is coming out in force ;-) )
Last time I did it I threw away my root install too because I figured it had been around long enough that either my drunken younger self messed up the install or otherwise something "dirtied up" the install.
I also figure it's nice to clean the slate just in case someone put a gnarly rootkit on my box.
Over the last two years I've migrated to fedora/Ubuntu and trying to do everything really secure, but I finally broke down and re enabled community a month or two ago. Just too much user space desktop quality of life stuff which only lives in community....
Out of curiosity, do you count community as official?
Copilot and the likes are legit for boilerplate, some test code, and posix/power shell scripting. Anything that's very common it's great.
Anything novel though and it suffers. Did AWS just release some new functionality and only like 4 people have touched it so far on GitHub? Are you getting source docs incomplete or spread out amongst multiple pages with some implicit/betwen-the-lines spec? Eh, good luck, you're probably better off just reading the docs yourself or guess and checking.
Same goes for versioning, sometimes it'll fall back into an older version of the system (ex Kafka with kraft vs zookeeper)
Personally, the best general use case of LLMs for me is focus. I know how to break down a task, but sometimes I have an issue staying focused on doing it and having a reasonably competent partner to rubber duck with is super useful. It helps that the chat log then becomes an easy artifact to more or less copy paste, and chatgpt doesn't do a terrible job reformatting either. Like for 90% of the stuff it's easier than using vim commands.
Btw anyone else seen that bear rummaging around? Any idea how to get rid of it?
I suppose if you make the refer nces fancy enough you wind up reinventing rst
It's fun and enlightening to go ham on any particular style/framework/philosophy, but actually living by dogma in prod gets kinda dangerous and imo is counter to the role of a senior+ engineer
https://en.m.wikipedia.org/wiki/Federal_Trade_Commission_v._....