BC DOTNETHOTRELOAD
Saved by @m4rc0v0nh4g3n

So, there have been some things going on with .NET Hot Reload you may have heard of this week. It's an important issue. Others had it covered so I thought I'd hang back, but I've seen calls for more voices, so here's mine. 🧵 1/

 Some background: Microsoft merged a PR that removed Hot Reload from the .NET 6 despite it working, an unusual move, and said it was due to prioritization for Visual Studio. There has been lots of backlash, snark, and attempts to reinstate it as a result. 2/
First up: Lots of amazing people work at MS who care about OSS and the community. Folks I continue to look up to. MS contains multitudes, and I think we'd all do well to keep that in mind. I'm rooting for them. 3/
On to the opinion section-- This decision is troubling for a bunch of reasons: 1) The surprise factor 2) The transparent business interest driving it while pretending otherwise 3) the communication around it 4) The implication of those business moves for the larger community. 4/
1) Surprises: this code was working, in an RC release, and people were starting to use it. It had been touted as a great feature of .NET 6. Then it was just gone, "de-prioritized". But de-prioritized doesn't mean it has to be removed. Patterns exist for flagging it, etc. 5/
My initial reaction was "well, MS has to support it, so it's only fair that they get to prioritize or not what they take on". I sympathized with MS. But then I realized it was essentially feature complete and usable, and things seemed fishier from there. 6/
2) Business interest: then the Verge piece came out saying that an MS CVP is essentially clawing this stuff back from OSS and wants to make it a proprietary feature of Visual Studio for business reasons. Oof. That's really not OK. 7/
MS should be all about making profit. But I wanted to believe they'd learned a lesson about making profit at the expense of community and "bigger tent" strategy. This flies in the face that. Terrible business decision. Squanders goodwill. /8
3) Communication: Initially I thought this was poor communication about readiness. I was going to suggest longer explanations in PRs, a call for the community to help, an open discussion on the roadmap sooner. But since the Verge article, I'm realizing it wasn't about that. 9/
This truly does seem to be the "old" Microsoft rearing its head again, and trying to sneak it in under the radar with vague corporate speak around priorities. That's very disheartening. And it does make me mad. 10/
4) Implications: The reason it makes me mad is that I truly feel that, warts and all, we're working toward a better place in .NET OSS. And the MS turnaround has been such a big part of that. For a CVP to endanger that is just bananas reckless. 11/
With one move, this decision gravely undermines the idea that .NET works in the open, that it builds for community first, that it wants to be a player in an overall ecosystem vs "just get yours" mentality for its product teams. It is actually a big deal. 12/
So, how can MS fix this? 1) Revert that PR if it's being held back for any reason other than quality and/or completeness. 2) Re-affirm that this was a mistake, both of leadership vision and of communication. 3) Work toward a unified approach to OSS and ensure CVPs respect it. 13/
Since MS hasn't fixed it yet, it sounds like the community is going to. Forks are beginning to take place of these tools. This is probably the appropriate thing to happen. If the community wants the tooling and MS won't look out for it in this case, 14/
Then "we'll do it ourselves" is the correct response. Looking forward to seeing how I might jump in there.

MS: This is not a good look. Do better. Listen to your OSS veterans. They have your best interests at heart. 15/
OSS is more than just tech. It is also a social contract and a community you agree to participate in alongside your most ardent fans and adopters. Don't take that for granted. There are many inside who know that already. Elevate them. (fin) 16/16.
17/16: I stink at tweet threads and forgot links because of course I did.

* Original PR with vague wording and blog post link: https://t.co/5fpHvtiLan

* The Verge article: https://t.co/wHkGETk2PI

* Great blog by @dustinmoris on the topic: https://t.co/gZBknsbRnX
18/16: Lastly, I'll say that I think folks are trying to work on this internally. I see you and I love you for it. Corporate culture change is so difficult. You have my utmost respect.

You May Also Like

Shaun Russell
Shaun Russell
@_ShaunRussell
"I really want to break into Product Management"

make products.

"If only someone would tell me how I can get a startup to notice me."

Make Products.

"I guess it's impossible and I'll never break into the industry."

MAKE PRODUCTS.

Courtesy of @edbrisson's wonderful thread on breaking into comics – https://t.co/TgNblNSCBj – here is why the same applies to Product Management, too.


There is no better way of learning the craft of product, or proving your potential to employers, than just doing it.

