Tailwind CSS is far beyond every other CSS framework out there. It’s tiny, blazing fast, easy to implement and entirely free! Plain CSS is a thing of the past.

TailwindCSS- You don’t have to hate styling anymore

Performance improvements, DevTools updates, new Material You support, a new app template, and more!

Hello and welcome to Flutter 2.5! This is a big release, with the 2nd highest stats in the history of Flutter releases: 4600 issues closed and 3932 PRs merged from 252 contributors with 216 reviewers. If we look back over the last year, we see a huge 21,072 PRs created by 1337 contributors, of which 15,172 of them were merged. While the “what’s new in Flutter” blog posts focuses on new features, our #1 job with Flutter is always making sure you have the features you need at the highest possible quality level.

And in fact, this release continues a number of important performance and tooling improvements to track down performance problems in your own app. At the same time, there are a number of new features, including full screen support for Android, more Material You (also called v3) support, updated text editing to support switchable keyboard shortcuts, a new, more detailed look at your widgets in the Widget Inspector, new support for adding dependencies in your Visual Studio Code projects, new support for getting coverage information from your test runs in IntelliJ/Android Studio and a whole new app template to serve as a better foundation for your real-world Flutter apps. This release is jam-packed with exciting new updates, so let’s get started.

Performance: iOS shader warmup, async tasks, GC & message passing

