Categories
Personal

Position Statement for the 2022 W3C TAG Election

Reading Time: 3 minutes

Update: I got re-elected!! Thank you for trusting me once more with this huge responsibility towards the Open Web. I will continue to do my best to justify the confidence the W3C membership has placed in me. šŸ„¹

Context:Ā In 2020, I ran for the TAG election for the first time and had the great honor of being elected by the W3C membership. This year, Iā€™m running for re-election. The W3C Technical Architecture Group (TAG) is the Working Group that ensures that Web Platform technologies are usable and follow consistent design principles, whether they are created inside or outside W3C. It advocates for the needs of everyone who uses the Web and everyone who works on the Web. If you work for a company that is aĀ W3C Member, please consider encouraging your AC rep to vote for me! My candidate statement follows.

Iā€™m Lea, and I’m running for re-election to the TAG to continue applying my usability research, CSS WG, and TAG experience to help W3C stay connected to the developer community, and to better serve their needs by ensuring web platform features are not only powerful, but also learnable and approachable, with a smooth ease-of-use to complexity curve.

I wear many hats. My background spans almost two decades of web design & development experience, one decade of standards work in the CSS WG, nearly a decade of PhD level human-computer interaction research & teaching at MIT, and over a decade of educating web developers through talks, books, articles, and helping them through my dozens of open source projects, some of which are used on millions of websites. For those unfamiliar with my background, I encourage taking a look at my 2020 candidate statement.

In 2020, I had the great honor of being elected to serve on the TAG by the W3C membership. In the two years I have served on the TAG, I participated in over 70 design reviews and helped prioritize API design in our reviewing. I have been publicly praised for the quality of design reviews I led. 

It is important that the TAG does not operate in a vacuum:  The primary purpose of our work is to serve developers and end-users by ensuring web platform features are usable, secure and privacy preserving. I have used my experience during design reviews to make sure we remain connected to this mission.

Together with Sangwhan Moon, I took the lead on our Web Platform Design Principles effort, which documents the principles that underlie Web Platform features ā€” previously only existing in WG lore. The Web Platform is going through an explosion of new features; only in the last year the TAG received almost a hundred design review requests. With this volume, it is important that reviews are consistent, transparent, and fast. Evolving our published design principles helps with all three goals.

The Web ecosystem is not just the Web Platform itself, but also the various tools and libraries out there. I started a project to publish a subset of the design principles that apply to web developers, to help them in creating Web Platform compatible APIs. After all, with web components, web developers are now HTML designers, with Houdini APIs, they are now CSS designers, and with JS, they’ve been JS API designers since forever. The project is currently in its infancy, and If elected, it will be one of my tasks to get it published within my next term.

As a Greek woman, I bring both a Mediterranean and European perspective that diversifies the TAG and as a fully bilingual Greek and English speaker, I can fully participate in rapid technical discussions while also having an appreciation of the Internationalization needs of those who use the Web in languages other than English.

To ensure my participation has been beneficial for the TAG, I reached out to the chairs for feedback before deciding to run again. Both were very positive and strongly encouraged me to run again.

As someone not employed at a big tech company, I am not influenced by any particular company line. My only agenda is to lead the Web Platform to its full potential, and if re-elected, Iā€™m willing to commit to spending the requisite hundreds of hours working towards that goal over the next two years. This was just the beginning, there is so much more important work to be done!

I would like to thank Open JS Foundation for graciously funding my TAG-related travel, in the event that I am re-elected, and both OpenJS Foundation and Bocoup for funding it during my first term.

Categories
Releases Speaking

Introducing Rety: live coding, without the stress

Reading Time: 3 minutes

I recently spoke at CSS Day in Amsterdam. It was only my second f2f talk after the pandemic. It went down really well, both in person, and recently that the video was released:

Here is a sample of tweets about it that made me particularly warm and fuzzy inside:

There’s a lot more where these came from too.

This was not just my second post-pandemic talk, but my first talk using Rety, which is what this post is about.

