BC TECH
Saved by @CodyyyGardner

Incremental rebuild was a feature of the C# compiler which was meant to increase the throughput after an initial build. It worked on the principle that changes in between builds are localized, and that the information gathered by the compiler from previous builds wouldn't be

 entirely invalidated; specifically, some of the information and, indeed, the assembly itself could be updated in an incremental fashion resulting in faster builds.
Both the VS 2002 and VS 2003 compilers exposed this option through the /incr switch on the command line, and the ‘Incremental Rebuild’ option in the Advanced tab of Project Properties. In 2002 incremental rebuild was enabled by default for all project types.
After we shipped 2002 we noticed that we started to get a large number of bugs (internal compiler errors - ICEs – the worst kind) which were a direct result of the incremental rebuild feature.
These bugs derived from the complexities involved in correctly implementing incremental rebuild and the problems associated with testing it. Consequently, for 2003 we fixed all known issues with incremental rebuild but subsequently turned it off by default for all projects.
Incremental build initially seems like a no-brainer win, it can theoretically improve compilation times by significant amounts, in certain cases we saw single assembly build times improve by as much as 6x.
However, and this may seem counter-intuitive at first, incremental rebuild could also lead to longer build times. Why? The feature had several heuristics to determine whether it should do a full rebuild or not.
One of those heuristics was if > 50% of the files being tracked needed to be recompiled. However, in most cases the files that needed to be recompiled aren't simply the files that have changes, but rather the dependency graph between the changed public interface of the types
within the files and those other source files that depend on those types. So, the compiler would do a lot of work to figure out the dependency graph, and occasionally discover it should actually do a full build anyway.
Due to how incremental rebuild worked, it would then throw out all of the work it had done, and simply perform the normal build at that point, increasing the end-to-end time. Incremental rebuild also had a few other implications that were likely non-obvious to folks.
We wanted to update the existing assembly and PDB, but due to the way they are laid out, incrementally updating them meant they would contain the old data as well and we'd just update the pointers (e.g. in the metadata table) to point to the new locations in the file.
That meant the assembly generated from an incremental build was different than what you'd get from a non-incremental build, and both be larger and slower to load.
The slower to load aspect likely wasn't a big deal; however, the different output spoke to one of the major problems that users had with incremental build. In VS 2002 it was entirely possible to build, have the compiler choke and issue an error, and the simply build again
and have it work. This lowered confidence in the compiler (reasonably), and led to odd conclusions about why the compiler was exhibiting this behavior that were unrelated to the incremental flag, because many users didn't even know it was set.
For example, folks might tweak their code, do another build, and have it work - not because of the change they made, but because a non-incremental build happened. There were at least 13 cases that would cause the compiler to bail on doing an incremental rebuild and perform a
full build instead, including things like 'more than 30 successful incremental builds without a full build', which would prevent the PE from getting too bloated over time. So, whether or not the user actually saw the incremental behavior was difficult for them to predict.
All of this led to the decision to cut incremental build in VS 2005. I should mention that this is incremental compilation of the assembly, incremental rebuild of the solution was most decidedly not cut and was greatly improved in VS 2005 through MSBuild.
The funny thing about this one is that we had initially spent significant design, added complexity to the codebase, and effort in validation (every feature added to the language needed to be separately tested in incremental cases) and when we turned it off by default in VS 2003
essentially no one noticed. We had a few folks who mentioned it in VS 2005, but not because they saw the compiler builds get slower, but simply because they saw the option was removed.
TBH the regular feedback we had was that the compiler was blazingly fast - particularly from folks who had been using C++ for a long while. This is another feature that, looking back, we probably should never have done.
It caused customers tons of headaches for little ultimate benefit. That said, I feel good about our willingness and decision to remove it. Occasionally, at Microsoft we fall prey to the sunk cost fallacy, but it's gotten much better over the years as our telemetry has
dramatically improved and we have lots of additional insight about usage and benefit versus what we had in 2003 when we made this decision. So, if anyone used VS 2002 and wondered what happened to this option, now you know :-)

More from Tech

Yoel Roth
Yoel Roth
@yoyoel
We’ve recently seen research about so-called “bots” and misinformation on Twitter and wanted to share our perspective on why findings that might seem remarkable at first are likely inaccurate. We’re working on a more detailed explanation, but some comments for now.