This release comes with several performance improvements. First on this list is a PR to wire up Metal shader precompilation from offline training runs (#25644), which (as our benchmarks show) cuts worst case frame rasterization times by 2/3s, and the 99th percentile frame by half. We continue to make progress on reducing iOS jank and this is another step along that path. Shader warmup is but one source of jank, however. Previously, processing asynchronous events from the network, filesystem, plugins, or other isolates could interrupt animations, another source of jank. Following improvements to scheduling policies (#25789) on the UI isolate’s event loop in this release, frame processing now takes priority over processing other asynchronous events, eliminating jank from this source in our testing.

Frame lag due to processing asynchronous event results before and after📷

Another cause of jank is when the garbage collector (GC)pauses the UI thread to reclaim memory. Previously, memory for some images would only be reclaimed lazily in response to GC performed by the Dart VM. As a workaround in earlier releases, the Flutter Engine would hint to the Dart VM that image memory could be reclaimed by a GC, which in theory could lead to more timely memory reclamation. Unfortunately, in practice this led to too many major GCs, and the memory would still sometimes not be reclaimed quickly enough to avoid low-memory situations on memory constrained devices. In this release, memory for unused images is reclaimed eagerly (#26219, #82883, #84740), reducing GCs considerably.

GCs before and after adding the fix to eagerly reclaim unused large image memory📷

For example, in one of our tests, playing a 20 second animated GIF went from needing 400+ GCs to needing just 4. Fewer major GCs means that animations involving images appearing and disappearing will have less jank, and consume less CPU and power.

Another performance improvement in Flutter 2.5 is the latency when sending messages between Dart and Objective-C/Swift (iOS) or Dart and Java/Kotlin (Android). As part of tuning-up message channels generally, removing unnecessary copies from messaging codecs reduced latencies by up to 50% depending on message size and device (#25988, #26331).

iOS message latencies before and after📷

You can read more about the details of this work in the Improving Platform Channel Performance in Flutter blog post by Aaron Clarke.

One final performance update if you’re targeting iOS: In this release, Flutter apps built on on Apple Silicon M1 Macs run natively on ARM iOS simulators (#pull/85642). This means there’s no Rosetta translation between the Intel x86_64 instructions and ARM, which increases performance during your iOS app testing and allows you to avoid some subtle Rosetta issues (#74970, #79641). This is another step along the path for full support in Flutter for Apple Silicon. Stay tuned for more.

Dart 2.14: formatting, language features, pub & linting out-of-the-box

Of course, Flutter isn’t Flutter without the Dart language and runtime on which it builds. This release of Flutter comes with Dart 2.14. The new release of Dart comes with new formatting to make cascades more clear, new pub support for ignoring files, and new language features, including the return of the legendary triple shift operator. In addition, and one of the best things about Dart 2.14, is that this release has created a standard set of lints shared between new Dart and Flutter projects that come right out of the box.

`flutter create` comes out of the box with an analysis_options.yaml file pre-populated with recommended Flutter lints📷

Not only do you get these lints when you create a new Dart or Flutter project, but with just a few steps, you can add this same analysis to your existing apps as well. For the details of these lints, the new language features and more, check out the release announcement for Dart 2.14.

Framework: Android full screen, Material You & text editing shortcuts

The Flutter 2.5 release includes a number of fixes and improvements to the framework. Starting with Android, we’ve fixed a set of related issues around full screen modes with nearly 100 thumbs up between them. The names of the modes themselves makes this one of our favorite new features: lean back, sticky, sticky immersive, and edge to edge. This change also added a way to listen to fullscreen changes in the other modes. For example, if the user engages with the app, when the system UI comes back, developers can now write their code to return to fullscreen or do something else.

New Android edge-to-edge mode: normal mode (left), Edge to Edge mode (center), Edge to Edge with a custom SystemUIOverlayStyle (right)📷

In this release, we continue to build support for the new Material You (aka v3) specification, including updates to floating action button sizes and theming (#86441), and a new MaterialState.scrolledUnder state that you can see in action with the sample code in the PR (#79999).

New MaterialState.scrolledUnder state in action📷

And while we’re talking about scrolling, another improvement is the addition of scroll metrics notifications (#85221, #85499), which provide notifications of scrollable areas even if the user isn’t scrolling. For example, the following shows the scrollbar appearing or disappearing as appropriate based on the underlying size of the ListView:

The new scroll metrics notifications enabling the scrollbar to appear and disappear automatically without scrolling📷

In this case, you don’t have to write any code but if you want to capture the ScrollMetricNotificationchanges, you can. Special thanks goes out to community contributor xu-baolin who worked hard on this and came up with a great solution.

Another excellent contribution from the community is the addition of Material banner support to the ScaffoldMessenger. You may remember the ScaffoldMessenger from the Flutter 2.0 release announcement as a more robust way to show SnackBars at the bottom of the screen to provide users with notifications. In Flutter 2.5, you can now add a banner to the top of your scaffold that stays in place until the user dismisses it.

Your app can get this behavior by calling the showMaterialBanner method of ScaffoldMessenger:

The Material guidelines for banners state that your app should show only one at a time, so if your app calls showMaterialBanner more than once, the ScaffoldMessenger will maintain a queue, showing each new banner as the previous one is dismissed. Thanks to Calamity210 for this great addition to the Material support in Flutter!

Building further on Flutter 2.0 and its new text editing features, like text selection pivot points and being able to stop propagation of a keyboard event once it’s been handled, in this release, we’ve added the ability to make text editing keyboard shortcuts overridable (#85381). If you want Ctrl-A to do something custom instead of selecting all text, you can do that. The DefaultTextEditingShortcuts class contains a list of every keyboard shortcut supported by Flutter on each platform. If you want to override anything, use Flutter’s existing Shortcuts widget to remap any shortcut to an existing or custom intent. You can place that widget anywhere in your widget tree where you want the override to apply. Check out some examples in the API reference.

Plugins: camera, image picker & plus plugins

Another plugin that’s seen a lot of improvements is the camera plugin:

3795 [camera] android-rework part 1: Base classes to support Android Camera features

3796 [camera] android-rework part 2: Android auto focus feature

3797 [camera] android-rework part 3: Android exposure related features

3798 [camera] android-rework part 4: Android flash and zoom features

3799 [camera] android-rework part 5: Android FPS range, resolution and sensor orientation features

4039 [camera] android-rework part 6: Android exposure- and focus point features

4052 [camera] android-rework part 7: Android noise reduction feature

4054 [camera] android-rework part 8: Supporting modules for final implementation

4010 [camera] Do not trigger flat device orientation on iOS

4158 [camera] Fix coordinate rotation for setting focus- and exposure points on iOS

4197 [camera] Fix camera preview not always rebuilding on orientation change

3992 [camera] Prevent crash when setting unsupported FocusMode

4151 [camera] Introduce camera_web package

There’s also been a lot of work on the image_picker plugin focusing on the end-to-end camera experience:

3898 [image_picker] Image picker fix camera device

3956 [image_picker] Change storage location for camera captures to internal cache on Android, to comply with new Google Play storage requirements

4001 [image_picker] Removed redundant request for camera permission

4019 [image_picker] Fix rotation when camera is a source

This work improves the functionality and robustness of the camera and image_picker plugins for Android. In addition, you’ll notice an early version of the camera plugin is available with web support (#4151). This preview provides basic support for viewing camera preview, taking a picture, using flash and zoom controls, all on the web. It is currently not an endorsed plugin, so you will need to add it explicitly to be used in your web app.

The initial Android camera rewrite work was contributed by acoutts. The camera and image_picker work was landed by Baseflow, a consulting firm specializing in Flutter and well-known for their own packages on pub.dev. The camera_web work was largely done by Very Good Ventures, a US-based Flutter consulting firm. Many thanks to all of you for your contributions to the Flutter community!

Another valuable community contribution is by the Flutter Community organization, known for the “plus” plugins. With this release of Flutter, each of the corresponding plugins from the Flutter team now carry a recommendation just like this one for battery:

Furthermore, since these plugins are no longer actively maintained, they are no longer marked as Flutter Favorite plugins. If you haven’t already done so, we recommend moving to the plus versions of the following plugins:

Flutter DevTools: performance, Widget inspector, & polish

This release of Flutter comes with a number of improvements to Flutter DevTools. First and foremost is the added support in DevTools to take advantage of engine updates (#26205, #26233, #26237, #26970, #27074, #26617). One set of these updates enables Flutter to do a better job of associating trace events with specific frames, which helps developers to determine why a frame might be going over budget. You can see this reflected in the DevTools Frames chart that has been rebuilt to be “live”; frames are populated in this chart as they are rendered in your app. Selecting a frame from this chart navigates to the timeline events for that frame:

The Flutter engine now also identifies shader compilation events in the timeline. Flutter DevTools uses these events to help you diagnose shader compilation jank in your app.

DevTools detecting lost frames due to shader compilation📷

With this new feature, DevTools detects when you’ve lost frames to shader compilation so that you can fix the issue. To run your app as if it’s the first time (before your shader cache has been populated as it would be for any user), use flutter runwith the --purge-persistent-cache flag. This clears the cache to ensure you are reproducing the environment that users see for the “first run” or “re-open” (iOS) experience. This feature is still under development, so please file issues for problems you find, or for any improvements we can make to help debug shader compilation jank.

In addition, when you’re tracking down CPU performance issues in your app, you may have been swamped in profiling data from Dart and Flutter libraries and/or the native code of the engine. If you’d like to turn any of these off to focus on your own code, you can do that with the new CPU Profiler feature (#3236) that enables you to hide profiler information from any of these sources.

For any of the categories you don’t filter out, they’ve now been color-coded (#3310, #3324) so that you can easily see what parts of the CPU Frame Chart come from what parts of the system.

Colored frame chart to identify app vs. native vs. Dart vs. Flutter code activities in your app📷

Performance isn’t the only thing that you’ll want to debug. This release of DevTools comes with an update to the Widget Inspector that allows you to hover over a widget to evaluate the object, view properties, widget state, and so on.

And, when you select a widget, it automatically populates in the new Widget Inspector Console, where you can explore the widget’s properties.

When paused at a breakpoint, you can also evaluate expressions from the console.

In addition to the new features, the Widget Inspector has undergone a facelift. To make DevTools a more useful destination for understanding and debugging your Flutter apps, we partnered with Codemate, a creative tech agency in Finland, to make some updates.

Flutter DevTools polished UX for greater ease of use📷

In this screenshot, you can see the following changes:

Better communicating what the debug toggle buttons do — those buttons have new icons, task-oriented labels, as well as rich tooltips that describe what they do and when to use them. Each tooltip further links out to detailed documentation of the feature.

Easier to scan and locate widgets of interest — frequently used widgets from the Flutter framework now show icons in the widget tree view on the left hand side of the inspector. They’re further color coded based on their categories. For example, layout widgets are displayed in blue while content widgets are displayed in green. Furthermore, each Text widget now shows a preview of its content.

Aligning the color scheme of the layout explorer and the widget tree — it’s now easier to identify the same widget from the layout explorer and the widget tree. For example, the “Column” widget in the screenshot below is on a blue background in the layout explorer, and it has a blue icon in the widget tree view.

We’d love to hear your thoughts about any issues that stem from these updates or any other improvements we can make to ensure that DevTools works great. And these highlights are just the start. For a full list of what’s new in DevTools with this release of Flutter, check out the release notes:

IntelliJ/Android Studio: integration tests, test coverage, and icon previews

The IntelliJ/Android Studio plugin for Flutter has also undergone a number of improvements with this release, starting with the ability to run integration tests (#5459). Integration tests are whole-app tests that run on a device, live in the integration_test directory and use the same testWidgets() functionality from widget unit tests.

Integration testing your Flutter app in IntelliJ/Android Studio📷

To add an integration test to your project, follow the instructions on flutter.dev. To connect the test with IntelliJ or Android Studio, add a run configuration that launches the integration tests and connect a device for the test to use. Running the configuration allows you to run the test, including setting breakpoints, stepping, etc.

In addition, the latest IJ/AS plugin for Flutter allows you to see the coverage information for both unit test and integration test runs. You can access this from the toolbar button next to the “Debug” button:

Coverage info is displayed using red and green bars in the gutter of the editor. In this example, lines 9–13 were tested, but lines 3 and 4 were not.

The latest release also includes the new ability to preview icons used from packages from pub.dev built around TrueType font files (#5504, #5595, #5677, #5704), just as the Material and Cupertino icons support previewing.

Flutter is a cross platform framework. Build one codebase and deploy everywhere.

Flutter- Who needs to build native

With support for SEO, server side rendering, image optimisation and  more, NextJS is the new JavaScript framework king of the hill.

NextJs- The Javascript framework King

Web and mobile app development is one of the fastest growing (and changing) disciplines in the software industry- It seems like there is a new, revolutionary technology coming out every day. To create a successful web or mobile app today you need to have all the latest and greatest features to deliver the best user experience to outlive your competition. The tools you pick to architect your system can either make or break your application- so pick wisely!

As I mentioned, things change a lot, and they change very quickly- However, at the time of writing this post, Firebase is a true one stop shop for almost all of your web and mobile app needs (and your new best friend). Everything from the basic necessities (authentication, database, hosting) to niche product improvement tools (analytics, performance monitoring, App distribution and more) works right out of the box! The real kicker is the pricing model- For most people, its entirely free. Now don't quote me on this, it depends highly on how you architect things, but keep reading to find out how you can keep all your Firebase projects free (or for negligible cost).

One of the most widely used Firebase services is their real time database solution, Firestore. Yes, I said Firestore, not Realtime Database which is the other database solution they provide. The Realtime Database, as some long time users may know, is the OG Firebase. It was the very first SDK that Firebase provided after evolving from Envolve (A mobile chat application). Cloud Firestore was subsequently added to Firebase after being acquired by Google in October 2014, and is, in my opinion, far superior to RTDB. Hence I will not be covering RTDB- You can read more on that in the Docs.

If you are coming from the world of 3F normalized SQL databases then buckle up, you won't like what I'm about to say next. Firestore is a NoSQL, or non-relational database, where the goal is to be as far from relational data structures as is reasonable (There are in fact times to use legacy methodologies). I will provide an example of this by explaining how I architected the blog you are reading.

In a traditional SQL database the data or content relating to a blog would be stored separately from data regarding users (specifically users who comment on posts or reply to comments). Seems reasonable to do the same in Firestore right? Wrong! We are in chaos land right now... managed chaos of course. I do have separate collections (Think SQL tables) for users and blog posts, however when it comes to comments and replies, this blog has no knowledge of the users collection or it's data. I actually copy the minimum required amount of information from the user's document (think SQL record or row) to a sub collection under blog posts as follows:

where the comment ID is the user ID of the person who made the comment. The type of data you store is entirely up to you and your use case but for me it's their profile picture; user info; some metadata about when they created/updated their comment and the comment body itself. This architecture was chosen entirely on purpose, is very untraditional and I can understand if your heart rate is rising.

It is possible to create a reference to the user by their user ID within the comment document, but that would be quite costly to both performance and the wallet. In NoSQL land it's all about the reads. How can you optimize your application to be as fast as possible, make as little requests to the database as possible, all while populating the screen with everything you need? With this in mind it makes sense to copy the user data, along with their comment. This avoids n database reads (one for every blog comment) as well as n database reads to retrieve user data. I just saved you twice as many db operations. All for the grand total of $0.

With Firestore charging $0.06 per 100,000 reads (After you have exceeded the 50,000 daily free tier) and $0.18 per 100,000 writes (After the daily 20,000 free tier) it's fairly obvious that optimizing for reads will most certainly save you money in the long run. Although, if you do ever get charged a hefty amount, please let me know because you may have a unicorn app on your hands. Before moving on to the elephant in the room, "What happens when a user updates their profile!?", I want to quickly touch on the real time streaming functionality of firebase. If you keep this any of these posts open long enough (Which should be all day smh) you will see comments and votes reflecting in real time. This is because Firestore allows you to subscribe to observable snapshot changes (the latest update) of your data which is reflected in the UI as soon as the database changes. Observables are a whole bag of nuts and bolts alone and may be delved into in another post.

So then, lets answer your earlier question. Say a user decides to change their profile information, how do I handle the fact that the profile picture, email or username on the comment will be stale? Here comes the interlude to the next Firebase service you should be using, Cloud Functions. Firebase Cloud Functions, or FCF for short, are pretty much glorified versions of NodeJs runtimes, wrapped up in a docker container and hosted on the cloud (In this case- Cloud Run. keep a look out for a fture blog post on Cloud Run because it will be epic). In layman's terms, Your code is only sitting on a machine and running when it needs to be. Back to the answer- FCF has many triggers which spin up your code and perform the desired operation. One of those are database triggers (onRead, onWrite, onUpdate and onDelete). I simply write a function that listens for updates on any user document and propagates the new data to all the places that a user has commented or replied to a comment.

I know what you're thinking, "You just told us to optimize your database operations". Well, actually I said to optimize for reads which is exactly what I'm doing. A user might change their profile information once in a blue moon- In which case, yes, I will have to perform some extra read and write operations to make sure everything is up to date, but this will happen far fewer times than all of the times any given user reading a blog post, it's comments or replies to comments.

There are other Firebase Cloud Function types available too- Namely, 

Https functions - traditional URL based endpoints that you can access from any backend services or UI with regular HTTP calls.

Callable functions - similar to https functions but they need to be called within your firebase app's environment.

Scheduled functions - Ran on some predictable timeline- daily, hourly, or whatever timeline you and you need and your wallet can handle.

Background triggers - These can happen for various reasons, Authentication changes, Firestore/RTDB changes as mentioned above, Cloud Storage, Pub-Sub and more. Check out the Docs for more info.

Each of these have their own unique use case and Firebase Cloud Functions truly deserves it's own post (coming soon).

I spoke a bit about users and their data without telling you how I actually get users and tie them to their database record. Good thing you're still reading because now is the time to talk about Authentication- One of the most difficult and time consuming things to get right (Unless you use Firebase of course). With Firebase Authentication you can allow your users to sign up and log in with email and password without having to encrypt their password. You can also join the revolution and allow users to sign in with their provider of choice (commonly known as Single Sign On or SSO). With less than five lines of code you can let your users sign in with Google, Facebook, GitHub, Apple and other popular O-Auth providers. Irrespective of the method you choose, Firebase will take care of all the security, authentication state management and provide you with a nifty token which lets you identify your users. It is common practice to tie your user's authentication token and database records by setting their document Id (think primary key if you're still in a SQL mindset) to their authentication token. The authentication SDK provides a whole host of other common authentication solutions like resetting passwords, sending email confirmations and even two factor authentication by sending text messages with a OTP (one time pin).

The last major necessity of modern app development is being able to host your website in a way that can scale to millions of users and still allow them to access your app or site securely and quickly. Firebase Hosting can do just that. With a single command,

You can send your code up to one of Google's fast and secure servers where it can be hosted for free and accessed by users from all around the world. As easy as it is to host a website or app with Firebase there is yet another, even better service provided by Vercel (The company behind NextJS) but that is beyond the scope of this post.

Once you have your application set up and users are coming to your site your next priority is to keep them there. Firebase has an entire vertical designed to do just that. Starting with making sure your users have a good experience, you will want to be using the Crashlytics and Performance Monitoring SDK's. Crashlytics is available to mobile and Unity applications right now but will be coming to web soon. This will allow you to determine which actions are causing your app to crash, along with metadata like the region, device types and more. Performance monitoring allows you to track the time it takes for operations to complete- this could be database calls, page loads or entire user flows (eg. how long it takes your user to click on a product since opening the app). Tracking this information will allow you to determine areas which could be improved, and in turn allowing you to create that frictionless user experience. The last core feature (and one of the most powerful) is Firebase Analytics. Adding analytics to your site will give you a fairly granular understanding of how your users are engaging with your app. This includes monitoring which pages get the most traffic, logging certain actions (events) such as adding a product to shopping cart, marking certain events as conversions (purchasing said item) as well as some data about your users like where they are visiting your site or app from, their device and browser types and many other custom markers that you can customize and control.

If you are still reading at this point you're probably one of those aforementioned power users. This last section is for you. At the very bleeding edge of user engagement technology is remote configurations and A/B testing. I have not implemented either of these extensively but the just of it is that you have the power to deliver custom user experiences based on some collected properties, as well as run tests with segmented groups of users to determine if one layout or color scheme drives more engagement than the other. Lately, these kinds of features have been under some scrutiny due to media backlash. In most cases the intention is good but I understand that it may seem a bit intrusive to use software and psychology to keep users glued to the screen. The Netflix show, The Social Dilemma does a great job of highlighting this and explaining things in layman's terms. Whether you choose to use it or not is entirely up to you but Firebase provides you with these tools in the event that you do, saving you enormous amounts of time and money to develop something custom from scratch.

There are plenty of other incredible tools that Firebase has to offer but I'm trying to keep you from falling asleep here. I'm planning to turn this into a mini series where I go more in depth for all of the tools discussed here as well as some that I left out. Please leave a comment down below if there is anything you think I missed or could elaborate on, or if there is a specific feature you want me to prioritize for a future post.

Lastly, I had the privilege and pleasure of running an entire video event series explaining the core features of Firebase by building an E-Commerce website. This was done during my time as a Google Developer Students Club Lead, in conjunction with another Lead, Andrii Denysenko (Who is extremely intelligent and a great developer) from the University of Conestoga in Ontario Canada. The series was accompanied by a GitHub repository, which has starter and completed code, allowing you to follow along and test out implementations on your own, or just view the final product. I'll leave links to all of the above below in case you would like to check it out.

Thanks for reading and I look forward to hearing some feedback in the comment section below.

Firebase is a backend service which makes it much easier to develop modern web and mobile applications. This post will outline some of the main features.

Firebase- A developers best friend

Please be prepared for lots and lots of puns in this blog (I think this may be one of the rare occasions a programmer has used hello world appropriately).

This entry is mostly going to be about the purpose and intention of this blog, as well as a little bit about me; I.e. why you should come back for more and who is it that is posting these blogs.

The intention behind this blog is to have a place where I can throw out wild ideas, projects I've worked on, topics I'm passionate about, or any other wildly random thing that pops into my head. There is a catch however- I want feedback. I want to hear your opinion.

More than just receiving feedback, I hope to have it shared for anyone else who comes across this page and might benefit from it. There are some complications however- Not all comments or ideas are good (mine included).

In order to combat this, I have designed a system which is somewhat similar to the reputation and permission based model of Stack Overflow.

You, the user, will start off with limited abilities to upvote, downvote, moderate or post your own blogs. With time, however (and positive engagement), you will build reputation and gain access to do more fancy things.

Self moderated (trusted users can remove nasty comments)

Inclusive (everyone has the opportunity to be heard)

Replying to posts, upvoting posts or comments and other forms of engagement will all contribute to your reputation (and associated permissions), allowing you to further engage with the community.

Enough about that, who am I and why should you care?

Well, I like to go by Raff - Born Rafael Zasas, 23 years ago today in Johannesburg, South Africa to mama Arlene and papa Reuben.

I was not very talented or intelligent by any standards in my early years and struggled to fit in quite a bit.

I got extremely lucky when my mom convinced me to become a swimmer- I was finally okay at something and it changed my life forever. I learned that it is possible to start off terrible at something and slowly work your way up. After all, "Sucking at something is the first step to becoming good at it." (Jake the dog). I went on to win a few junior national medals, even captained a junior national team (Junior All African Games 2015).

Later on in my high school career I found out that I also really enjoyed programming (something I sucked at in the beginning too). Through lots of practice, I was able to  fake my way through a B.S in Computer Science with a minor in applied math and physics from the University of Redlands in California; start a chapter of the Google Developer Student Clubs at my university; land my first job as a Software Engineer in a different country and even create this blog entirely from scratch.

With all that being said, I think I've learned a good amount in the short time I've been on the blue marble, and would like to share, learn and grow with all of you reading this.

I hope to see you in the comment section and future posts to come!

My first blog entry! This post outlines why I created a blog, how you can contribute, and a little bit about myself. Hope you enjoy!

From the blog