BC SOFTWARE
Saved by @CodyyyGardner

1/ In early 2004 we were heads down executing on Edit and Continue across a large contingent of teams. There had been several iterations of scoping, redesigns, and customer feedback.

 2/ We had a weekly meeting every Thursday morning when representatives from each of the teams would get together and review progress. It was fairly heavy weight, but there were so many teams involved that it was necessary to have a regular sync.
3/ Regardless, E&C was coalescing, but teams were stretched thin working diligently to enable scenarios, improve performance, fix bugs, etc. It had been a month or so since we decided to add support for C# to the matrix as well, so folks were a bit stressed.
4/ That set the stage for the meeting that we had on the first Thursday in April. A debugger PM named Habib Heydarian ran the meeting and after a brief intro he gave me a ring to come in and present.
5/ I walked in and handed out a document that I had written up, titled DCR: C# Edit and Continue for Venus. DCR meant design change request, and Venus was the design-time code name for ASP .NET support.
6/ I explained that we had a recent review with leadership and that while the feedback was very positive, we had been asked to enable E&C for ASP .NET as well.
7/ The room was shocked - their teams were already over-extended and ASP .NET support was something that we had scoped out essentially day 1.
8/ We then proceeded to review the document which went through the customer rationale, scenarios, the user experience design, and suggested architecture. The first Thursday of April in 2004 happened to be April 1st - April Fool's Day.
9/ The 'spec' looked and read legitimately for the first sections, but was intended to get wilder and more ridiculous as we read through it.
10/ In the final section it had statements like "happily, most of the work for edit and continue has already been done for the Client, so extending it to support Venus should be relatively trivial" (absolute nonsense of course). as well as
11/ "however, it is also necessary to make Office development support EnC."
12/ It went on to suggest that the only reasonable way to get design time support for this scenario was to run the language service on the server, which, despite what we've been doing with Codespaces recently, was absolute crazy talk at the time.
13/ This was the 'architecture diagram' included:
14/ When we got to this point in the document, I expected folks to catch on that this wasn't serious, or at least, call out that perhaps some more thinking would be needed :) I tried to make it as ludicrous as possible, without any detail, with arrows just randomly drawn in…
15/ but... TBH, I think folks were in shock as no one said anything. In fact, a good number of folks were busy writing emails to their teams and management - once Habib and I realized that, we finally told people it was a prank.
16/ I'm not *exactly* sure how many folks in that room hate me to this day, but based on the reactions then, it maybe wasn't quite as funny as I had hoped :-)
17/ I'm sure it'd make folks feel better to know that I spent a good portion of the rest of the day answering emails from various levels of management who were still convinced it was real and were uh, nonplussed, when I told them it wasn't.
18/ Habib and I did a brief Channel 9 video a couple of years later where we talked about it which is still available here: https://t.co/nrzm1wGvpZ. Since the only comment on the video is "I missed what the prank is exactly…"
19/ we somehow managed to have perhaps the unfunniest prank in the history of computing, but we tried! FWIW, a few folks eventually got a laugh out of it, you know, after they stopped being enraged.

More from Software

Chris Heilmann
Chris Heilmann
@codepo8
🚨 🦮 Seven ways to test for accessibility using only what is already in browser developer tools of Chromium browsers https://t.co/C7kdbigHGE

@MSEdgeDev @EdgeDevTools @ChromiumDev
#tools #accessibility #browsers
Also, a thread: 👇🏼


Issues pane, powered by @webhintio, listing accessibility issues with explanations why these are problems, links to more info and direct links to the tools where to fix the problem. https://t.co/4K5RynHhbg


The inspect element overlay showing accessibility relevant information of the element, including contrast information, ARIA name, role and if it can be focused via keyboard.


Colour picker with contrast information offering colours that are AA/AAA compliant. You can also see compliant colours indicated by a line on the colour patch.
Note: the current algorithm fails to take font weight into consideration, that's why there will be a new one.


Vision deficit ("colour blindness") emulation. You can see what your product looks like for different visitors.
https://t.co/bxj1vySCAb
INTERNET , SOFTWARE
Jack Butcher
Jack Butcher
@jackbutcher
Building Principles:

↓

1/