As you may know, I love live coding as a teaching tool, and over the years it has become part of my trademark speaking style.

When combined with some kind of interactive preview, it allows the speaker to demonstrate not only the final state of a coding snippet, but also how you get there, and what the intermediate results are. Live coding is to programming what a blackboard is to math or physics.

But it does create a unique challenge: My live coded slides donā€™t make sense without me. This may be acceptable for a conference talk, which is usually recorded, but not in other contexts, such as teaching a university course, where all instructors need to be able to teach all lectures, and students need to be able to quickly refer to examples shown.

Back in the fall of 2021, when we were preparing for the second iteration of our course, Design for the Web: Languages and User Interfaces, this came up as a pressing issue. The current state of the course required me to be there to teach my lectures, and this may well be the last year I teach it, since I’m finishing up my PhD soon.

I didnā€™t want to completely remove live coding from my slides, as I truly believe it is the perfect implementation of the ā€œshow, donā€™t tellā€ teaching adage for certain things, so I thought instead: what if I could record my live coding, and make it replayable?

Doing so manually seemed like cruel and unusual punishment. And thus, Rety was born (pronounced like the ā€œretyā€ in ā€œretypeā€).

While originally the plan was for me to still live code, and have the Rety functionality there for students and future instructors, I ended up using it during my own lectures as well, as I concluded that a well crafted Rety script was strictly superior to me doing the live coding:

  • Same progressive development as a live demo
  • It still affords unplanned demonstrations (e.g. to answer a question), since Rety still works with the same editors, and I could always pause it and take over if needed.
  • I could record myself and edit the script to maximize education value and minimize typos, delays, fumbling etc.
  • People can consume typed text far faster than people can type text. This is why most video tutorials speed up the typing. With Rety, typing speed is adjustable, and doesn’t need to match mine.

After test driving it for our course the entire spring 2022 semester, it went through the ultimate test in June 2022: I used it for my CSSDay conference talk. You can watch the talk here (first live demo at 7:15).

Right now Rety is just a set of two classes: Recorder and Replayer, which are used entirely independently. The exact UI is left up to the Rety user. E.g. to use it in my slides, I integrated it with the Live Demo plugin of Inspire.js (it is automatically included if a <script class="demo-script" type="application/json"> is found in a live demo slide).

The library could use more docs and some tests and I have doubts about the API, but I figured I should release it it earlier rather than later (it’s already been sitting in a repo for 7 months). After all, what best time to release it than when the first Rety talk is still making the rounds?

My vision is to ultimately evolve and standardize the Rety script format, so that it can be used to describe a coding interaction across a variety of tools. There are so many possibilities!

  • Wouldn’t it be cool if CodePen and similar playgrounds supported embedding a Rety script into a pen?
  • What if you could store Rety scripts in a repo and editors like VS Code recognized them and let you replay them?

Enjoy: Rety

Categories
Original Personal Releases

On Yak Shaving and <md-block>, a new HTML element for Markdown

Reading Time: 2 minutes

