Hi everyone,

I may have an upcoming interview for a Senior Data Platform Engineer role, and I’m trying to prepare properly.

My background is mainly as an Azure Platform Engineer — I’ve worked with Azure networking, CI/CD, security, infrastructure, App Services, AKS, monitoring, etc. However, I was told that a big portion of the interview may focus on Databricks and data engineering concepts.

For those who work with Azure Databricks or interview candidates for similar roles:

• What topics should I focus on the most?
• What kind of Databricks questions are commonly asked in interviews?
• How deep should I go into Spark internals, Delta Lake, medallion architecture, optimization, clusters, Unity Catalog, etc.?
• Are there any must-know concepts or hands-on exercises you’d recommend?

I’d also appreciate any advice on how platform engineering experience can be positioned well for a data platform role.

Thanks in advance!

Hey everyone 👋

I’m currently building a Flutter app and trying to choose a backend/database stack that can grow from an MVP into a production-grade product (potentially large-scale later).

I keep seeing different choices like Firebase/Firestore, Supabase (Postgres), custom Node/Django backends, etc., and I’m trying to understand what actually works well in real production environments—not just in tutorials.

I’d love to hear from people who have actually shipped Flutter apps.

Specifically:

• What backend/database are you currently using in your Flutter app(s)?
• How many apps (or what scale) have you built with it? (MVP, startup, production, large user base, etc.)
• Why did you choose it over other options?
• What are the biggest pros/cons you’ve experienced in real usage?
• If you could restart today, would you pick the same stack again?

I’m especially interested in what holds up well when moving from MVP → production scale (performance, cost, complexity, scaling pain, vendor lock-in, etc.).

Thanks a lot 🙌

I am currently building my first serious Flutter application and trying to make good long-term architectural decisions early.

One thing I am currently researching is routing/navigation.

I know Flutter has multiple routing solutions like:

• go_router
• auto_route
• Beamer
• GetX routing
• Navigator 2.0 directly
• etc.

What I would really like to understand from experienced Flutter developers is:

Which routing package would you personally recommend for a production-grade Flutter application that needs to scale long term?

By “scale”, I mean:

• large codebase
• clean navigation architecture
• deep linking support
• authentication guards
• nested navigation
• maintainability over time
• used by real apps with large user bases

I am less interested in “what works for a small demo app” and more interested in: what teams actually trust in production and why.

I would also really appreciate if you could explain:

• why you chose it
• tradeoffs you experienced
• things you regret
• what becomes painful at scale
• what you would choose again if starting from scratch today

Thanks! I’m trying to learn the right mental models early instead of just following tutorials.

Hi everyone,

I recently started my competitive programming journey, and I wanted to ask if anyone else has dealt with "brain fog" when looking at new problems.

Today, I tried solving an 800-rated implementation problem. As soon as I saw the text, I felt overwhelmed. Before I even finished reading, I had a gut feeling that I wouldn't be able to solve it. This feeling made it really hard to focus, and even after reading it multiple times, I struggled to understand what the question was actually asking for.

I feel stuck and a bit discouraged because this is supposed to be a "simple" level.

• Has anyone else experienced this "mental block" when starting out?
• How do you train yourself to stay calm and break down the problem when the text feels like too much?
• Does the ability to "parse" these problems quickly come with time, or am I missing a specific technique?

I’d love to hear any advice or stories from people who have been in this same situation. Thanks!

Hi everyone,

I recently started my competitive programming journey, and I wanted to ask if anyone else has dealt with "brain fog" when looking at new problems.

Today, I tried solving an 800-rated implementation problem. As soon as I saw the text, I felt overwhelmed. Before I even finished reading, I had a gut feeling that I wouldn't be able to solve it. This feeling made it really hard to focus, and even after reading it multiple times, I struggled to understand what the question was actually asking for.

I feel stuck and a bit discouraged because this is supposed to be a "simple" level.

• Has anyone else experienced this "mental block" when starting out?
• How do you train yourself to stay calm and break down the problem when the text feels like too much?
• Does the ability to "parse" these problems quickly come with time, or am I missing a specific technique?

I’d love to hear any advice or stories from people who have been in this same situation. Thanks!

https://preview.redd.it/whoywwjv5l0h1.png?width=900&format=png&auto=webp&s=62763e5498cd5573993c6d970c7605e6892d67da

Hi everyone, this is actually my first time ever posting to any subreddit, but I wanted to share my experience and get some thoughts from the community.

About three weeks ago, I bought the Garmin Fenix 8 (51mm AMOLED). Since then, I haven’t missed a single day of wearing it. I’ve been using it day in and day out to track my running goals, and honestly, I am very satisfied with the product itself. It has genuinely helped me reduce my screen time and stay much more focused on my physical fitness.

However, I’ve decided to return it for a few specific reasons:

• The "Scratch" Test: A few days ago, I accidentally hit the watch against a door knob. Even though it's titanium, it picked up a small scratch. I know this can happen with any watch, but being my first expensive timepiece, I was a little disappointed that it marked so easily after only three weeks.
• AMOLED vs. MIP: While the battery life is great and the screen is beautiful, I’ve realized the AMOLED is almost too bright. Even with notifications muted, I find it a bit distracting. I think I’m looking for something a bit more "boring" and less attractive. I want to try the MIP version because it’s less shiny, and the potential for even more battery life suits my needs better.
• Gesture Issues: I’ve also had some trouble with the hand gestures. At first, I thought I just wasn't doing it properly, but after three weeks, I’ve realized the watch simply doesn't react to my gestures consistently.

This is the first smartwatch I have ever owned, and it has already moved me into a much better situation regarding my health and activity levels. I'm definitely staying with the Garmin family, but I think the MIP version will be the better long-term fit for me.

Has anyone else made the switch from AMOLED back to MIP for similar reasons? Would love to hear your thoughts!