You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2010-02-16-meetup.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,11 +26,9 @@ organizers:
26
26
- ksimpson
27
27
---
28
28
29
-
### Speaker: YOU
29
+
##JavaScript Quiz
30
30
31
-
Yes, that's right, you will be participating, okay, only if you want to, but it is highly encouraged.
32
-
33
-
### Talk: JavaScript Quiz
31
+
**Speaker: YOU.** Yes, that's right, you will be participating, okay, only if you want to, but it is highly encouraged.
34
32
35
33
Recently, Juriy Zaytsev, otherwise known as "kangax" and core developer for Prototype, released a quiz with some rather challenging questions related to some of the unique underpinnings and nuances of the JavaScript language.
Copy file name to clipboardExpand all lines: _posts/2013-06-18-meetup.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,8 +29,6 @@ organizers:
29
29
30
30
It's June. It's getting hot and we all need a little more JavaScript in our lives. Well, enjoy the air conditioned comfort of Austin JS on June 18th with a talk from JavaScript SuperStar Rebecca Murphey.
31
31
32
-
#### Topic: Writing Testable JavaScript
33
-
34
32
It's one thing to write the code you need to write to get something working; it's another thing to write the code you need to write if you want to be able to prove that it works — and that it keeps working as you refactor and add new features. In this talk, we'll look at what it means to write testable JavaScript code.
35
33
36
34
Of course we will followup all of this up with our wildly crowd-pleasing roundtable of JavaScript-related questions. This is an open forum to present topics of discussion in a rapid-fire manner or simply heckle [@slexaxton][9]!
Copy file name to clipboardExpand all lines: _posts/2013-07-16-meetup.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ It's finally over 100 degrees with some consistency. It feels like home again. I
21
21
22
22
Instead of having a traditional speaker, we're going to try a lightning talks meeting. We've discussed it with the a few of you and are excited to here everything you guys have to say. If it goes well, we'd like to have these 1 or 2 times a year, so please give feedback!
23
23
24
-
####How it will work
24
+
## How it will work
25
25
26
26
1. Show up to the meeting with a 5 minute (or so) demo of something that's useful to you in your work as a front-end engineer. This can be software, or patterns, or tools, or frameworks. In the past, just pulling up the website for a tool has been a totally easy way to have something to show without any slides to prep! (We encourage you to think about what you'll say though).
27
27
2. Get up at some point during the meeting and plugin your laptop (we should have a default laptop if you don't need/have one) and give this (very informal) presentation.
Copy file name to clipboardExpand all lines: _posts/2016-04-19-meetup.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,4 +29,4 @@ organizers:
29
29
30
30
It's April, so let's shake off our collective SXSW hangovers 🍻 (or maybe emerge from our SXSW bunkers ☢️) and get together on <x-date>{{ site.categories.meetups[0].when | date_to_xmlschema }}</x-date> for another great AustinJS!
31
31
32
-
We'll be hearing from Anton Astashov about [Elm](http://elm-lang.org), a transpiled-to-JavaScript language which makes sure you’ll never have a runtime error in your app. Almost. He'll cover why it’s cool, what it looks like, it’s pros and (most importantly) cons!
32
+
We'll be hearing from Anton Astashov about [Elm](http://elm-lang.org/), a transpiled-to-JavaScript language which makes sure you’ll never have a runtime error in your app. Almost. He'll cover why it’s cool, what it looks like, it’s pros and (most importantly) cons!
bio: Dave is not committing atrocities like <a href="http://daverupert.com/2016/06/dave-goes-build/#edge">saying nice things about IE</a> and <a href="https://www.godaytrip.com">artisanally hand-crafting locally-owned-and-sourced social networks</a>, he's <a href="http://daverupert.com/2015/04/davegoeswindows/">fighting the good fight against device monoculture</a> and <a href="http://daverupert.com/2016/08/hidden-expectations/#empathy">teaching empathy</a> to our cold digital hearts.
Copy file name to clipboardExpand all lines: _posts/2016-11-15-meetup.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,15 +32,15 @@ Much has been made of Lean Startups, A/B testing and building data driven cultur
32
32
33
33
To address this problem, I’ll share a roadmap to successfully evolving a web analytics pipeline that starts by leveraging third party and open source tools for speed and time to market, but is still robust enough to evolve to owning your own warehouse. For context, I’ll walk through my experiences of introducing A/B testing and building out web analytics integrations at Bazaarvoice, expanding HomeAway’s A/B testing program to nearly 1000 tests a year, and now helping to architect data.world’s analytics pipeline.
34
34
35
-
- Do’s and Don’ts for front-end instrumentation:
36
-
- Do use exception track (Sentry) as well as event tracking
37
-
- Don’t use a general purpose tag manager
38
-
- Do leverage third party tools along the way
39
-
- Do plan to own your analytics stack eventually
40
-
- Don’t give away all your data
41
-
- Don’t believe the ‘one line of JS’ hype/No silver bullet
42
-
- Do provide a way for your business team to experiment with tooling
43
-
- Do be explicit
44
-
- Do keep allocation and bucketing in mind
45
-
- Tracking all the things vs. tracking the important things
46
-
- How our front end tech stack enables all this
35
+
* Do’s and Don’ts for front-end instrumentation:
36
+
* Do use exception track (Sentry) as well as event tracking
37
+
* Don’t use a general purpose tag manager
38
+
* Do leverage third party tools along the way
39
+
* Do plan to own your analytics stack eventually
40
+
* Don’t give away all your data
41
+
* Don’t believe the ‘one line of JS’ hype/No silver bullet
42
+
* Do provide a way for your business team to experiment with tooling
43
+
* Do be explicit
44
+
* Do keep allocation and bucketing in mind
45
+
* Tracking all the things vs. tracking the important things
Copy file name to clipboardExpand all lines: _posts/2017-09-19-meetup.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,6 @@ Source maps, huh, yeah. What are they good for? Absolutely... some things.
29
29
30
30
We have an extra special treat this month thanks to our gracious hosts and good friends at Spredfast: Ben Vinegar is coming all the way from "San Francisco" to tell us everything about how source maps work. Join us Tuesday <x-date>{{ site.categories.meetups[0].when | date_to_xmlschema }}</x-date> for a special Bae Area AustinJS!
31
31
32
-
###Talk summary
32
+
## Talk summary
33
33
34
34
You may already be familiar with source maps. They let you debug your original, unminified, and untranspiled code in the browser. But have you ever wondered how they actually work? Ben will take a deep dive into the source map format to see what’s under the hood, exploring source map generation tools, parsers, and how to manipulate source maps directly for fun and profit.
Copy file name to clipboardExpand all lines: _posts/2017-11-21-meetup.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,6 @@ We've got [Mando Escamilla](http://mando.org) coming this month to **_deploy_**
35
35
36
36
In his own words…
37
37
38
-
###DOCKER! CONTAINERS! KUBERNETES! GAAAAH!
38
+
## DOCKER! CONTAINERS! KUBERNETES! GAAAAH
39
39
40
40
If all that stuff is confusing or intimidating, don’t panic - we’re here to help. We’ll help you develop a mental model of a kubernetes cluster and what it does, then jump into a demo of how you’d build and deploy a simple javascript application inside a kubernetes cluster. Don’t worry - if we were able to figure this out, you can too.
Copy file name to clipboardExpand all lines: _posts/2018-01-16-meetup.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ organizers:
16
16
17
17
Let's kick off the new year with [Bradley Farias](https://github.com/bmeck), who will deliver a meditation on the seven stages of ~~grief~~ standards development:
18
18
19
-
###From Language Design to TC39 (The JS Language Standards Group)
19
+
## From Language Design to TC39 (The JS Language Standards Group)
20
20
21
21
This talk is a reflection on a lot of discussions that come up when talking about language design and what it means to design for a future that is always bigger than the past. Topics from the past present and future such as ASI, ESM, decorators, and private fields are things that are important to get right if we are stuck with them forever. We can use discussion examples of each of these topics to get a better understanding of why it is so difficult to make things "just work". I will discuss ongoing themes of discussion within TC39 and efforts that are changing how TC39 is viewed.
0 commit comments