This week has been Yak Shaving Galore. It went a bit like this:

  1. I’ve been working on a web component that I need for the project Iā€™m working on. More on that later, but letā€™s call it <x-foo> for now.
  2. Of course that needs to be developed as a separate reusable library and released as a separate open source project. No, this is not the titular component, this was only level 1 of my multi-level yak shavingā€¦ šŸ¤¦šŸ½ā€ā™€ļø
  3. I wanted to showcase various usage examples of that component in its page, so I made another component for these demos: <x-foo-live>. This demo component would have markup with editable parts on one side and the live rendering on the other side.
  4. I wanted the editable parts to autosize as you type. Hey, Iā€™ve written a library for that in the past, itā€™s called Stretchy!
  5. But Stretchy was not written in ESM, nor did it support Shadow DOM. I must rewrite Stretchy in ESM and support Shadow DOM first! Surely it wonā€™t take more than a half hour, itā€™s a tiny library.
  6. (It took more than a half hour)
  7. Ok, now I have a nice lil’ module, but I also need to export IIFE as well, so that it’s compatible with Stretchy v1. Let’s switch to Rollup and npm scripts and ditch Gulp.
  8. Oh look, Stretchyā€™s CSS is still written in Sass, even though it doesnā€™t really need it now. Letā€™s rewrite it to use CSS variables, use PostCSS for nesting, and use conic-gradient() instead of inline SVG data URIs.
  9. Ok, Stretchy v2 is ready, now I need to update its docs. Oooh, it doesnā€™t have a README? I should add one. But I donā€™t want to duplicate content between the page and the README. Hmmm, if onlyā€¦
  10. I know! Iā€™ll make a web component for rendering both inline and remote Markdown! I have an unfinished one lying around somewhere, surely it wonā€™t take more than a couple hours to finish it?
  11. (It took almost a day, two with docs, demos etc)
  12. Done! Here it is! https://md-block.verou.me
  13. Great! Now I can update Stretchyā€™s docs and release its v2
  14. Great! Now I can use Stretchy in my <x-foo-live> component demoing my <x-foo> component and be back to only one level of yak shaving!
  15. Wow, itā€™s already Friday afternoon?! šŸ¤¦šŸ½ā€ā™€ļøšŸ˜‚

Hopefully you find <md-block> useful! Enjoy!

Categories
Personal

Position Statement for the 2020 W3C TAG Election

Reading Time: 5 minutes

Update: I got elected!! Thank you so much to every W3C member organization who voted for me. šŸ™šŸ¼ Now on to making the Web better, alongside fellow TAG members!

Context: Iā€™m running for one of the four open seats in this year’s W3C TAG election. The W3C Technical Architecture Group (TAG) is the Working Group that ensures that Web Platform technologies are usable and follow consistent design principles, whether they are created inside or outside W3C. It advocates for the needs of everyone who uses the Web and everyone who works on the Web. If you work for a company that is a W3C Member, please consider encouraging your AC rep to vote for me! My candidate statement follows.

Categories
News Personal

New decade, new theme

Reading Time: 2 minutes

It has been almost a decade since this blog last saw a redesign.

This blog’s theme 2011 – 2020. RIP!

In these 9 years, my life changed dramatically. I joined and left W3C, joined the CSS WG, went to MIT for a PhD, published a book, got married, had a baby, among other things. I designed dozens of websites for dozens of projects, but this theme remained constant, with probably a hasty tweak here and there but nothing more than that. Even its mobile version was a few quick media queries to make it palatable on mobile.

Categories
Personal

Never forget type=”button” on generated buttons!

Reading Time: 2 minutes I just dealt with one of the weirdest bugs and thought you may find it amusing too.

In one of my slides for my upcoming talk “Even More CSS Secrets”, I had a Mavo app on a <form>, and the app included a collection to quickly create a UI to manage pairs of values for something I wanted to calculate in one of my live demos. A Mavo collection is a repeatable HTML element with affordances to add items, delete items, move items etc. Many of these affordances are implemented via <button> elements generated by Mavo.

Normally, hitting Enter inside a text field within a collection adds a new item, as one would expect. However, I noticed that when I hit Enter inside any item, not only no item was added, but an item was being deleted, with the usual “Item deleted [Undo]” UI and everything!

At first I thought it was a bug with the part of Mavo code that adds items on Enter and deletes empty items on backspace, so I commented that out. Nope, still happening. I was already very puzzled, since I couldn’t remember any other part of the codebase that deletes items in response to keyboard events.

So, I added breakpoints on the delete(item) method of Mavo.Collection to inspect the call stack and see how execution got there. Turned out, it got there via a normal …click event on the actual delete button! What fresh hell was this? I never clicked any delete button!

And then it dawned on me: <button> elements with no type attribute set are submit buttons by default! Quote from spec: The missing value default and invalid value default are the Submit Button state.. This makes no difference in most cases, UNLESS you’re inside a form. The delete button of the first item had been turned into the de facto default submit button just because it was the first button in that form and it had no type!

