Angélique Weger

Generally, I do a lot of reading – books, yes, but also blog posts, articles, newsletters, the like.

Back in 2022, I switched from using Goodreads to Storygraph.

One year ago, I started a new job with the Maryland Department of Labor.

On the last day of 2021, I deleted my Facebook and Instagram accounts.

Exactly three years ago, I made my own private copy of Coraline’s lftm and pushed my first commit.

There’s a fair amount of angst about how much there is to learn in web development (and often front-end dev specifically).1 As someone who wrote her first HTML 25 years ago, I get it.

Today is Global Accessibility Awareness Day (GAAD), an opportunity to share and spread knowledge about digital accessibility and inclusion.

In this series, I’ve shared how and why I started working remotely, what has made me a successful remote employee for over a decade, and why I think 2020 was more about working through a pandemic than a great experiment in remote work.

To wrap up this series on remote work, I’m going to focus on the things that improve a remote worker’s life.

Since the middle of 2020, folx have been fretting and opining about worker productivity in articles, in blogs, on Twitter.

I have been working remotely since 2007.

For the last five years, the community at Dev.to has used International Women’s Day as an impetus to share the stories of women who code.

Before sharing some of the details and process I used to migrate this site from Middleman to Eleventy, I think it’s helpful to provide some context behind my choice.

Since my team is currently hiring, how we go about hiring for tech roles is very much on my mind right now.

On January 6, like so many other Americans, I watched a scary and violent thing unfold in our nation’s Capitol.

Last year, in what must have been a pique of new year energy, I started working on both redesigning this blog and investigating what it might take to migrate it from Middleman to Eleventy.

I’ve been thinking a lot about teams and, based on my own lucky experiences, what makes them work well.

With the exception of an original iMac I worked on for a couple years after graduation, my personal computers have always been, well, PCs.

I finally conquered a technical challenge that had been stumping me for awhile.

While this could easily be a commitment to a new year, a reboot for my blog (I know it’s been awhile), first I have to look back, to write something that’s been in my head since September and shares things beyond even 2015.

I wrote previously about how to set up your Windows command prompt to work better and wanted to add to that ways I’ve customized my interface of choice (Cmder FTW) to make my command line more efficient and enjoyable for me to use.

When I started using Git and later learning Ruby, the command line became a place I hung out regularly.

There’s been enough coverage in the last year, that most folx accept tech has a diversity problem.

If you’ve decided Sass is snazzy and want to learn more, I’ve gathered up some links I’ve found useful and hope you do, too.

Using variables for colors is awesome; naming those variables can be…complicated.

Back in the days when I was still intimidated by the command line, the lure of variables convinced me to figure out how to start using Sass in my projects.

True story: I wrote my first lines of Ruby in February and used that wee bit of knowledge that to motivate myself to start this blog using a Ruby-on-Rails-based static site generator (Middleman FTW!)

I don’t follow all the advice I receive via social media and blogs (because, oh, what a surreal life I would lead then!)