Long time no see!! I missed you all so much during this break 😢. The main reason why I’ve been inactive on Instagram was because I was in the UK 🇬🇧 for 2 weeks visiting my boyfriend (@kimo_dev) but break time is over 🙅🏻♀️ and it’s time for me to get back to work 👩🏻💻.
While I was in the UK I got a chance to visit the London Eye 🎡 where you can see a beautiful view of the entire city of London including the Big Ben and the Houses of Parlament 🏛.
I also visited one of London’s most popular attractions which is the London Dungeon ☠️. It recreates various gory and macabre historical events in a gallows humor style. It uses a mixture of live actors, special effects and rides 🎢.
A few other places included Winter Wonderland in Hyde Park ❄️, The Buckingham Palace 🏰, Tower Bridge, London Bridge 🌉 , Piccadilly Circus, Covent Garden, Regent Street, Soho, Oxford Street, Leicester Square, Knightsbridge 🛍, Green Park, Trafalgar Square, Borough Market 🐟🍎, watched the Lion King at Lyceum Theatre and tried Nando’s for the first time 🍗.
I also got the chance to meet the fellow Instagrammers @martinsoft, @herhelloworld and @alice_brunel 🍻.
I finished my semester at college and I’m currently on vacation until mid January. I only have one semester left to graduate college 👩🏻🎓. Most likely after graduation I will take a break from school 🏫 and focus on my personal goals and family 👩👦 for a couple of years before enrolling in the university to pursue my Bachelors degree in computer science 💻.
👉🏼What have you been up to?.
👉🏼 What plans do you have for the new year?.
much love, Cece 🌸 (@carmencodes_)
2 5411 minutes ago
🤓 See that #V8? The universe is still giving me signs that the path I’ve chosen 22 years ago is the right one.
I decided to become a programmer when I was pretty much 10 years old. I was playing DOS games on my father’s computer and I was so curious how they were made that I started digging around how to make my own games, adventure games to be exact. That was before this thing we call internet these days. So I went to our library, found a book about #Basic and started learning how to write stuff in it. My first game was a short text-based adventure game. A few years later, the internet came to my country and I was obsessed with it. The idea of creating pages other people can instantly see was huge. And that was probably the moment when I decided I want to be a web developer. It was a hell of a ride up to this moment. Going from Netscape, IE6, table layouts, tag, Macromedia Flash, jQuery to #Vue. And that’s just the frontend stuff, not mentioning Basic, Pascal, PHP, … lol.
But the most wonderful thing about this is my passion is still the same today as it was 22 years ago. I’m just a bit older, but the passion is the same or perhaps even bigger. Which I’m grateful for. 🙏
Working on this app is my biggest pain & fun ever! 🙏🏾🙌🏾 When Tech is life 👀😂🙌🏾 please don’t ask me for favors or referrals 😂🙌🏾 Lil dumb bitch ain’t so stupid after all 🙏🏾😂😂😂😂😂😂 Invest in consistency before making assumptions... We all aren’t born privileged 😂🙌🏾The Orchid The Blossomed From the concrete ! Bih
Meal prepping for the week before christmas today. 2 crock pots and a pot on the stove should get us through all of the last minute shopping, cookie baking, present wrapping and all that comes with prepping for the holiday.
Meal prepping is a great way to stay focused on your nutrition during busy times when cooking a full meal can be difficult.
Rate this setup 👇🤓🚀 Photo by: @tara.vox -
Do you plan how you're going to implement a solution with code before you start writing it? I have a mental checklist of things I do before I ever start building out functionality. Some things require all steps, some a few. Here's how I do it!
1.⚙ Check that I understand what I'm about to work on and why. What's the problem I'm solving? Why is this important? Who does it impact?
2. 🧠 Brainstorm possible solutions. Have I done something similar previously? Is one possible solution more cost effective than another? Often times there are multiple ways to solve a single problem and usually it comes down to doing the best I can with the information I have at the time.
3. 📝 Document the things I know I need to do. Do I need to save something to the database? Do I need to change what's displayed based on a user interaction? I often do this in a checklist in Trello. It helps me remember things and creates a level of transparency to the team about the details of what's been done.
4.❓Document my unknowns. This is often limited by what I know I don't know meaning there may be something that I dont know I'm missing. But it's still good to make note of things I'll need to know and then make a point to get the answers.
5. 💻 Write out todos in my editor! If I know something is going to be logic intensive or have special cases, I'll write out what I need to do in a comment. Often times editors recognize todos and highlight them like they do any other keywords and allow you to search by them.
6. ⌨ And last but not least, code!! 🎉