I also remembered that regardless of how you submit a form (e.g. by hitting Enter on a single-line text field) itĀ also fires a click event on the default submit button, because people often listen to that instead of the form’s submit event.Ā Ironically, I was cancelling the form’s submit event in my code, but it still generated that fake click event, making it even harder to track down as no form submission was actually happening.

The solution was of course to go through every part of the Mavo code that generates buttons and add type=”button” to them. I would recommend this to everyone who is writing libraries that will operate in unfamiliar HTML code. Most of the time a type-less <button> will work just fine, but when it doesn’t, things get really weird.

Categories
Personal

My positive experience as a woman in tech

Reading Time: 5 minutesWomen speaking up about the sexism they have experienced in tech is greatĀ for raising awareness about the issues. However, when no positive stories get out, the overall picture painted is bleak, which could scare even more women away.

Lucky for me, I fell in love with programming a decadeĀ before I even heard there is a sexism problem in tech. Had I read about it before, I might have decided to go for some other profession.Ā Who wantsĀ to be fighting an uphill battle all herĀ life?

Thankfully, my experience has been quite different. Being in this industry has brought me nothing but happiness. Yes, there are several women who have had terrible experiences, and Iā€™m in no way discounting them. They may even be the majority, though I am not aware of any statistics. However, there is also the other side. Those of us who have had incredibly positive experiences, and have always been treated with nothing but respect. That sideā€™s stories need to be heard too, not silenced out of fear that we will become complacent and stop trying for more equality. Stories like mine should become the norm, not the exception.

Iā€™ve had a number of different roles in tech over the course of my life. Iā€™ve been a student, a speaker & author, Iā€™ve worked at W3C, Iā€™ve started & maintain several successful open source projects and Iā€™m currently dabbling in Computer Science research. In none of these roles did I ever feel I was unfairly treated due to my gender. That is not because Iā€™m oblivious to sexism.Ā I tend to be very sensitive to seeing it, and I often notice even the smallest acts of sexism (ā€œdeath by a thousand paper cutsā€). I see a lot of sexism in societyĀ overall. However, inside this industry, my gender never seemed to matter much, except perhaps in positive ways.

On my open source repos, I have several contributors, the overwhelming majority of which, is male. Iā€™ve never felt less respected due to my gender. Iā€™ve never felt that my work was taken less seriously than male OSS developers. Iā€™ve never felt my contributors would not listen to me. Iā€™ve never felt my work was unfairly scrutinized. Even when I didnā€™t know something, or introduced a horrible bug, Iā€™ve never been insulted or berated. The community has been nothing but friendly, helpful and respectful. If anything, Iā€™ve sometimes wondered if my gender is the reason I hardly ever get any shit!

On stage, Iā€™ve never gotten any negative reactions. My talks always get excellent reviews, which have nothing to do with me being female. There is sometimes the odd complimentary tweet about my looks, but thatā€™s not onlyĀ exceedinglyĀ rare, but also always combined with a compliment about the actual talk content. My gender only affected my internal motivation: I often felt I hadĀ to be good, otherwise I would be painting all female tech speakers in a negative light. But other people are not at fault for my own stereotype threat.

My book, CSS Secrets, has been as successful as an advanced CSS book could possibly aspire to be and got to an average of 5Ā stars on Amazon only a few months after its release. Itā€™s steadily the 5th bestseller on CSS and was No 1 for a while shortly after publication. My gender did not seem to negatively affect any of that, even though thereā€™s a picture of me in the french flap so there are no doubts about me being female (as if the name Lea wasnā€™t enough of a hint).

As a student, Iā€™ve never felt unfairly treated due to my gender by any of my professors, even the ones in Greece, a country that is not particularly famous for its gender equal society, to put it mildly.