Value = doing things that other people don't do, won't do or can't do.

"You get paid in direct proportion to the difficulty of problems you solve" — Elon Musk


2/

Service is high-touch result generation (building experience), product is low-touch result generation (scaling experience).


3/

In a world of infinite distraction, focus is the only path to freedom.


4/

Sell time to buy experience, sell experience to buy time.

“If you don't find a way to make money while you sleep, you will work until you die.” — Warren Buffett
SOFTWARE , ALL
Advertisement
Andrew Harmel-Law \U0001f3e1
Andrew Harmel-Law 🏡...
@al94781
Software architecture is in crisis, and the way to fix it is a hefty dose of anarchy.


Some lay the blame for this on @boicy with the whole microservices thing.

(Admittedly, @nicolefv, @jezhumble and @realgenekim didn’t help when they statistically proved that he might have been onto something with all that de-coupling and team-alignment…)

However I don’t blame him at all.

I think he saved us; bringing us back to the path of value-delivery and independent services, but now with added independent teams.


But one thing is clear. Microservices need more architecture, not less (as do other forms of #Accelerate-style software organisation).

(See https://t.co/B2hWmXhIqe if you need convincing)

I mean, all those pesky slices we need to carve up our monoliths (or were they big balls of mud?) That’s a significant amount of work right there…
SOFTWARE , ARCHITECTURE
Jessica G. Young
Jessica G. Young
@JessGeraldYoung
@JuliaLMarcus @Iplaywithgerms This paper gives documentation on software (with causal reasoning, assumptions reviewed in appendix) for a parametric approach to estimating either "total effects" or "controlled direct effects" with competing events and time-varying

@Iplaywithgerms Total effects capture paths by which treatment affects competing event (e.g. protective total effect of lifesaving treatment on dementia may be wholly/partially due to effect on survival). Controlled direct effects do not capture these paths

@Iplaywithgerms More detailed reasoning on the difference and tradeoffs between total and controlled direct effects and causal reasoning in the point treatment context provided here along with description of some estimators and

@Iplaywithgerms If you are familiar with more robust approaches like IPW or even better TMLE for time-varying treatment, these are trivially adapted to go after the controlled direct effect by simply treating competing events like loss to follow-up (censoring). e.g.

@Iplaywithgerms Examples of IPW estimation of the total effect of a time-varying treatment described in Appendix D of this paper:
https://t.co/RNhcgTBMkb
And here
https://t.co/rMWmwFBWwV
Others in reference lists of above papers.
SOFTWARE
foone
foone
@Foone
now that's a title screen


foolish people like to quote that "science says there are only two genders". This is incorrect.

Science instead says that in addition to the regular genders, there are 25 Science Genders, shown here. (tag yourself I'm Skull)


I have no idea how to continue with this game.
I clicked a bunch of things and the game just pauses for a second, except when I clicked electron it animated and then was replaced by... something


Quarky & Quaysoo's Turbo Science!

Turbo Science is like regular Science, but FASTER


oh I see

is this Gizmos and Gadgets but by Sierra?
SOFTWARE

You May Also Like

Brian Armstrong
Brian Armstrong
@brian_armstrong
1/ Productivity tip: when I keep procrastinating on something I often trick myself by saying, "ok just work on it for the next 20 minutes" or some short period of time, "and then you can chill/relax guilt free" and give myself some treat (sugar, netflix, etc)

2/ Usually at the 20 minute mark (sometimes I set a timer) I'm so engrossed in what I'm doing that I don't want want to stop and end up working on it for the next hour or two. But getting started seems to be the hardest part.

3/ Key to this: you have to actually be ok with stopping after 20 minutes and being guilt free if that's how you feel. So it's not a trick, i have the option every time, I just often don't want to use it once i'm in the zone.
PRODUCTIVITY
Aditya Todmal
Aditya Todmal
@AdityaTodmal
The absolute best 15 scanners which experts are using.

Got these scanners from the following accounts:

1. @Pathik_Trader
2. @sanjufunda
3. @sanstocktrader
4. @SouravSenguptaI
5. @Rishikesh_ADX

Share for the benefit of everyone.

Listing all scanners from @Pathik_Trader Sir first.

1. Open

2. 80-20 Reversal Setup


3. Fake

4. Trapping Inside Bar (Positional Setup)
TECH , STOCKLEARNINGS , STOCKS
Advertisement
Vibhu Vashisth
Vibhu Vashisth
@VIBHU_Tweet
RANI NAIKI DEVI AND THE BATTLE OF KASAHRADA

Mohammad Ghori, the young Ghurid Prince conquered Ghaznavids in Afghanistan in the year 1173 CE. He conducted some successful raids into the Indian territory, which even Mahmud Ghazni & the Persians couldn't do.


First&foremost,Ghori invaded states of Multan &Uch in India.After this he turned to southern states of Gujarat &Rajputana.Everybody knows this about Ghori,but what most pple r unaware of is the defeat he suffered at hands of Chalukyan Queen Naiki Devi in 1178 Battle of Kasahrada.


When he marched southwards, his first target was the prosperous fortified town of Anhilwara Patan.
It was the capital of Chalukyas(also known as Solankis of Gujarat) which was established by Vanraj of Chapotkata Dynasty in 8th century.


American historian Tertius Chandler states that it was the 10th largest city in the world at that time. The history of Chalukyas has been written by many historians, but the valour of the Great Queen Naiki Devi remains unsung.


Born to the Kadamba King Paramardin of Goa,Naiki Devi was well trained in sword fighting, horse riding, strategy & every other subject of Statesmanship. She was married to King Ajaypala of Gujarat who sat on throne in 1171CE. Unfortunately,the King died within 4 yrs of his rule.
ALL
Marc K\xf6hlbrugge
Marc Köhlbrugge
@marckohlbrugge
💬 I often get Q’s like these:

How did you get your first customers for WIP? How did you grow BetaList’s traffic? Etc.

Makers are looking to reverse-engineer success. I see it everywhere.

I don’t think it works that way and the answers to those questions are mostly useless. 💥

I have built dozens of different products over the last couple of years. The vast majority failed. 😭

Surely if I know the answers to these questions, but still fail over and over again, these answers aren’t that useful. 🤷‍♀️

So what’s a better question to ask? 🤔

99.9% of the questions I receive are about the products that did well. In a way that makes sense, because we quickly forget about those that didn’t succeed.

🧠 This is known as survivorship bias.

Focusing on what survived, while ignoring what made it survive in the first place.

The real question, what you really want to know, is this:

What makes @WIP, @BetaList, and to some extent @AllStartupJobs succeed where my countless other attempts failed?

What separates a failed product 👎 from a successful product 👍?

Honestly, I don’t know. I wish I did.

It’s like Steve Jobs said “I’ll know it when I see it.” 👀

Same is true when we make products. We don’t know upfront what will work. But once we see an inkling of a product that does have potential, it’s not that hard to spot.
STARTUPS
Anu Satheesh
Anu Satheesh
@AnuSatheesh5
Beautiful story of Shri Krishna, Mata Rukmini & Satyabhama which teaches the importance of Bhakthi.
Devotion is important than anything.
#bhakthi
🕉
Satyabhama, royal princess was very proud of herself. Rukmini was very humble, her devotion was pure to Shri Krishna.


One day, Rishi Narada( Kalahapriya) arrived in Dwaraka and met Sathyabhama. In between the conversation he hinted that Krishna exhibits affection more to Rukmini than her. Worried Sathyabhama asked what can should be done to gain Krishna's undivided attention.
@SriramKannan77


Narada asked Satyabhama to make a vow, that she will hand over Krishna to him as a slave, if she cannot trade wealth equivalent to Krishna's weight. Narada thus convinces Sathyabhama that Krishna will admire her for sacrificing all her wealth for him.


Sathyabhama was sure that she have enough wealth to balance Krishna.

She went to Krishna and told about her vow to Narada. Krishna patiently listened to her and accepted the challenge. Satyabhama arranged to bring large scales to weigh and brought all her precious jewels.


Krishna patiently sat on one plate of the Scales (tula). Sathyabhama started piling up the gold, jewels on the other plate. She kept adding more and more wealth, but the pan with Krishna did not even budge. Even after keeping all her jewels the scale did not move a little
RELIGION