We continue to be excited by the research opportunities that Twitter data provides. Our service is the largest source of real-time social media data, and we make this data available to the public for free through our public API. No other major service does this.

Many researchers, academics, and journalists use our public API — a set of tools for programmatically accessing information on Twitter. We make all public Twitter content available via our APIs. You can learn more about them here:

The basic issue with much of the research based on our public APIs is simple: The APIs don't provide insight into our defensive actions to protect Twitter from manipulation, including bots.

Because of this, API-based research can't distinguish between accounts we've already identified as bad (and hidden or removed) and real, authentic ones.
TECH
Nicolas
Nicolas
@necolas
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
TECH
Advertisement
s. e. smith
s. e. smith
@sesmith
Oh are we talking about Sheryl Sandberg again? Well, your reminder that disabled feminists, LGBQT feminists, and feminists of color criticised her ‘lean in’ deal from day one. Don’t let anyone retcon that out of existence.

Like, a pretty narrow slice of feminists actually endorse and support corporate feminism, they’re just white, nondisabled, straight, cis, and noisy so their voices have a bigger reach.

So if your impression is that ‘feminism’ gave her a ‘free pass’ maybe you should question your overall impression of feminism rather than continuing to centre a handful of people as ‘thought leaders’ or whatever.

Critics within feminism have been doing this work for a long time and have been getting shat on it for about as long and I'm tired of seeing them erased. But what do I know — I am, after all, not a feminist.

But I WILL say, from my not-a-feminist perspective, that people who aren’t feminists who are criticising feminism should maybe understand the movement more deeply beyond a handful of high profile celebrity feminists.
TECH , SOCIETY
Shannon Woodward
Shannon Woodward
@shannonwoodward
Ok, I’ve told this story a few times, but maybe never here. Here we go. 🧵👇


I was about 6. I was in the car with my mother. We were driving a few hours from home to go to Orlando. My parents were letting me audition for a tv show. It would end up being my first job. I was very excited. But, in the meantime we drove and listened to Rush’s show.

There was some sort of trivia question they posed to the audience. I don’t remember what the riddle was, but I remember I knew the answer right away. It was phrased in this way that was somehow just simpler to see from a kid’s perspective. The answer was CAROUSEL. I was elated.

My mother was THRILLED. She insisted that we call Into the show using her “for emergencies only” giant cell phone. It was this phone:


I called in. The phone rang for a while, but someone answered. It was an impatient-sounding dude. The screener. I said I had the trivia answer. He wasn’t charmed, I could hear him rolling his eyes. He asked me what it was. I told him. “Please hold.”
TECH
Gergely Orosz
Gergely Orosz
@GergelyOrosz
The 12 most important pieces of information and concepts I wish I knew about equity, as a software engineer.

A thread.

1. Equity is something Big Tech and high-growth companies award to software engineers at all levels. The more senior you are, the bigger the ratio can be:


2. Vesting, cliffs, refreshers, and sign-on clawbacks.

If you get awarded equity, you'll want to understand vesting and cliffs. A 1-year cliff is pretty common in most places that award equity.

Read more in this blog post I wrote: https://t.co/WxQ9pQh2mY


3. Stock options / ESOPs.

The most common form of equity compensation at early-stage startups that are high-growth.

And there are *so* many pitfalls you'll want to be aware of. You need to do your research on this: I can't do justice in a tweet.

https://t.co/cudLn3ngqi


4. RSUs (Restricted Stock Units)

A common form of equity compensation for publicly traded companies and Big Tech. One of the easier types of equity to understand: https://t.co/a5xU1H9IHP

5. Double-trigger RSUs. Typically RSUs for pre-IPO companies. I got these at Uber.


6. ESPP: a (typically) amazing employee perk at publicly traded companies. There's always risk, but this plan can typically offer good upsides.

7. Phantom shares. An interesting setup similar to RSUs... but you don't own stocks. Not frequent, but e.g. Adyen goes with this plan.
TECH

You May Also Like

Manas Arora
Manas Arora
@iManasArora
My course is now available for FREE on youtube.