As a new researcher, I have no experience with publishing papers yet, so I cannot share anyĀ experiences on that. However, Iā€™ve been treated with nothing but respect by both my advisor and colleagues. My opinion is always heard and valued and even when people donā€™t agree, I can debate it as long and as intensely as I want, without being seen as aggressive or ā€œbossyā€.

Iā€™ve worked at W3C and still participate as an Invited Expert in the CSS Working Group. In neither of these roles did my gender seem to matter in any way. Iā€™ve always felt that my expertise and skillset were valued and my opinions heard. In fact, the most well-respected member of the CSS WG, is the only other woman in it: fantasai.

Lastly, In all my years as a working professional, Iā€™ve always negotiated any kind of remuneration, oftenĀ hard. Iā€™ve never lost an opportunity because of it, or been treated with negativity afterwards.

On the flip side, sexism today is rarely overt. Given that hardly anybody over ten will flat out admit they think women are inferior (even to themselves), itā€™s often hard to tell when a certain behavior stems from sexist beliefs. If someone is a douchebagĀ to you, are they doing it because youā€™re a woman, or because theyā€™re douchebags? If someone is criticizing your work, are they doing it because they genuinely foundĀ something to criticize or because theyā€™re negatively predisposed due to your gender? Itā€™s impossible to know, especially since they donā€™t know either! If you confront them on their sexism, they will deny all of it, and truly believe it. It takes a lot of introspection to see oneā€™s internalized stereotypes. Therefore, a lot of the time, you cannot be sure if you have experienced sexist behavior, and there is no way to find out for sure, since the perpetrator doesnā€™t know either. There are many false positives and false negatives there.

Perhaps I donā€™t feel I have experienced much sexism because I prefer to err on the side of false negatives.Ā Paraphrasing Blackstone, I would rather not call out sexist behavior ten times, than wrongly accuse someone of it once. It might also have to do with my personality: Iā€™m generally confident and can be very assertive. When somebody is being a jerk to me, I will not curl in a ball and question my life choices, I will reply to them in the same tone. However, those two alone cannot make the difference between a pitĀ rampant withĀ sexism and anĀ egalitarian paradise. I think a lot of it is that we have genuinelyĀ made progress, and we should celebrate itĀ with more women coming out with their positive experiences (it cannot just be me, right?).

Ironically, one of the very few times I have experienced any sexism in the industry was when a dude was trying to be nice to me. I was in a speaker room at a conference in Las Vegas, frantically working on my slides, not participating in any of the conversations around me. At some point, one of the guys said ā€œfuckā€ in a conversation, then turned and apologized to me. Irritated about the sudden interruption, I lifted my head and looked around. I noticed for the first time that day that I was the only woman in the room. His effort to be courteous made me feel that I was different, the odd one out, the one we must be careful around and treat like a fragile flower. To this day, I regret being too startled to reply ā€œEh, I donā€™t give a fuckā€.

Categories
Original Personal Releases

Introducing Bliss: A 3KB library for happier Vanilla JS

Reading Time: 4 minutesScreen Shot 2015-12-04 at 16.59.39Anyone who follows this blog, my twitter, or my work probably is aware that Iā€™m not a huge fan of big libraries. IĀ think wrapper objects are messy, and big libraries are overkill forĀ smaller projects. On large projects, one uses frameworks like React or Angular anyway, not libraries.

Anyone who writes Vanilla JS on a daily basis probably is aware that itĀ can sometimes be, ahem, somewhat unpleasant to work with. Sure, the situation is orders of magnitude better than it was when I started. Back then, IE6 was the dominant browser and you needed a helper function to even add event listeners to an element (remember element.attachEvent?) or to get elements by a class!

jasset-datepicker

Fun fact: I learned JavaScript back then by writing my own library, called jAsset. I had not heard of jQuery when I started it in 2007, so I had even coded my own selector engine! (Anyone remember slickspeed?) jAsssetĀ had plenty of nice helper functions, its own UI library and a cool logo. I had even started to make a website for its UI components, seen on the right.