You do not need anybody's permission. We don't have diplomas, nor doctorates. We can barely agree on a single standard of what a Product Manager is supposed to do.

But – there is at least one blindingly obvious industry consensus – a Product Manager makes Products.

And they don't need to be kept at the exact right temperature, given endless resource, or carefully protected in order to do this.

They find their own way.
TECH
Carol Forden
Carol Forden
@CarolForden
1. The major problem most startups face is marketing and the ability to carve out a niche, find and retain paying customers.

Even with a stellar developer team and a stellar product, your startup may not grow or survive without a great marketing and sales teams.

2. Start growing your audience before you’ve a product or an idea.

You should start promoting yourself and building your audience before you have a finished product or even before you have a great idea that you want to build.

3. Don’t wait to start building your audience after you’ve launched a product.

Most first-time developers actually ignore marketing.

They’re oblivious to the challenge of attracting people to take a look at something they’ve created.

4. At least until they see their first project crash and burn within hours of the launch.

There are so many times that I have seen developers spend countless hours building something, releasing it with no fanfare...

5. and only then trying to figure out how to promote it by asking marketing questions on Indie Hackers, Quora or Hacker News. Don’t make that mistake.
STARTUPS
Advertisement
Mau Abata \U0001314a
Mau Abata 𓅊
@MauAbata
Read through a forum thread on Chastity Mansion to see who is talking about the Edge-o-Matic and figure out what more to address regarding frequent questions, as well as scout out user feedback. Here's some thoughts you can carry back to the forums!

My website doesn't have any product reviews, but people scatter them everywhere else in forums, tweets, xtube vids, etc.

If you ARE a previous customer, and you like the thing, can you drop a review on my site to help others?

The price is steep, but that's the amount of coins I calculated to make these. I have several spreadsheets calculating every expense involved with this project.

The current cost sustains production and development of new tech, and is helping create jobs. We are 2 people now!!

It IS 3D printed, because injection molding is orders of magnitude more expensive for the initial tooling, and I am still making small revisions to the enclosures.

Injection molded plastics are a six thousand dollar commitment for fifteen cent parts. Great for mass mfg.

Also, if you didn't know, 3D printing technology allows for some shapes which would be difficult, expensive, or impossible on injection molding or milled parts!!

Undercuts, which I use in this design, require special lifters to mold that cost a tremendous fortune.
FOR LATER READ
Jig's Patel
Jig's Patel
@jigspatel1988
How to trade on Expiry day with Nifty straddle?
(System trading on Expiry)

Triple straddle is one of the best and accurate methods for expiry day

If nifty trading at 15720 then will sell three straddles above 50 points from ATM, below 50 points and ATM.

Ex.
Sell straddle 15700(ATM), 15650(ATM-50), 15750 (ATM+50)

Stoploss of 80% on every leg and run your trade till 3 PM

Once SL hit in any Leg just keep holding other leg till expiry with SL (Never or less chance to hit both SL on expiry day)

Trading timing at 9:20 the Morning
ALL , STRADDLE BACKTEST , STRADDLE
Anu Satheesh \U0001f1ee\U0001f1f3
Anu Satheesh 🇮🇳...
@AnuSatheesh5
Stories of Guruvayurappan
Shri Krishna Leela

This is a beautiful story of Guruvayurappan. Once there lived in Guruvayur a poor family. Kitta, his wife & kids were struggling for their daily needs. With only a coconut tree in house, he earned a living by selling coconuts.


Kitta was from a low caste family. He was a great devotee of Guruvayurappan. Everyday before going to work he always prayed infront of a picture of Guruvayurappan in his house. His only wish was to worship at Guruvayur & have annadanam in temple. But he was not allowed there


It was Utsavam time in Guruvayur. From far behind kitta and family worshipped Guruvayurappan. Annadanam was given daily and no one was left empty stomach. Only Kitta didn't receive. That night, it was only Kitta's family who was sleeping without food. After temple nada closed


Shri Krishna, dressed himself as a Brahmin went to temple Kitchen. He packed food and went directly to kitta's house. Reaching Kitta's house, Shri Krishna told he was sent by a cook of Guruvayur temple and gave them the food he packed. Kitta and family was very happy seeing food.


When Kitta finished his food, Brahmin asked it will be better if he get a tender coconut( karikku)to drink. Kitta climbed the tree and gave all coconuts to him. After having 1 tender coconut, the Brahmin asked to bring remaining coconuts to Guruvayur temple the next day.
ALL