Channel link: https://t.co/BJqESqFVko
ALL
Seth Abramson
Seth Abramson
@SethAbramson
(MAJOR NOTE) The reason Manafort took over Trump's campaign in just 3 weeks despite being hired as a mere delegate counter is that ROGER STONE initiated a whisper campaign against Corey Lewandowski. That campaign started...days after Manafort returned from meeting with WikiLeaks.

2/ Stone and Manafort are longtime business partners; we'd expect Manafort to tell Stone what Assange told him, and for him to expect Stone to then pressure the campaign not only to hire him but quickly elevate him.

And who was Stone in touch with at the campaign? Trump himself.

3/ I bet you Manafort's late March emails are very interesting and that some of them are to/from his longtime business associate Roger Stone. And I bet Roger Stone's late March phone calls are very interesting and that some of them are to/from his longtime friend Donald Trump.

4/ At the end of March 2016, Trump suddenly convenes a NatSec meeting. At that meeting he directs his NatSec team to change the RNC platform in July to benefit Putin. Who later takes credit for that change?

Paul Manafort's business associate, Kremlin agent Konstantin Kilimnick.

5/ Why did Donald Trump suddenly convene a NatSec meeting 3 days after he finally hired Manafort? Why did he issue a pro-Kremlin directive at that meeting that Manafort's camp would later take credit for? What did Manafort tell Trump in the days leading up to that NatSec meeting?
POLITICS
Advertisement
Ferruccio Balestreri \U0001f308
Ferruccio Balestreri 🌈...
@0xferruccio
🕵️‍♂️ How Google's PageRank algorithm works

The PageRank algorithm gives each page a rating of its
importance, which is a recursively defined measure of importance, based on if important pages link to it.
It's recursive because the importance of a page refers back to the importance of other pages that link to it

Here's how it works in practice:
1⃣ We start with some pages and crawl them for links


2⃣ Each page has 1/N points (where N as the total number of pages)


3⃣ Add points to each page for the amount of links to it, divided by the number
of links emanating from the sources of these links
TECH
Jaya_Upadhyaya
Jaya_Upadhyaya
@Jayalko1
HORANADU ANNAPOORNESHWARI, CHIKMAGALUR (KAR)
#bharatmandir

Annapoorneshwari is the Devi of nutrition and food. The literal meaning of Annapoorneshwari is “Feeding one and all”. Anyone who comes here is offered meals and shelter within the premises.
@LostTemple7


Maharshi Agastya is believed to have done pratishtha here.

Once, Shiva and Parvati had an argument. Shiva declared everything in the world including food to be Maya or illusion. To prove him wrong, Devi Parvati disappeared resulting in entire Earth becoming still.


Taking pity, Devi appeared as Annapoorna and relieved everyone.
Another belief is that once Shiva beheaded Brahma and his skull got stuck in Shiva’s hand. He was cursed that till the skull is not full of food or grains, it will remain stuck to his hands.


Shiva went everywhere and asked for food but the skull was never full. He finally came here and Maa Annapoorna filled the skull with grains and reversed Shiva’s curse.

It is believed that who ever visits Devi Annapoorna here will never be without food in their lives.
ALL
The Astro Sapien\u2728
The Astro Sapien✨
@TheAstroSapienn
Here is my Thread on 'Ketu (South Node) Through Nakshatras' The 27 Constellations 🙏❣.

Do check your “Past life Mastery” which KETU Represents🤞🏻.


1. Ketu in Ashwini Nakshatra:

Here native is Great at Financial Planning, Face reading, understanding other’s mind and intention, Driving Fast they don’t like but they are wayyy smooth over driving Fast. This is also great position which can make native Great Surgeon,

Neurologist, Psychologist.
These natives are Selfless and Sacrifice self for others. They gets Fame and Success but they just don’t care.

2. Ketu in Bharani Nakshatra:

They are good at Flirting, Attracting opposite sex, studing ancient subjects. They are also Great at Creativity and Artistic activities. The are lazy but they are really open minded who handles situations really well.

In Past life they have handles many things which is now helping them to make things easier in this life. They are great Leaders too.

They are really good at Hard work and Smart work both. And yes just as Ashwini they don’t much care about Fame and Success!
ALL