Sadly, jAssetĀ died the sad inevitable death of all unreleased projects: Without external feedback, I had nobody to hold me back from adding to its API every time I personally needed a helper function. And adding, and adding, and addingā€¦ Until it became 5000+ loc long andĀ its benefit of being lightweight or comprehensible had completely vanished. It collapsed under its own weight before it even saw the light of day. IĀ abandoned it and went through a few years of using jQuery as my preferred helper library. Eventually, my distaste for wrapper objects,Ā the constantlyĀ improving browser support for new APIs that made Vanilla JS more palatable, and the declineĀ of overly conspicuous browser bugs led me to give it up.

It was refreshing, and educational, but soon IĀ came to realize that while Vanilla JS is orders of magnitude better than it was when I started, certain APIs are still quite unwieldy, which can be annoying if you use them often. For example, the Vanilla JS for creating anĀ element, with other elements inside it, events and inline stylesĀ is so commonly needed, but also so verbose andĀ WET,Ā itĀ can make oneĀ suicidal.

However, Vanilla JS does not mean ā€œuse no abstractionsā€. Programming is all about abstractions! The Vanilla JS movement, is about favoring speed, smaller abstractions and understanding of the Web Platform,Ā over big librariesĀ that we treat as a black box. Itā€™s aboutĀ using libraries to save time, not toĀ skip learning.

So, I used my own tiny helpers, on every project. They were small and easy to understand, instead of several KB of code aiming to fix browser bugs I will likely never encounter and let me create complex nested DOM structures with a single JSON-like object. Over time, their API solidified and improved. On larger projects it was a separate file which I had tentatively codenamed Utopia (due to the lack of browser bug fixes and optimistic use of modern APIs). On smaller ones just a few helper methods (I could not live without at least my tiny 2 slocĀ $() and $$() helpers!). Here is a sample from my open source repos:

Notice any recurring themes there? šŸ™‚

I never mentioned Utopia.js anywhere, besides silently including it in my projects, so it went largely unnoticed. Sometimes people would look at it, ask me to release it, Iā€™d promise them I would and then nothing. A few years ago, someone noticed it, liked it andĀ documented itĀ a bit (site is down now it seems). However, it was largely my little secret, hidden in public view.

For the past half year, Iā€™ve been workingĀ hardĀ on my research project at MIT. Itā€™s pretty awesome and is aimed at helping people who know HTML/ CSS but not JS, achieve more with Web technologies (and thatā€™s all I can say for now). Itā€™s also written in JS, so I used Utopia as a helper library, naturally. Utopia evolved even more with this project, got renamed to Bliss and got chainability via my idea about extending DOM prototypes without collisionsĀ (can be disabled and the property name is customizable).

All this worked fine while I was the only person working on the project. Thankfully, I might get some help soon, and it mightĀ be rather inexperienced (the academia equivalent ofĀ interns). Help is veryĀ welcome, but it did raiseĀ the question: How will these people, who likely only know jQuery, work on the project? [1]

The answer was that the time has come to polish, document and release Bliss to the world. My plan was to spend a weekend documenting it, but it ended up being a little over a week on and off, when procrastinating from other tasks I had to do. However, Iā€™m very proud of the resulting docs, so much that I gifted myself a domain for it. They are fairly extensive (though some functions still need work) and hasĀ two thingsĀ I always missed in other API docs:

  • Recommendations about what Vanilla JS to use instead whenĀ appropriate, instead of guiding people into using library methods evenĀ when Vanilla JS would have beenĀ perfectly sufficient.
  • A ā€œShow Implementationā€ button showing theĀ implementation, so you can both learn, and judge whether itā€™s needed or not, instead of assuming that youĀ should use it over Vanilla JS because it has magic pixie dust. This way, the docs also serve as a source viewer!

So, enjoy Bliss. The helper library for people who donā€™t like helper libraries. šŸ™‚Ā In a way, it feels thatĀ aĀ journey of 8 years, finally ends today. I hope the resultĀ makes you blissful too.

