Vaidehijoshi.github.io Website Review

a year ago, i had this idea: i was going to write things down. to be clear, this wasn’t a novel idea, and definitely not a new one by any stretch of the imagination. but it was something i wasn’t exactly in the habit of doing, and the first day of a new year seemed like the so, i decided to start writing down all the things i didn’t know, and make an effort to learn them. i honestly didn’t know what i was going to be writing, and i didn’t know if any of it would be well-written, much less worth reading. all i was sure of was that i was going commit to doing it wholeheartedly, just once a week — not for anyone else specifically, but really just for myself. thus began a year-long adventure of researching, writing, and sharing all the things i would discover in my first year as a software engineer in my today brings me to the end of the road on this journey of technical tuesday blog posts. and just like the first day of a new year, the last day of a soon-to-be-gone year is a seemingly perfect time to do some reflecting on a year of tuesdays. i crossed over to the dark side awhile ago, and i can hide it no longer. and when i say “the dark side”, what i mean is ja*ascript. surprise, surprise — i am now haunted by semicolons everywhere i go! i’ve been working a lot with ember and a little bit with react over the past six months, and have both struggled and enjoyed integrating these frameworks with a rails api. at first, coming back to rails after a week or so of ember was just like coming home: warm, comforting, and familiar. yet the wild west of braces and semicolons called out to me. the more that i worked outside of rails, the more comfortable i became with more functional programming concepts (read: concepts that are abstracted away such that you don’t ever have to think about them in the rails framework). after awhile, i noticed that coming back to rails was less like coming back to something familiar, but instead something that often seemed limiting and constricting in