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

Patrick McKenzie
Patrick McKenzie
@patio11
It’s underremarked upon that stablecoins accomplish basically all of the original design goals for Bitcoin qua a transactional mechanism (instant free value transfer anywhere), but that nobody cares about this because nobody ever cared about that part of the pitch.

“Why do people care about stablecoins then?”

A mix of “they encourage dollar-denominated liquidity in the cryptocurrency ecosystem and discourage withdrawal of the same” and “they’re good for money laundering.”

“But they make value transfer between exchanges much faster!”

This was a solved problem in traditional finance, too, mostly through the extension of credit. (It doesn’t matter how long settlement takes if there is sufficient trust to enable credit.)

The Bitcoin ecosystem is *positively allergic* to credit, so you have to call it a coin for them to accept it. And after you call it a coin they ignore everything the world has learned about credit, like risk management.

“Stablecoins aren’t credit!”

They’re pretty much exactly credit? A tether is a zero-coupon Bitfinex bond with a non-functioning call option. I
TECH
ashkan soltani
ashkan soltani
@ashk4n
BREAKING: @CommonsCMS @DamianCollins just released previously sealed #Six4Three @Facebook documents:

Some random interesting tidbits:

1) Zuck approves shutting down platform API access for Twitter's when Vine is released #competition


2) Facebook engineered ways to access user's call history w/o alerting users:

Team considered access to call history considered 'high PR risk' but 'growth team will charge ahead'. @Facebook created upgrade path to access data w/o subjecting users to Android permissions dialogue.


3) The above also confirms @kashhill and other's suspicion that call history was used to improve PYMK (People You May Know) suggestions and newsfeed rankings.

4) Docs also shed more light into @dseetharaman's story on @Facebook monitoring users' @Onavo VPN activity to determine what competitors to mimic or acquire in 2013.

https://t.co/PwiRIL3v9x
TECH
Advertisement
Patrick McKenzie
Patrick McKenzie
@patio11
Most software founders, particularly in B2B, need to get radically better at sales. @Steli , who is the best person for explaining the scrappy stages in the beginning and then building out a team with scripts and processes, wrote a guide to:

For technical founders it is irrationally, obscenely hard to reverse years of programming (ba dum bum) that sales is a value-destroying activity. Sales is CLEARLY a value-creating activity, contingent on you have a value-creating product.

The world will not drop what they are doing to adopt your work. This is particularly true in B2B, where simply building a better mousetrap won't overcome the activation energy required to get people with additional non-mice problems to prioritize changing mousetraps today.

This is very non-obvious for founders because founders are not often people who *want* to be sold to. We often come from a background where trying out tools is a bit of a fun hobby. We like looking at all the options, making charts, and ripping out partially complete tests.

"This week I unsuccessfully trialed four software options for automating that thing that has been killing us. Our actual production process remains the same as last week. Don't worry; this was a great use of time." is not a thing you want to write in a progress report to manager.
TECH
Ameya
Ameya
@Finstor85
After getting good feedback on yesterday's thread on #routemobile I think it is logical to do a bit in-depth technical study. Place #twilio at center, keep #routemobile & #tanla at the periphery & see who is each placed.


This thread is inspired by one of the articles I read on the-ken about #postman API & how they are transforming & expediting software product delivery & consumption, leading to enhanced developer productivity.

We all know that #Twilio offers host of APIs that can be readily used for faster integration by anyone who wants to have communication capabilities. Before we move ahead, let's get a few things cleared out.

Can anyone build the programming capability to process payments or communication capabilities? Yes, but will they, the answer is NO. Companies prefer to consume APIs offered by likes of #Stripe #twilio #Shopify #razorpay etc.

This offers two benefits - faster time to market, of course that means no need to re-invent the wheel + not worrying of compliance around payment process or communication regulations. This makes entire ecosystem extremely agile
TECH
Joe Natoli
Joe Natoli
@joenatoli
#UX and #design friends, we need to talk about estimating. I'd like to share some advice that's come up 3 times this week, in hopes it's useful. And it's echoed, by the way, in the BUSINESS OF UX course @EliNatoli and I are teaching at my UX 365 Academy (link at the end).

(1/12)

Avoiding wars with clients is a matter of how you structure your engagements, along with how you spell out what you're doing in your proposals/contracts. That starts with estimating.

The biggest 2 rules I follow are these:

(2/12)

1. I do not EVER estimate a project in full from start-to-finish.

2. Once we're past initial Discovery (see below), I estimate in small chunks, e.g. "here's what will take us to the next iteration/review."

(3/12)

NEVER estimate past the point where you may get new information based on a build/test cycle.

Believe me when I say that you'll be wrong every time. Ask me how I know ;-)

(4/12)

So instead, first, I estimate a Consult/Discovery part that details what I think we need to do to get a handle on what's actually wrong here, and how long that will take.

For example...

(5/12)
TECH

You May Also Like

Reagan Gomez
Reagan Gomez
@ReaganGomez
Black movie goers know which movies are for us and which films aren’t. We really don’t like our stories being made into films that center (and humanize) people that hate us. The filmmakers/studio know that by naming the film “The Green Book”, black movie goers...

...are going to be expecting a story about black people trying to safely navigate the country (real history) and instead will get a white savior film. Like folks went to see Detroit thinking it was about the riots...

Anywhoo, I know Mahershela is fantastic in it. He was the best thing about the trailer. As rich as the history behind the creation of ‘The Green Book’ is/was, as amazing as Dr. Don Shirley’s story is, WHY is this film about a random, racist driver and his family?

