#wapi17 - Twitter Hashtag

WAPI'18 @wapi2018

about 9 years ago

$> wapi.slides.publish() Some of our speakers kindly provided their slides an we put them on https://t.co/WNATIZjN0x #icse17 #wapi17

0

2

0

WAPI'18 @wapi2018

about 9 years ago

$> wapi.summary() Read up on all talks and discussion from #wapi17 summarized by @svamann: https://t.co/Lt15qcqOU0 #icse17

0

1

0

Sven Amann @svamann

about 9 years ago

The #wapi17 concluded with an interesting discussion about open research challenges: https://t.co/D4eAtOe037 #icse17 #api

0

1

0

Sven Amann @svamann

about 9 years ago

“Type Checking for Reliable APIs” by @mkechagia and @CoolSWEng https://t.co/9NGFUIVZ8z #wapi17 #icse17

0

4

3

0

Sarah Nadi @sarahnadi

about 9 years ago

Missing a few people who left early, but thanks everyone who joined for #wapi17. Great talks and discussions! #icse17

2

14

2

0

WAPI'18 @wapi2018

about 9 years ago

How do Web APIs and APIs relate? New research challenges from #wapi17 https://t.co/ng4bqVyeek

Annie Ying @annieying

about 9 years ago

API Harmony @ApiHarmony putting web APIs on the map in the Workshop of APIs @wapi2017 !

0

4

3

0

1

0

Sven Amann @svamann

about 9 years ago

API Evolution and Migration at Google by @hyrumwright https://t.co/vBuxVyuWSo #wapi17 #icse17

0

1

3

0

Sarah Nadi @sarahnadi

about 9 years ago

Lots of discussion points for #wapi17 after the coffee break #icse17

0

4

2

0

Sarah Nadi @sarahnadi

about 9 years ago

Last paper talk at #wapi17. @mkechagia talking type checking APIs #icse17

0

5

2

0

Thomas LaToza @[email protected] @ThomasLaToza

about 9 years ago

When you have a system with 100k users, cannot chnge comment without breaking dependency. (Why? Brittle test on line num). #wapi17 #icse17

ThomasLaToza's tweet photo. When you have a system with 100k users, cannot chnge comment without breaking dependency. (Why? Brittle test on line num). #wapi17 #icse17 https://t.co/A5TbYD8a2Y

0

7

4

0

Thomas LaToza @[email protected] @ThomasLaToza

about 9 years ago

It takes more effort, by an order of magnitude, to kill an old API than to write it in the first place. @hyrumwright #wapi17 #icse17

0

3

0

Sarah Nadi @sarahnadi

about 9 years ago

Excited to listen to @hyrumwright's talk about how Google deals with API migration and evolution. #wapi17 #icse17

0

3

0

WAPI'18 @wapi2018

about 9 years ago

.@PaigeRodeghero is also on the market. Don’t miss it! #wapi17 #icse17

0

3

5

0

WAPI'18 @wapi2018

about 9 years ago

“API Usage in Descriptions of Source Code Functionality” by @PaigeRodeghero https://t.co/TYojBFjDEN #wapi17 #icse17

0

1

3

0

Sarah Nadi @sarahnadi

about 9 years ago

Nice work on web APIs by @erikwittern & @annieying at #wapi17 . they also have a related talk at #icse17 thurs at 11am

0

2

0

Thomas LaToza @[email protected] @ThomasLaToza

about 9 years ago

Lack of type checking, freq changes, external control, and QoS differences all make API consumption hard. #wapi17 #icse17

ThomasLaToza's tweet photo. Lack of type checking, freq changes, external control, and QoS differences all make API consumption hard. #wapi17 #icse17 https://t.co/vfYdSjeGmK

0

2

1

0

Thomas LaToza @[email protected] @ThomasLaToza

about 9 years ago

Many open challenges incorporating usability into API design, incl. better process & guidelines. @bradamyers #wapi17 #icse17

ThomasLaToza's tweet photo. Many open challenges incorporating usability into API design, incl. better process & guidelines. @bradamyers #wapi17 #icse17 https://t.co/Mzq9k6XEZy

0

2

0

Sarah Nadi @sarahnadi

about 9 years ago

.@erikwittern talking about Web APIs at #wapi17 #icse7

0

2

0

Sarah Nadi @sarahnadi

about 9 years ago

Now, @PaigeRodeghero talking about API usages & documentation of method summaries #wapi17 #icse17

0

2

1

0

Thomas LaToza @[email protected] @ThomasLaToza

about 9 years ago

API middleware is a $5.5B business. @bradamyers #wapi17 #icse17

0

5

7

0

Top Tweets for #wapi17

Last Seen Hashtags on Sotwe

Trends for you

Most Popular Users