After four days of combining business and pleasure in this beautiful area, we're getting ready for the main event: the An Event Apart conference.
Today's Document
đȘŒ
he wasn't even looking at me and he found me
Monterey Bay Aquarium

â
d e v o n
No title available
sheepfilms

No title available
i don't do bad sauce passes

oozey mess

@theartofmadeline

Origami Around
Claire Keane

Discoholic đȘ©
Mike Driver

ç„æ„ / Permanent Vacation
Sweet Seals For You, Always

Love Begins
One Nice Bug Per Day
seen from United States

seen from United States

seen from United States
seen from United States

seen from United States

seen from United States
seen from United States
seen from Germany

seen from United States

seen from United States

seen from Malaysia

seen from Germany
seen from United States
seen from United States
seen from United States
seen from United States

seen from T1

seen from United States

seen from United States

seen from United Kingdom
@vgconf
After four days of combining business and pleasure in this beautiful area, we're getting ready for the main event: the An Event Apart conference.
DroidCon UK 2015 day 2
If I was a bit negative yesterday, that is all gone today. What a day! Great talks and great atmosphere here. Seriously considering cashing in on the early bird ticket for 2016 already now (one fifth of the price this weekend).
Highlights of the day was the keytalk (again) on general tips on performant Android development, Duana Stanleyâs talk on micro services and getting a chance to talk to Olivia from the React Native Facebook team as well as Mohammad from the Guardian about their app.
Keynote - âAndroid is not Javaâ by Senior Software Engineer at Google, Chet Haase.
This was a very hands-on talk about the differences between being a Java developer and an Android developer which was a bit of a wake-up call for me. Developing on a device with four CPU cores on 2.3GHz, one kind of forgets that itâs still only a phone with limited resources, that not all devices have those specs, and that weâre not running on the JVM but ARM/Dalvik. All slides were packed with concrete tips which Iâve taken notes of but which are too many to list here.
âReact Nativeâ by Olivia Bishop from Facebook
An intro to React Native for Android. Having spent a day testing this a week prior to the event, the contents of this talk was mostly known to me except for a couple of key points:
The latest build support hot-loading of images. Yay! :)
Facebook is considering making the React Native JSX also for web. I.e. instead of . Would make tri-platform-development simpler (iOS, Android, HTML). Interesting!
It was also new to me that most React Native development happens from the team in London. I got a short chat with Olivia after the speak and it was reassuring to hear about their dedication!
âWorking together - Avoiding house divided with developers and designersâ, Juhani LehtimĂ€ki
This âsoftâ talk the cooperation process was a nice break from the technical. Juhani was experienced in this regard and held an entertaining and educating talk on the subject. I we at VG are pretty good at this but we can always be better. Key takeaways:
Handover from design to development is not a one-time process, but an iteration
Try finding and implementing the easy wins design-wise first, leaving the fancy design which is hard to implement last.
Designers must educate themselves in the platform they design for, and the developers must in a helpful manner aid to this.
Developers must tell the designers what can easily be done programatically so that they donât waste time doing work the Android platform can do.
âMaterial Design Adaptive UIâ - Marcos Paulo
A talk on how to use principles from Responsive design on Android. Adaptive is not responsive though, but the principles are the same. Design for multiple screen sizes and modes using the Android âGridâ and âPercentLayoutâ. He also encouraged not to blindly follow the Android Design Guidelines but to stay creative.
At the end of the talk the power to his Macbook died so he told an anectode about this one time he did karaoke. Almost expected him to start singing. He didnât but still humorous :)
âKotlinâ, Jake Wharton
The only reason I went to this talk was because itâs held by Jake Wharton. My qualms with Java is all but gone after becoming friends wtih Lambdas and RxAndroid, so why learn a new language?
Kotlin is a functional language from Jetbrains running on the JVM/ARM which is promising to make Android programming fun again (I believe it already is). It took Jake about 20 minutes to get to the point (the background was needed) and while I got it, Iâm unsure Iâm totally convinced yet.
In short, Extension Function Expressions (watch the video to understand it) allow you to create elegant code wrappers around nasty Android SDK functions (or your own), without adding overhead the way you would do with Java wrappers. The talk was very relevant to the keynote where Chet Haase stressed keeping the number of classes to a minimum in any Android project.
âMicroservices is our BFFâ - Duana Stanley from SoundCloudÂ
A back-end talk at a front-end conference, but a very relevant one. She talked about how they had rearchitected their service infrastructure in SoundCloud to accomodate for more rapid development. A lot of pointers to take home to VG here. Basically building a layer of services specialized for mobile presentation in front of the generic REST services enabled SoundCloud to be more agile.
I will go into detail about this in our next dev meeting.
SoundCloudâs infrastructure before the refactoring
âAndroid is the world phoneâ - Corey LatislawÂ
Corey gave us a reminder on that Android is growing extremely fast in developing countries - Russia, Brazil, India, Brazil and many African countries. World wide, 80% of the smart phones are Android phones. What oppurtunities lies in this and what are the challenges? She talked about how to tackle cultural and language differences or even illiteracy. How do find out about your users needs when theyâre at the other side of the world (basically go there).
Not very relevant for VG only producing apps for the Norwegian market but a good reminder on the impact of Android phones.
SummaryÂ
I had a great time at DroidCon UK. The conference grew on me from day 1 to 2 and I met a lot of great people. Everyone I talked to was open and friendly and it was a really good atmosphere there. I was also surprised with home many big names were there both as speakers and in the stands. This is really the conference to attend for Android developers in Europe, and the range of attendees reflected that as well. I heard German, Dutch, Italian, Spanish, Portuguese, English, American, Swedish, Danish, Norwegian, Russian and Polish being spoken, and probably a bunch of other languages as well. Definitely considering going back next year!
DroidCon 2015 day 1
DroidCon is one of the largest Android-related conferences in the world and has been organized for 4-5 years already. Many of the big names in the Android world are on the speakers list, so I was keen to see what this conference had to offer.
Yellow flag already before I had entered the building. There was a line. A long one. I knew I was in the right line though becuase no one talked. But didnât the venue have the capacity for the amount of people signed up? Or were the organizers understaffed? After 15 minutes of waiting it turned out not to be that bad, yet Iâm sitting here writing my blog now instead of attending the final talk of the day becaue the capacity of the room was blown.
Also fix your Wifi. It does not work in 9 out of 10 attempts. Oh yeah and when Iâm ranting: The âBarCampâ-thing could be better organized. "BarCamp" turned out simply to be open slots in the programme to which there may or may not have been some democratic voting system which decided which talks would be held. Wasn't very much information about this - the organizers kind of expected everyone to have attended this before and to know what it was. I would prefer to know the theme of the talks up front, and not having to scramble on the non-functioning internet 5 minutes before the start to (not) find out what the subject would be.
Enough negativity. There have been some highlights today. In short:
The keynote
Meeting other developers from Schibsted
The keynote
The theme suprised me: Taking charge of your career. This turned out to be a really interesting non-technological talk by a technologist from Brazil, Sandro Mancuso. At 17:00 this is still the most interesting talk of the day. Maybe it's because I'm getting old and experienced so the technological talks really have to impress me to blow me away. Or maybe The tech talks simply were bad or trivial, I don't know. Key take-aways:
Your job is not your career
Stay in your job as long as your career goals aligns with your company's goals. Then quit. (Best for you, best for the company)
Don't use recruiters. Neither as job-seeker or when recruiting.
Ever
Recruiters are a disease that needs to be eradicated from the face of the earth.
When you conduct interviews with code submissions, do the candidate a favour and always give feedback even though you do not hire him/her.
In Interviews, ask questions related to the day-to-day job - not abstract algorithmic questions anno Google 2009
Interviews are a two-way street. Sell your company and your people to get the best candidates.
Side note: Are we at VG as good as we can be here? Could we have a web page presenting individuals in the development team?
The social part
Thanks to the #sch-android channel on Slack, I've been able to join up with Lasse from Finn.no, Gustav from Blocket.se and Ronan and Conorfrom DoneDeal.ie. I'm surrounded by classifieds :( But that's fine :) Great guys and we've already had some interesting technological discussions. We will go for a beer later and probably solve some world (tech)problems.
In general there's a lot of opportunities for socializing and getting to know the speakers here - they all have stands in addition to appearing in the "mingle zone". I'll be sure to seize the opportunity to talk to more guys from some of the big companies that are represented here.
Other talks
Talk 2 - The journey of Touch events
Marco Cova from Facebook talked about the pitfalls with the touch event system on Android and how he overcame them to build awesome UI controls in the Facebook apps. Good to know for that day we'll do the same :)
Talk 3 - Gradle
Etienne Studer from Gradle talked about the upcoming performance improvements in the next version of Gradle
Showed some nice graphs on what takes time in the build process. Basically Google needs to get their shit together with the DEX process ;)
Talk 4 - Gradle plugins take it to the next level:
Eyal Lezmy from Genymotion talked about how he made their Gradle plugin and how we could do it as well
Meh
Talk 5,6,7: Open slots/ "BarCamp" .
Attended briefly one about animation, but left before 10 minutes had passed because I got the impression it would be just about what's well documented by Google and partly known by me
Attended one about how to use Genymotion emulators in the CI-cycle. Not sure we would want to do that, but interesting nontheless
Spent time socializing instead of attending the one about improving Gradle Performance.
I kind of regret not going to the ones about the XDA web site and the one about reverse engineering now that I know the quality of the other talks. I hope & think they post the videos online though, so I'll check them out.
Looking forward to tomorrow - a more packed program and what seems like a good lineup.
ONA15: Breaking News in 2015 is Reshaping Social Newsgathering
Hele sesjonen kan sees og hĂžres her:Â http://ona15.journalists.org/sessions/socialnewsgathering/
Notater:
Newsrooms now have teams dedicated to social newsgathering.
Mandy Jenkins from Storyful, social news agency. Tech + investigative journalism skills. Dig in to find sources on the ground, eyewitnesses, people sharing photographs/video. We contact them and verify facts, copyright clearance.
Fact checking by looking at buildings on Google map, does photos match the weather at the supposed time/location.
Andy Carvin, Reported.ly.
Our office hours are on Twitter. Team spread over 10 time zones.
Real time rather than breaking news. Many have resources to be first. We want to go deeper into the story and find out who the people are, analyze what's happening. Not racing to be first. Would rather have more understanding than being first.
News organizations should be very transparent about what they know and don't know and why.
Easy to hide behind law enforcement sources.
Team of social media natives. We are guests in the communities we cover.
Niketa Patel: uses dataminr in tweetdeck.
Jenkins: Use a lot of Chrome extensions - everything in Chrome. Tweetdeck.
Carvin: Have a package of Chrome extensions. Most important tool are our followers. They are an army of human sensors. May seem strange to rely on the public, but they are often the switches that trip first.
Reportedly's Twitter lists are public.
Boils down to cultivating relationships with sources. That is not going away even if the person is not standing in front of you.
Can be as simple as following someone's @-replies. Using observational skills about how a conversation is playing out.
Some people don't want to talk to journalists, others very eager to get the word out.
A lot more noise, but people are also getting more news literate - don't see the same fake photo circulate as much as it used to. Still happens of course.
Q: Open vs closed networks. Twitter vs WhatsApp/weechat/firechat/waybo?
Jenkins: Very used to open networks. Hard to get into, but people share more in networks where they trust each other. Photos passed around among friends, hard to track down original source.
Carvin: No discovery tools for the closed networks. Private space for a reason.
A whole new cultivation skill to talk your way into closed groups on WhatsApp.
Fake photos can be geotagged in other locations. Content passed from network and network can be scrubbed on the way. Metadata can be misleading. It's a starting point for verification but not enough.
People don't want to talk to journalists after tragic events. Need to build relationships over time.
Jenkins: Trauma. Difficult to deal with disturbing photos and videos. Young staff, need to create a space where journalists can feel safe and react.
Carvin: Spent Arab Spring mining social media. Scared by sources Twitter feeds going silent.
Important to recognize each other's triggers. Stop and talk through what we just saw. Take breaks and reflect, make us better journalists and better human beings. The possibility of being haunted by stuff you've seen for life.
Seeing staff work harder is a sign of people going into trauma. Especially important with remote staff.
Q: Verification process. PR people.
Carvin: Bad sign when PR people pop up in a conversation. Usually means things are a lot worse than we initially thought.
Avoid intermediaries. Get to eyewitnesses as soon as possible.
Q: refugee crisis.
Carvin: Lot of cellphones. To keep their families alive. Incredible networks of refugees who coordinate and help people behind them. Kingsley from Guardian doing incredible reporting following people on the road.
Q: Licensing companies swoop in and grab photos. People asking compensation.
Jenkins: My company does video licensing. Others do more viral videos. Many people are going after news videos for exclusive licensing. Â Sources deserve credit and compensation.
Carvin: Not dealing with this, looking at people who share information in the open. Not a good use of our time. Happy to wait for AP/Getty.
Patel: trustworthiness depend on sources being credited.
Q: Israel. Not a problem to get people to talk.
Carvin: our densest collection has to do with the Middle East. Palestine moving into private networks / WhatsApp. Strong motivations on both sides.
Jenkins: Both sides have an agenda. People posting old images.
Q: process for corrections, would you delete a tweet.
Carvin: Full transparency when we're wrong and about how we do things. Only deleted a tweet once. Virginia shooter. Played into the killers hands. Won't share something that plays into the propaganda of the source.
Droidcon 2015
ONA15: Fact-Checking 101
Session: http://ona15.journalists.org/sessions/factchecking/#.VgWwnyAqfOE
#ona15factcheck
3-i-1 presentasjon fra forskjellige faktasjekkere med tips om hvordan de jobber mot valget i 2016.Â
6 reasons what you're doing isn't fact-checking
Linda Qiu - Staff Writer, PolitiFact/Tampa Bay Times
@ylindaqiu | http://www.politifact.com
1. You report on what is being said. Fact-checkers report on the accuracy of what is being said.
2. You break news, grind out headlines. Fact-checkers aren't restricted to that 24-hour cycle.
3. You tell a story about an event. Fact-checkers focus on a specific claim in that event (e.g. debates).
4. You protect your sources. Fact-checkers give theirs up. Point readers to primary sources.
5. You "tell the story from all sides.". Fact-checkers don't need that "contrary voice".
6. You work for the big scoops. Fact-checkers deliver bite-sized vetting. Politifact checks typically 3-5 claims per day. Debate nights much higher. 20-30 reporters. Popular posts on Facebook give 1.5 - 2 million likes. Big twitter presence during debate nights. Experimenting with Scribble Live.
6 Political Fact-Checking Resources (That You Probably Don't Know About)
D'Angelo Gore - Staff Writer, FactCheck.org
@DAngeloGore | http://www.factcheck.org/
1. Refdesk.com
2. NCSL 50-state searchable Bill Databases
3. TreasuryDirect's Debt to the Penny
4. The American Presidency Project
5. The Federation of American Scientists6. Money in State Politics: followthemoney.org
7 Ways to Screw Up Fact-Checking
Lisa Halverstadt - Staff Writer, Voice of San Diego
@LisaHalverstadt | http://www.voiceofsandiego.org
1. Wait until you're on deadline to call the people you're fact-checking. Or don't call them at all.
2. Consider every statement fact-checkable.
3. Promise your bosses a dozen fact checks a week.
4. Make up your fact-check ratings as you go.
5. Leave it to one person to decide what should be fat-checked and the rating.
6. Fact-check those politicos making crazy claims all the time and neglect their opponents.
7. Let the haterade get you down.
https://www.facebook.com/Flatchecker - videofaktasjekker
-- Jari
ONA15: Moving The Needle
Sesjon: http://ona15.journalists.org/sessions/measuringimpact/
Praktiske tips: http://bit.ly/ona15-impact-tips#ona15impact
To forskere som har sett pÄ bruk av mÄlinger/metrikker i nyhetsrommet presenterte sine hovedfunn.
Rapport #1: The Traffic Factories av Caitlin Petre.
Caitlin la merke til at det var en levende debatt rundt hva slags tall redaksjoner burde bry seg om, men kunne ikke finne noe grundig forskning pĂ„ omrĂ„det. Mye av debatten handlet frykt for hvordan tall vil pĂ„virke redaksjonen â vil dette fĂžre til mer Bieber og mindre Syria? FĂ„ har sett grundig pĂ„ hva som faktisk har skjedd.
Caitlin har hovedsakelig sett pÄ hvordan trafikktall, dashboards og mÄlinger pÄvirker redaksjonelt ansatte. Har fokusert pÄ trafikktall fra Chartbeat hos Gawker og New York Times, og hvordan data forstÄs og brukes i nyhetsrommet i disse organisasjonene. Spesielt Gawker har en veldig datadrevet kultur med mye dashboards og tall synlige i nyhetsrommet.
Funn:
1. Metrics engender strong emotions.
Det snakkes mye om de rasjonelle fordelene med Ä ha tall og mÄlinger og innsikten dette gir, men lite om hvordan det pÄvirker folks fÞlelser. Ingen selger nye mÄleverktÞy med at «dette vil ta dine ansatte pÄ en emosjonell berg-og-dalbane», men det er en viktig del av bildet.
2. Metrics can be addictive.
Mange beskriver at de blir avhengige av Ä se de siste tallene pÄ sine artikler. Minner om resultater fra forskning pÄ spillavhengighet, men at du er pÄlagt Ä spille som del av jobben.
3. Metrics intensify internal competition
Gawker gikk fra individuelle til kollektive mÄltall, og mener det fÞrer til et bedre arbeidsmiljÞ alt i alt. De har gjort forsÞk med Ä trekke frem hvem som skaper mest trafikk med sine artikler, men resultatene har vÊrt demoraliserende og stressende for skribentene. Det kan ogsÄ Þdelegge insentivet for Ä samarbeide.
Hovedfunn: Metrics are management tools just as much as they are editorial tools.
Rapport #2: Newslynx. Tool for newsroom impact measurement. Michael Keller and Brian Abelson.
Skrolledybde og andre tall er fint og flott, men hvordan kan vi mÄle om leseren blir opprÞrt, engasjert eller om vi avslÞrte noe viktig?
Har forsket pÄ hvordan nyhetsrom balanserte trafikktall mot andre mÄlinger av «impact». Tok utgangspunkt i smÄ, ideelle gravejournalistikkorganisasjoner, som mÄ kunne vise at de fÄr noe ut av stÞttepenger de fÄr, selv om trafikktallene ikke er all verden.
Kan vi mÄle hvor ofte vi har fÄtt en korrupt maktperson avsatt? Fungerer ikke sÄ bra.
BĂžr lage en kombinasjon av:
1. Blir vi nevnt / sitert av viktige personer? Twitter, Google Alerts, taler i Kongressen. (Erna snakket om Odin pÄ Stortinget.)
2. Lag en taksonomi for «impact». Skapte dekningen en endring i verden? Ble det startet en granskning, hÞring hos myndighetene?
3. Kvantitative mÄlinger. Unike brukere, reach i sosiale medier.
4. Organisasjonens overordnede mÄl.
Har laget verktÞyet Newslynx, et verktÞy som minner om If This Then That / alerts rundt impact-mÄlinger.
Trafikk-tall trenger kontekst. Er N sidevisninger bra eller dÄrlig? Er det bedre enn snittet (eller medianen om én veldig populÊr artikkel vrir distribusjonen). Og ikke minst: Hvorfor gjÞr den det sÄ bra?
-- Jari
ONA15: A Deep Dive into Google
FĂžrste dag ble sparket i gang med en samtale mellom Emily Bell, mangeĂ„rig digitalsjef i Guardian og nĂ„ hos Tow Center for Digital Journalism, og Richard Gingras, sjef for nyheter hos Google med rundt 40 Ă„rs erfaring fra mediebransjen.Â
Gingras mener at teknologi og journalistikk stadig blir tettere sammenvevd, og at nyhetsorganisasjoner i dag mĂ„ vĂŠre like gode pĂ„ teknologi som de har vĂŠrt pĂ„ skriving og rapportering.Â
Google jobber med noe de kaller «the Trust Project», som skal hjelpe folk Ä identifisere journalistisk innhold av hÞy kvalitet, noe som ikke er like lett nÄr blogger og «corporate spin sites» velvillig spres i sosiale medier uten noen klare skillelinjer nÄr det gjelder troverdighet. For dette opererer Google med ulike «trust signals» som deres algoritmer bruker for Ä vurdere troverdigheten pÄ innholdet. Jo flere signaler, jo bedre, men de bÞr vÊre mulige Ä forklare for leserne, mente Gingras.
Bell pĂ„pekte at tross alle mulighetene Google og andre teknologiselskaper skaper for journalister, er ikke journalistikk deres hovedmĂ„l. Hvorfor skal vi stole pĂ„ Googles vurderingsevne nĂ„r det gjelder hvilke aktĂžrer som er troverdige? Google er ikke nĂždvendigvis pĂ„ journalistikkens side nĂ„r deres egne interesser blir gjenstand for kritisk undersĂžkelse fra pressen.Â
Gingras svarte at selv om Trust-prosjektet er finansiert av Google, er det ment Ä vÊre allemannseie. Resultatene av Googles algoritmer er dessuten Äpne for alle Ä undersÞke og kritisere, og de er helt avhengige av brukernes tillit for at forretningen skal fungere.
Han mente ogsÄ at det var opplagt mye Þkonomisk verdi i sÞkemotorer og aggregeringstjenester, og at Ä forsÞke Ä regulere disse Þdelegger «the link economy». Vi trenger et Äpent Þkosystem som stÞtter bÄde smÄ og store publisister.
Bell spurte om veksten i mobilbruk nÄ gjÞr at Apple og Facebook stÄr i fare for Ä Þdelegge «the open web». Gingras svarte at det er en fare, og at Google jobber med et initiativ rundt dette som de vil lansere innen kort tid. Han mente at «the mobile web» stÄr ovenfor en krise. WeblÞsninger gÄr for sakte pÄ mobil, og det gjÞr at folk sÞker seg til proprietÊre plattformer.
Google har vĂŠrt i prat med mange utgivere om hvordan dette problemet kan lĂžses, og mener at lĂžsningen mĂ„ vĂŠre basert pĂ„ Ă„pne standarder og Ă„pen kildekode. Hvordan kan vi gi folk en rask, umiddelbar opplevelse pĂ„ mobil, uten Ă„ mĂ„tte inngĂ„ forretningsavtaler med de som eier plattformene.Â
Uten Ä nevne konkurrentene ved navn var det opplagt at Gingras her har et initativ pÄ trappene som vil gÄ i strupen pÄ Apple News og Facebooks Instant Articles. Lekkasjer tyder pÄ at det er snakk om et samarbeid med Twitter.
Annonseblokkering er bare et symptom pÄ problemet med at ting generelt gÄr for sakte, mener Gingras. Det finnes ikke én enkelt lÞsning, men Googles initativ vil tilnÊrme seg annonsering pÄ en annen mÄte.
Bell spurte om Washington Post nÄ gjÞr ting riktig ved Ä legge alt innholdet sitt pÄ Facebook som instant Articles. Gingras svarte at publisister mÄ bruke alle tilgjengelige plattformer for Ä spre innholdet sitt, og at WPs samarbeid med Facebook derfor er helt riktig ting for dem Ä gjÞre. Men Google Þnsker Ä tilby en enklere modell, hvor aktÞrene ikke trenger Ä vÊre forretningspartnere.
Bell spurte videre om Apple vil klare Ä flytte nyheter fra den Äpne webben til et lukket mobilÞkosystem som de selv kontrollerer. Gringas svarte at det ikke var umulig, men at tilsvaret mÄ vÊre Ä lage rammeverk basert pÄ Äpne standarder og Äpen kildekode, hvor utvikere i nyhetsrommet ikke trenger Ä bruke dyrebar tid pÄ Ä tilpasse innholdet sitt for en rekke proprietÊre plattformer.
-- Jari
ONA15 dag 1
En spennende dag med mange parallele sesjoner er over.
Her er noen notater fra Amy OŽLeary sitt foredrag, som var et av de beste jeg var pÄ i gÄr.
Amy OÂŽLeary jobber i Upworthy, men har blant annet jobbet med innovasjonsrapporten til NyTimes +++
Tittel:Â From Scheherazade to Snapchat: Ancient storytelling practices that win the internet for good
Twitter: #ancientUX Videopresentasjon: http://ona15.journalists.org/sessions/scheherazadetosnapchat/#.VgWMo7Qn__m
Historien om Gilgamesj:Â Bildedrevet historie: Hos Upworthy lager de storyboards med bilder til alle sakene. âThink as images as the backbone of a story. LotÂŽs of images when you scroll. Especially on mobile.â
Iliaden: Hvordan holde pÄ oppmerksomheten til leseren nÄr alle vet hva som har skjedd? Fortell noe mer. Bryt ned alle bitene av historien. Ikke bare fortell hva som skjer, men hvordan og hvorfor.
Fin viral sak (tegneserie): Trying to follow what is going on in Syria and why? This comic will get you there in 5 minutes.
Humma ha og Shakespeare: Bruk humor i seriÞse historier. Se tumbler siden Shakespeare dick jokes.
Saken â5 incredibly delicious chain restaurants you should never, ever eat at and 1 you should but can'tâ er et godt moderne eksempel. Saken er pĂ„ 5000 tegn, inneholder mer enn 75 vitser, men forteller ogsĂ„ historien om segregering, fagforeningstrĂžbbel etc. Den ble selvfĂžlgelig masse delt og lest.
Amy hadde ogsÄ flere eksempler fra blant annet Dantes inferno og gamle myter, og mente vi burde bli mer personlige i nyhetsformidlingen og vise mer empati, blant annet i delinger i Sosiale medier.
Hun hadde ogsÄ laget noen fine postere som oppsummering.
Onsdag 9. september
Onsdag startet som de fleste andre dagene pÄ konferansen, feite stykker med bacon kombinert med black and white pudding og scrambled egg. Begynte Ä bli litt lei av frokosten nÄ.
I âspiegeltentâ ble det fortalt om hvordan man kunne portere eksisterende legacy-systemer over til Node, noe som reflekterte mye av det vi har hĂžrt fĂžr her - steg for steg, bytte ut enkeltstĂ„ende sider ved hjelp av en reverse proxy i forkant ol. Ingen store overraskelser.Â
Todd Moore fra IBM sto pĂ„ scenen like etter og prĂžvde Ă„ dra noe symbolikk mellom âOpen Technologyâ og universet. Her var det veldig mange ord og veldig tette slides uten noe voldsomt med take-aways.
Stephan Bönnemann var ânext man upâ. Han har jobbet en del pĂ„ Hoodie, og stĂ„r ogsĂ„ bak semantic-release. Budskapet hans var at moduler lar deg lage ting raskere, og at problemer rundt versjoner og dependency problems ligger like mye pĂ„ consumers som pĂ„ publishers. âSkriv testerâ, pretty much. Vi var litt enige, og litt uenige samtidig.
Matthew Podwysocki er kul. Han jobber for Microsoft, men snakka om Thali Project, som er dritkult. Det er en platform for Ă„ bygge applikasjon pĂ„ tvers av miljĂžer, herunder Android og iOS, som fokuserer pĂ„ sikkerhet og tilgjengelighet. Det kuleste her var at de har implementert en peer-to-peer teknologi som gjĂžr at du enkelt kan âcrowdsourceâ applikasjonene i miljĂžer der internettilgangen ikke nĂždvendigvis er helt pĂ„ topp. Med bruk at PouchDB kan du lage noen ganske fiffige applikasjoner som potensielt kan ha stor pĂ„virkning i land som har dĂ„rlig nettforbindelse.
Hugh Rawlinson snakket om Node og musikk. Har ikke sÄ mange notater herfra, men vil pÄstÄ at det var vanvittig kult, selv om jeg ikke kan mye om musikkproduksjon osv.
Trevor Norris viste oss masse ting man stort sett ikke bÞr gjÞre med Node. AltsÄ ting man kan fÄ Node til Ä gjÞre, som ikke er helt anbefalt. For Ä si det sÄnn. Ting som live reloading av kode, og eksperimenter med optimalisering av kode som viste seg Ä vÊre en ytterst dum idé. Et av eksperimentene hans landet derimot i node core og har sÞrget for Þkt performance. Kult.
Jeremiah Senkpiel fortalte om forskjellige mĂ„ter man kunne bidra til Node core pĂ„. Alt fra dokumentasjon til issues markert som âeasy fixâ, ol. Noe ikke alle er klar over er for eksempel at mye av koden i Node core er Javascript. Med andre ord trenger man ikke nĂždvendigvis kunne C/C++ for Ă„ bidra.
Mathias Buus pleier alltid Ä imponere. PÄ WebRebels i fjor snakket han om node-modulen hans for torrents, pÄ OneShot Oslo viste han oss et distribuert og versjonert filsystem, og pÄ NodeConf EU denne lystige onsdagen presenterte han en torrent-aktig protokoll som Äpnet for innhold som forandret seg over tid - en stream. I presentasjonen viste han hvordan dette kunne gjÞres med alt slags innhold over flere forskjellige typer streams. Demoen var fÞrst med tekst, og sÄ med en MP3-fil. Han kombinerte sÄ dette med WebRTC og viste hvordan man kunne streame innhold til browseren, og videre til andre klienter. Awesome.
Thorsten Lorenz hadde laget en greie som hjelper folk med Ă„ lĂŠre seg Assembly. Den heter Visulator, og hjelper med Ă„ visualisere hva de forskjellige instruksjonene faktisk gjĂžr.
Contra, mannen bak Gulp, hadde en veldig kreativ og morsom talk. Han irriterer seg stadig over hvor vanskelig det er Ă„ fĂ„ ting gjort i USA. Om man finner et hull i veien, sĂ„ nytter det ikke Ă„ si ifra. Klagen blir bare borte, og man hĂžrer aldri noe tilbake. Han gjorde et eksperiment: Han ga Mechanical Turk en oppgave der man skulle late som man var fra San Francisco og irriterte seg over hvor mye lysforurensing det var i en av parkene. De skulle sitere forskjellige lokale medier og sende individuelle klager over en gitt tidsperiode. Det fungerte. Basert pĂ„ dette lagde han et shellscript for Ă„ automatisere prosessen pĂ„ en spesifikk side - denne relatert til âinfrastructure problemsâ. Talken er veldig mye bedre enn oppsummeringen, og bĂžr sees om den legges ut som video senere.
Yosuke Furukawa, vĂ„r venn fra Japan, har laget âHexagonal Stickers as a Serviceâ. Morsom tjeneste, og gĂžy Ă„ hĂžre om den, selv om talken ikke ga noe nevneverdig verdi rent teknisk.
Worksoppene etter dette handlet om Hapi, som viste seg Ä vÊre workshoppern (nodeschool-sessionen) som Hooverdam allerede hadde vÊrt gjennom. Istedet ble det slÄtt noen golfballer fra driving rangen, og kvelden ble brukt pÄ gala-middag og fest som avslutning pÄ en kul konferanse. Da natten kom krypende var Fossegrimmen for lengst gÄtt til sengs, mens E and E plukket golfballer og slo noen slag pÄ driving rangen i mÞrket. Man spiller alltid best golf i mÞrket.
Tirsdag 8. september
Tirsdag klokka 07:30 nĂžt vi en rolig frokost med utsikt over hagene. Hjorter som beitet, harer som hoppet og konferansedeltakere fra USA, som gikk rundt og sa "Good morning, how y'all doing?". Ah, such bliss!
Dagens fÞrste foredrag var en ganske interessant fortelling om koding av nodemoduler i C++, som selv Fossegrimen klarte Ä fÞlge med pÄ. Mike Tunniclife fra IBM foredro.
Suz Hinton fortalte om hvordan hun har gÄtt fra Ä lage ting til Ä lage ting for Ä hjelpe folk med Ä lage ting. Som hun selv sier: "Many people want to hack chips, not many people want to code C/C++". Hun stÄr som ansvarlig for avrgirl, et prosjekt som er tenkt Ä gjÞre det enklere Ä bruke Node.js til Ä programmere microchips.
Kelsey Breseman dro pÄ med en skildring av hvor vanskelig det er Ä vite hvordan man skal utvikle et Äpent produkt, sÊrlig med tanke pÄ hva man gjÞr nÄr produktet er sluppet. En aldri sÄ liten filosofitime der altsÄ.
Thomas Watson er en artig fyr fra Danmark, som viste hvordan han har hacket Apples Airplay. Han presenterte eksempler pÄ hvordan han klarte Ä late som om EDB-maskinen hans var en Airplay-enhet, slik at vi kunne laste bilder opp pÄ maskinen hans (og mye mer). Fiffig.
En slÞy amerikaner fra IBM fortalte oss om sine erfaringer med Ä lage et alarmsystem for hytta si ved bruk av Node.js, Arduino og diverse smÄdeler til en totalverdi pÄ $100. Det synes jaffal Fossegrimen var gÞy Ä se pÄ.
Med italiensk bravur og dramaturgi, stĂžttet av minst fire doble espresso, viste Luka Maraschi oss hvordan han feilsĂžkte i nattens mulm, etter at produksjonssiten hans gikk ned klokka 3 om morgenen. Han var flink til Ă„ fortelle. Det er J Edgar enig i.
Neshornet mÄtte holde senga. Ingen bilder :(
Mandag sto vi opp klokka 07:45 og spiste en god irsk frokost pÄ slottet.
Tekniske problemer preget resten av dagen; flaky wifi og generelle problemer med A/V-utstyret resulterte i at flere foredrag ble utsatt. Alle konferansedeltakerne fikk gratis Ăžl.
Etter lĂžnsj var det workshops. De var stappfulle.
Mer grillfest, mer Þl. Hyggelige mennesker fra et telekomselskap i Irland fyrte opp Neshornet i en diskusjon om hvorvidt Node.js egner seg til hÄndtering av prising av telefonsamtaler (pre-paid cards), hvor responstid vanligvis skal ligge pÄ <50ms pr samtale. Neshornet var ikke overbevist om at Node.js' event loop var den best egnete kandidaten til jobben.
Deretter whiskysmaking. SĂ„ senga.
Vi ruslet ned i en av slottets mange hager og prÞvde oss pÄ litt falkejakt. NÊrkontakt med en falk kan anbefales, bare spÞr Edgar.
ArrangÞren hadde ogsÄ satt opp et stort telt fra 1923 ("Spiegeltent") i hagen, hvor samtlige foredrag skulle finne sted. Et fint telt, som visstnok blir satt opp uten bruk av verktÞy.
Grillfest, med to helstekte griser og Ăžl. Nam!
Edgar fant noen venner fra yld ("yield") han hadde blitt kjent med pÄ lxjs. Neshornet og Fossegrimen gikk og la seg.
J Edgar og Fossegrimen nÞt to slÞve dager i Dublin fÞr Neshornet kom og Þdela alt sammen: "NÄ mÄ vi dra. Er det greit at jeg tar bilder av dere? Hele tiden."
Etter en to timers kjÞretur pÄ feil side av veien, hvor Edgar kun hadde to-tre tillÞp til panikk og hysteriske utrop, kom vi fram til fergeleiet ved Waterford Castle. En kort fergetur senere var vi trygt innlosjert i rene og moderne rom.
www.newsup.me - Play the news.
"In order to make the right move you need to make a lot of moves."
stan_chudnovsky #pandoland2015
Paul Carr & Mike Ottaro. Weird music Thingy Founded on Kickstarter.