This feeds into the ignorant anti-Black American stereotype of “Black Americans don’t have any culture/history/mythology” or whatever. That our stories are still both being used while simultaneously erased in 2018 is wild to me. It’s gonna clean up come award season. 🤦🏾‍♀️

And now, if black filmmakers WANTED to make a film about The Greenbook, guess what it can’t be called🙃. Just like if someone wanted to make a film about the actual Detroit riots, guess what it can’t be called? Then those filmmakers would run into...
CULTURE
Kestrel \u2664 lwj kin
Kestrel ♤ lwj kin
@slutxian
MDZS is laden with buddhist references. As a South Asian person, and history buff, it is so interesting to see how Buddhism, which originated from India, migrated, flourished & changed in the context of China. Here's some research (🙏🏼 @starkjeon for CN insight + citations)

1. LWJ’s sword Bichen ‘is likely an abbreviation for the term 躲避红尘 (duǒ bì hóng chén), which can be translated as such: 躲避: shunning or hiding away from 红尘 (worldly affairs; which is a buddhist teaching.) (https://t.co/zF65W3roJe) (abbrev. TWX)

2. Sandu (三 毒), Jiang Cheng’s sword, refers to the three poisons (triviṣa) in Buddhism; desire (kāma-taṇhā), delusion (bhava-taṇhā) and hatred (vibhava-taṇhā).

These 3 poisons represent the roots of craving (tanha) and are the cause of Dukkha (suffering, pain) and thus result in rebirth.

Interesting that MXTX used this name for one of the characters who suffers, arguably, the worst of these three emotions.

3. The Qian kun purse “乾坤袋 (qián kūn dài) – can be called “Heaven and Earth” Pouch. In Buddhism, Maitreya (मैत्रेय) owns this to store items. It was believed that there was a mythical space inside the bag that could absorb the world.” (TWX)
RELIGION
Advertisement
Jaya_Upadhyaya
Jaya_Upadhyaya
@Jayalko1
SRI VARAHA NARSIMHA, SIMHACHALAM, VIZAG (AP)
#bharatmandir

One of the 32 Narsimha Kshetram of Andhra. It has a unique form of Narsimha, appearing like a shivlingam

It is said that Narsimha’s fierce nature is soothed by worshipping him with Varaha, considered a peaceful deity


The shrine is believed to have been constructed by Prahlada. With time, it crumbled.
In Treta yuga, King Pururava was passing from here in his vimana. The vimana was attracted to this place by a mystic power.
When the place was unearthed, the deity was found.
@GunduHuDuGa


Pururava’s wife, Urvashi, had a dream that the deity should remain covered in sandalwood paste for the whole year except on Akshaya Tritiya.
This practice has continued till date.
The mukhya mandap here, has a pillar kappam stambham believed to possess curative powers.


Chandanotsava/ Chandan Yatra is the most important festival celebrated on Akshaya Tritiya. The sandalwood paste is removed from the moolavar deity and nijarupa darshan (original form of deity) for twelve hours of the day are done by devotees.
ALL
Coffee Sloth \u2615
Coffee Sloth ☕
@CaseyExplosion
*Heads-up that this thread will feature some extreme examples of homophobia and transphobia.*

Hey folks, have you ever wondered why trans people face constant accusations of fetishism, sexual predation and child abuse/grooming? Well, today let's talk about stochastic terrorism.

So, first we have to talk about what stochastic terrorism actually is. Remember when there was a conspiracy that there was a pedophile ring operating out of a pizza parlour basement, and a crazed gunman showed up? It's that sort of incitement that stochastic terrorism describes.

It's the demonisation or incitement against a group of people or individuals with the intent that other, unaffiliated parties will act upon it; it's the releasing doctored footage and a shooter show up at Planned Parenthood as a direct result of what he's been led to believe.

So with that in mind, let's talk about Russia's extreme anti-LGBT laws that banned the "promotion" of LGBT lifestyles to children. A move that specifically marked LGBT people as a threat to children, and resulted in neo-nazis meting out vigilante "justice" against gay men.


Groups such as this would lure unsuspecting gay men via dating sites, and brutalise and humiliate them on camera. They did so under the guise of combating child abusers, one group calling themselves "Occupy
SOCIETY
Vibhu Vashisth
Vibhu Vashisth
@VIBHU_Tweet
Surkanda devi mandir is a famous shrine of Hindus located near Kaddukhal distt of Uttarakhand, 11 Km from the town of Dhanaulti and 35 Km from Mussoorie.
The Temple is one of the 51 Shakti Peethas spread all over Indian Subcontinent and is dedicated to Goddess Surkanda.


Nestled on a Hill at an Altitude of 2700 m approx, the place offers a splendid view of the snow capped mountains, the picturesque scenic beauty that offers an experience of the lifetime.
The Temple build in the traditional Garhwal style exuberates the Architectural splendour.


The origins of the Surkanda Mata Mandir is attributed to Goddess Sati, consort of Bhagwan Shiv who in a rage immolated herself in her arrogant Father Daksha's Yajna Kund bcoz he didn't invite Bhagwan Shiv in the Yajna.


Devastated by the death of Sati Shiva wandered all over the cosmos performing Tandava-The Dance of Cosmic Destruction.Fearing the total annihilation of cosmos, Gods requested Bhagwan Vishnu to pacify Shiva.Bhagwan Vishnu then used his discuss to destroy the burning corps of Sati.


The pieces of Sati Mata's body then got scattered all over the region which were later established as Shakti Peethas by Bhagwan Shiva himself.Its believed that the head of Sati fell here and it was called Sirkhanda Mata Temple before, but with passage of time it became Surkanda.
ALL