What is #Microsoft actually good at? Going thru their key products, it is clear they don't create new paradigms, they make often buggy implementations of ideas from other people: #BASIC#MSDOS#Windows#Word#Excel#browser#Bing#Cloud#dotnet. One thing they are clearly good is building a #monopoly. So it seems what they are good at is seeing good ideas, "embrace and extend" to control it, then building monopoly profiteering.
Just started to learn C# this weekend. It was something recommended to me by a colleague, as a part of my development plan. I've dabbled in Python, but hoping I finally stick with it and start building stuff.
@KirillOsenkov Yes, it's still technically a Task but having to methodically change signatures from int? to Task<int?> feels tedious, especially with the great tooling options available to #dotnet devs. Especially since most folks will be adding the async keyword anyways. It's two changes when one would suffice.
So much for thru-hiking the #AppalachianTrail this year. I've been on a downward spiral since leaving my job in September 2022. I was professionally burnt out. I didn't want to keep building #backend#dotnet APIs. I also read through the latest #IPCC reports, which paint a bleak picture of our collective future. In short, I was miserable.
I quit my meds cold turkey -- #Lexapro and #Metformin -- and started downsizing my life. I got a job as an #Amazon warehouse worker, but left after a few weeks as the holidays ramped up while the pay stayed the same. #DoorDash became my only source of income.
I also threw myself into political activism, working with the #PartyForSocialismAndLiberation to fight off an Austin Energy rate hike that punished the poor with big rate hikes while giving cuts to the wealthy. We won a few minor concessions, but the disparities were still there.
Afterwards, I sold or donated most of my possessions to try to pay my bills. I even sold my car eventually once DoorDash stopped paying well. I took the remaining cash and geared myself for a thru-hike of the AT, convinced that I could walk myself to a better place physically and mentally.
Physically, by mid April of 2023, I certainly felt ready. I was doing 15-mile days in #atx#austin. But mentally, I was still struggling with suicidal ideation every few days. My mom had booked flights and a hotel to see me off at #AmicalolaFalls, and the week before, she picked me up and brought me to her place.
It took all of 48 hours for her to chip away what little facade of confidence I had left. I broke down crying, saying I was at least passively suicidal, had crazy #anxiety and #depression, my blood sugar was all kinds of fucked up on account of not taking my #diabetes meds, and, above all, I was not (mentally, at least) ready to spend months in the mountains, alone.
So now I'm here, in Benbrook TX, back on meds, back at home (again (at 33)), going to #therapy, going bankrupt, and trying to figure out how to survive in #LateStageCapitalism and not end it all.
At this point I'm out of the nosedive at least. But I've got a bunch of climbing to do in the meantime.
#dotnet apps, when starting up, should output the process Id into the console output. It would make it easier to find them and attach to process that way.
✅ https://Tusk.Ninja now accepts many image file formats if you want to upload a background image for its 'Text To Image' feature.
👉 With https://Tusk.Ninja's 'Txt2Img' , a #dotNET#Blazor WASM web application, you can create images with text (duh 😉) online and post them instantly as 'Toots' to #Mastodon.
Hear me out:
Imagine you work on software projects that are often measured in years. Imagine that your developers rarely get to re-visit apps once they’ve launched. Imagine your large fleet of apps have all been written in #DotNet Framework. Now, imagine you are evaluating the possibility of moving from framework to .net7 or the upcoming 8 and your managers ask about support. 7? 18 months from release so support ends 1 year from now. 8? 3 years. Framework 4.x? For the foreseeable future. 1/2
Your managers response:
If we start a project today & it takes a year to finish - if we go #dotnet 7 we’d launch without support, if the timing somehow worked out perfectly & we start on dotnet 8 launch day we’d launch w/just 2 yrs of support but if we stick with framework (which we already know & already have to support) we get support for the foreseeable future? Support alone seems like a deciding factor to stick with what we already do.
I can’t honestly blame this “imaginary” manager. 2/2