0x202020

I’ve got an esports side project that was starting to get some interest within the community and generate non-trivial MRR (~4k mo). I have a closed alpha that a few teams in the league were using, and I was talking at some level to basically everyone that could be in the market for the current version of the problem. I was looking into getting a business/sales partner in order to have more success on the business side of getting the other organizations I was in talks with, as I am normally just a lead dev with no business interaction. Then the league, along with everything else, got delayed and quarantines started. Within 3ish days all of the professional teams, academy teams and two other organizations are interested in my “alpha” software. So now my “side project” as of April 1st has ~10x’d its MRR (~40k).

As of now I am getting some business stuff ironed out and only making bug fixes/small updates while I get a better feeling of what type of workload difference the growth is making

These reviews look great for the 35/45w TDP chips. I can’t wait to see what the 15w (Ryzen 7 4800u) chips that would go in an XPS13 look like when they are released

I have been on the saving end of some of these AWS mistakes (billing/usage alerts are important people), but alerts aren't always enough to keep them from happening completely if they are fast

- Not stopping AWS Glue with an insane amount of DPUs attached when not using it. Quote "I don't know I just attached as many as possible so it would go faster when I needed".

- Bad queueing of jobs that got deployed to production before the end of month reports came out. Ticket quote "sometimes jobs freeze and stall, can kick up 2 retry instances then fails", not a big problem in the middle of the month when there was only a job once a week. End of the month comes along and 100+ users auto upload data to be processed, spinning up 100+ c5.12xlarge instances which should finish in ~2 mins but hang overnight and spin up 2 retry instances each

- Bad queueing of data transfer (I am sensing a queueing problem) that led to high db usage so autoscaling r5.24xlarge (one big db for everything) to the limit of 40 instances

I was really appreciative of the way the first company I worked for handled my departure. Things were changing at the company so I was looking to leave anyway but then they decided to change their structure and I was given a few options in person (lived ~2000 miles from main office) all of which were mutually beneficial from my point of view.

A) stay on and help integrate an external team for up to 16 weeks (reduced hours, freedom to interview and apply elsewhere) B) stay on and wrap up the current sprint and tidy up some documentation for up to 8 weeks C) finish out the week and receive 6 weeks separation pay. All options also allowed me to keep insurance until I found a new position as well as keep my company provided tech. It really made me appreciate the people at the company overall, minus the person who was making the changes (which has since been canned and some of the engineering efforts at the company have stalled which is sad)

I managed a few HP C7000 blade systems once in an inadequate environment. They have jet like fans and at the time a firmware bug that meant the fans had two levels: 79% and 100%. Compared to after the firmware was fixed it stayed around 30% at full load and was bearable at least

I saw this in a company I worked at previously. When I joined they had just moved their headquarters from the West Coast to the Midwest and gave employees the option to WFH or freedom to come into office still at new location. Within a year it was a pretty even split on A) staying where they were and working remote B) moving to be in the suburbs around the new location C) moving further out from the city but staying on the West Coast D) leaving the company

I don’t mind it, but my SO could never get used to it. We may be revisiting them soon though, thanks

I wish my household had normal TP usage. My fiancée and I both have Crohn’s disease, we probably average a bit more than a roll per day for just the two of us. On top of this we both take immunosuppressants, so we are at very high risk right now. We bought an industrial size pack from Sams Club when things started to get bad, but now we are on “don’t think about leaving the house any more than taking the dog out” levels on advice from our doctors, and that pack is depleting more quickly than I see this dissipating. We have a friend that works at Walmart back home and he is going to see if he can purchase some for us then ship ~1000mi as no one else obviously has any for shipping

To me it seems to be more so that Apple designs for Intels listed TDP and that’s it. The CPUs in the MBA are 9/10w and that is what it can handle sustained and staying slightly above base clock so not technically thermal throttling. Most of the time iirc Intel doesn’t list per core boost only the highest possible boost.

So for example the CPU is rated at 1.1ghz base and up to 3.5ghz boost. In the thermal throttling video we see it hold steady at ~10w and ~1.5ghz sustained. As far as Intel/Apple is concerned this isn’t thermal throttling because it is still higher than the base clock. Previously they would list all core boost clock and I think if it fell below that it would technically be thermal throttling

It seems to me that cooling is the ball that has been dropped on the new MBA. I haven’t seen one opened up yet but the heatsink design from last time (2018/2019) didn’t use a heat pipe over the CPU, it just kinda forced air to be drawn over it.

From this video: https://youtu.be/hB1aP2OnUJA we can see it quickly gets to 100c and stays there despite ramping the fan up. So while a quad core that can turbo up to 3.5/3.8ghz sounds awesome, for heavy sustained performance it looks like it’s definitely going to be clocking down to 1.5ghz or so.

This isn’t a surprise to me but I think some people just see 3.5/3.8 quad core and think this is going to be right on the heels of the MBP 13