blissfuljs.com

Oh, and donā€™t forget to follow @blissfuljsĀ on twitter!

[1]: Academia is often a littleĀ behind tech-wise, so everyone uses jQuery here ā€” hardly anyĀ exceptions. Even though browser support doesnā€™t usually even matter to research projects!

Categories
Original Personal

Spot the unsubscribe (link)!

Reading Time: < 1 minute

Screen Shot 2015-07-28 at 19.39.34After getting fed up with too many ā€œpromotionalā€ emails and newsletters with incredibly obscure unsubscribe links, I decided to make this tumblr to point out such examples of digital douchebaggery. This annoying dark pattern is so widespread that Google even added a feature to Gmail for making those unsubscribe links obvious!

Unsubscribe links are crucial to promotional emails. They are not just another menu item. They are not something that should be hidden in a blurb of tiny low contrast text. Unsubscribe links should be immediately obvious to anyone looking for them. You want people to be reading your email because theyā€™re interested, not because they canā€˜t find the way out. Otherwise you are the digital equivalent of those annoying door-to-door salesmen who just wonā€™t go away.

ā€” From my introductory post onĀ Spot the unsubscribe!

On the spur of the moment, after yet another email newsletter with a hard to find Unsubscribe link, I decided to quickly put togetherĀ a tumblog about this UX pet peeve of mine, called Spot the Unsubscribe!. In less than an hour, it was ready and had a few posts as well šŸ™‚

Hopefully if this bothers others as well, there will be submissions. Otherwise, new posts will be rather infrequent.

Categories
Personal

Iā€™m going to MIT!!

Reading Time: 2 minutesLast year, I did something crazy, that I’ve been wanting to do since I was little: I applied to MITā€™s PhD program in Electrical Engineering and Computer Science.

One of the letters

It was not only crazy because I have been working for several years already, but also because I only applied to MIT, as I decided I did not want to go to any other university, both for pragmatic and emotional reasons. As any prospective grad student will tell you, applying to only one top university is recipe for failure. I didn’t tell many people, but everyone who knew thought I’d get in ā€” except me. You see, I wasn’t a typical candidate. Sure, I have done lots of things I’m proud of, but I didn’t have an amazing GPA or publications in prestigious academic conferences.

It felt like a very long shot, so you can imagine my excitement when I received the letters of acceptance, about a week ago. I will remember that moment forever. I was watching Breaking Bad, feeling miserable over a breakup that happened only a few hours earlier. About a minute into the episode (s05e09), I saw an email notification titled ā€œYour application to MIT EECSā€. My first thought was that there was some problem with my application. And then I read the first few lines:

Dear Michailia Verou:

If you have not already heard from them, you will shortly receive a letter from the EECS department at MIT, informing you that you have been admitted to the graduate program in Computer Science at MIT next fall. Congratulations!!

WHAAAA? Was it a scam? But then, how did they have all my details? Holy mother of the Flying Spaghetti Monster, I got in!!! Soon thereafter, a letter from CSAIL followed (where I said I wanted to work, specifically in the UID), and then even more letters. I started calling everyone who knew I applied to share the news, though it proved quite hard to form sentences instead of uncontrollably screaming in joy. I was (and am!) so excited about the future, that it completely overshadows any other life problems (at least for the time being).

Of course, my happiness is mixed with sheer terror. I keep worrying that I will be the dumbest person in the room, or that I donā€™t remember as much from my undergrad studies as the others will. Iā€™m even terrified of meeting my future advisor(s) in case getting to know me better makes them wonder why I was accepted. But I try to remind myself about impostor syndrome, and from what I’ve read in forums & blogs, it seems that I’m not alone in having such fears.

I held off blogging about it until I felt I was able to write something coherent, but I canā€™t wait to share my excitement any longer.

To the future!

To real life plot twists!

To MIT!

Boy, Iā€™m thrilled. šŸ˜€