What does your life look like when you are living at your courageous best?

That question came from a leadership coach during a women’s leadership program I was part of at work. The room went quiet, then people started naming their fears. Talking to a large audience. Doing something new outside their comfort zone. Networking with unknown people.

I sat there realizing I did not share any of those fears. Mine was self-advocacy.

For years my mantra was to let the work speak for itself. It felt like the safer, more dignified choice. But in a world of shrinking attention spans, is it fair to expect someone else to notice what I built? That question sent me into a why-why analysis on what I was missing.

Two problems surfaced immediately. Firstly, I do not always know what I should be advocating for. I do the work, but I rarely stop to name what it proves about me. Moreover, even when I know what to say, I do not know how to say it without sounding like I am bragging.

And I am living this right now. I led a product build that went from zero to one with a successful beta run in three months. We are now moving towards general availability. Scaling it from here on needs more people on my team. But when I raise this with my leaders, I can see they do not instinctively get why.

Because I never told them what it actually took to get here. I never walked them through the build, the partner negotiations, the scaling decisions, the ongoing support, all of it stacked on top of each other for months. I assumed the beta success would speak for the effort behind it. It did not. Success is visible. The work underneath it is not, unless you name it.

This article is my attempt to work through both, using what I learned in the session and what I have tested since.

Self-advocacy begins with self-trust, and self-trust is shakier than it looks.

Every evening a voice shows up and tells me the day did not amount to much. It does not pause to check; it just delivers the verdict. I used to treat that voice as the final word.

But there is a second voice, if I actually let it speak. It does not argue with the critic directly. It just asks one question first. What did I actually get done today? Most evenings, when I stop and answer that honestly, the list is longer than the critic gave me credit for. The day was not wasted. I simply never stopped to notice it before moving on to the next thing.

Call it the critic and the mentor. The critic is fast and loud. It shows up uninvited every single day. The mentor only speaks if you deliberately ask it a question, which is exactly why it loses so often.

Here is the fix I am using. Every time the critic makes a claim, I call in the mentor to check it against evidence, not feeling.

And evidence comes in two forms. Functional evidence talks about what I actually produced. That is a fact, not a feeling, and it directly counters the critic's claim. Emotional evidence involves what I got through. Moments I stayed steady, or recovered from something hard.

The reason self-trust feels shaky is not that the evidence does not exist. It is that we never log it. The critic keeps a precise record of every shortfall. The mentor gets no record at all, unless you build one.

So the practical answer to problem one is simple. Keep a running log, even three lines a week, split into two columns. What did I produce. What did I get through. That log becomes the material your mentor uses to talk back to the critic. It is also, directly, the raw material for what you advocate for later.

Knowing your evidence is only half the problem. The other half is saying it out loud without it sounding like self-promotion.

Here is the distinction that unlocked this for me. Self-advocacy is stating a fact. Self-promotion is trying to win approval. The two get confused because they can use the same words. The difference is in what you attach to the sentence.

If I say, I turned around this initiative despite the constraints, and stop there, that is advocacy. It is a fact, stated plainly, with no ask attached.

If I add, so I hope people notice, or, so I deserve more credit, that same sentence turns into a request for approval, and it starts to feel uncomfortable to say, and to hear.

The technique is to separate the update from the ask. State what happened. Do not hedge it with a joke, do not shrink it with a qualifier, do not attach a request unless you actually have one. If you do have an ask, make it separately, and make it direct.

In practice, this sounds like: This shipped, and it took solving three specific constraints. Not: I don’t know if this matters, but I guess I managed to get this out despite everything. The first is advocacy. The second is an apology wearing the clothes of an update.

Self-advocacy is not one skill. It is knowing what to say, built from evidence you deliberately collect, and knowing how to say it, built from separating fact from request.

1. Log your evidence weekly, split into what you produced and what you got through.
2. When the critic speaks, ask what the mentor would say, using the log as proof, not opinion.
3. When you communicate an update, state the fact plainly, with no self-deprecating qualifier and no unstated ask.
4. If you have an actual request, make it as its own sentence, separate from the update.

I turned this log into a skill called daily self-advocacy log, open source on GitHub: github.com/kaantibshetty/skills-library/tree/main/career/daily-self-advocacy-log. You can schedule a task using this skill on Claude Cowork or Perplexity, and it will auto-trigger a conversation at the end of your day. Each evening it asks two questions: what did you produce and what did you get through, then saves the entry to a running log so the mentor always has evidence on hand.

The courageous version of me is not the one who talks the loudest about her work. It is the one who keeps the receipts and hands them over without apologizing for it.

The Courage Nobody Talks About was originally published in Code Like A Girl on Medium, where people are continuing the conversation by highlighting and responding to this story.

This wellfield is located on Kitchener's west side near Trussler Rd. and the boundary with Wilmot Township. It consists of multiple Supply Wells (i.e. pumping wells K21A, K25, K29) along with Recovery Wells (RCW1-2) originally and now RCW 2-4.  Aquifer Storage & Recovery Wells (ASR1-5) are to accept treated Grand River water for storage to be pumped later into the distribution system by the Recovery Wells RCW 2-4 .   There are also a set of wells known as Peaking wells and they are designated K91-94). 

I would very much like to see audited up to date pumping rates for all these wells because the data I do have does not jive with the reality of a system constantly needing to expand along with our population. I have long suspected that the entire Mannheim  Aquifer Storage and Recovery System has not lived up to expectations whether through misadventure, bad luck or poor planning. Regardless again the data for all these wells that I have shows pumping rates well below the permitted volumes. This alone without ever greater population growth would cause pressure on other nearby well systems to take up the slack. This would include the Mannheim West Wellfield in Wilmot Township as well as the just down the road further west Wilmot Centre Wellfield which has been causing well interference complaints from local residents.

Under all the circumstances well interference is hardly surprising but what is, is the Region's hardas# attitude towards these residents and their water shortages possibly caused by again misadventure, bad luck or poor planning. 

The OTT industry continues to grow rapidly as streaming consumption increases across global markets. In 2026, consumers are looking for seamless playback, a continuous streaming experience, and broadcast-quality service on every device. Streaming reliability has become a key factor influencing user retention, which is why businesses are prioritizing high-quality OTT platform development services to drive long-term growth.

According to the latest market estimates by Ampere Analysis, global OTT revenues are already in the hundreds of billions of dollars, despite ever-growing consumer expectations.

On the OTT platform side, a few moments of delay may cause loss of subscribers, loss of viewing duration, lower ad completions, and reputational damage. With increasing competition and growing numbers of users, operational reliability has become a major competitive differentiator for streaming platforms.

Quality of streams is no longer a technical characteristic that concerns backend systems alone. Rather, stream quality is now considered a key business KPI tied directly to client retention and monetization.

According to industry studies by Conviva in its State of Streaming report, buffering and playback problems have been found to affect viewer engagement and session completion for OTT platforms.

The multi-CDN approach remains one of the most efficient ways of lowering buffering and reducing downtime.

Relying on a single CDN provider creates operational risks. Regional CDN outages, ISP routing issues, and sudden traffic spikes can negatively affect streaming performance if traffic cannot be dynamically redirected.

By implementing multi-CDN infrastructure, an OTT provider may route customers to a high-performance CDN depending on various factors such as:

• Customer’s location
• Network traffic
• Network latency
• Performance of CDN in real time
• Network demand

A 2025-study on CDN-based live-streaming architectures stated that a drop in buffering rate can be achieved due to optimization of edge delivery and CDN routing practices.

Keeping video playback smooth when millions of people log in at once is tough. Live sports, big movie releases, or breaking news can bring in huge crowds in just a few minutes. If a platform isn’t ready, these sudden traffic spikes cause buffering, crashes, login delays, and network overloads.

To handle these crowded moments, advanced OTT app development services focus on a few key operational steps:

• Smart Scaling: Using past data to prepare servers before the crowd arrives.
• Traffic Spreading: Sharing the user load across different regions and servers.
• Auto-Backup Systems: Instantly switching to a backup network if the main one fails.
• Edge Storage: Storing content closer to the users so videos load faster.
• Fast Processing: Speeding up how live video is broken down and sent to devices.
• Stress Tests: Testing the system with fake traffic before the real event starts.

Running these tests helps companies find and fix weak spots in their streaming setup ahead of time. This proactive approach prevents annoying disruptions when viewer numbers — and ad revenues — are at their highest.

Standard infrastructure monitoring is not adequate for today’s streaming services.

Earlier, the main concerns of OTT operations managers were uptime, bandwidth, and server availability. But these indicators don’t capture the full picture of the viewer’s experience.

The recent trend in the streaming world is Quality of Experience (QoE) monitoring that analyzes the performance of content delivery from the viewer’s perspective.

Here are the key factors that successful OTT organizations currently monitor:

1. Rebuffering ratio
2. Video load time
3. Failure rate
4. Adaptive bitrate switch
5. Session abandonment
6. Performance based on specific devices
7. Streaming degradation related to ISPs

This allows OTT teams to detect and resolve playback issues proactively before they impact viewer satisfaction. Moreover, modern monitoring tools utilize AI technologies to analyze potential problems and take immediate action automatically.

Adaptive bitrate (ABR) streaming dynamically adjusts video quality based on network conditions to maintain stable playback. However, improper configuration of bitrate ladders results in fluctuating quality issues, unnecessary buffering, and unstable playback experience for users.

Current best practices for improving OTT streaming are as follows:

• Well-tuned bitrate ladders
• Device-dependent encoding profiles
• Optimized segments
• Increased efficiency of manifest delivery
• Low-latency packaging
• Fast transcoding process

Codec optimization is now gaining popularity among OTT service providers to minimize data usage while preserving high visual quality.

Codec efficiency becomes especially important for global OTT apps serving millions of concurrent users.

Ultra-low-latency streaming demand is increasing rapidly, especially in:

• Live sports coverage
• Streaming interactivity
• Gambling integration
• Gaming content
• Real-time user interaction

Yet, ultra-low latency creates operational challenges.

Lowering latencies aggressively without building resilient systems may lead to higher levels of playback disruptions, synchronization problems, and segment delivery failures.

Successful OTT services focus on balancing latency and reliability rather than chasing the minimum latency possible.

Artificial intelligence is becoming an increasingly important part of OTT infrastructural management.

Advanced AI technologies have the ability to predict:

1. Spikes in traffic
2. CDN congestion
3. Degradation of playback quality
4. Potential risks of viewer churn
5. Regional network instability
6. Infrastructural bottlenecks

AI can also enhance adaptive streaming by taking advantage of user behavior and network conditions. As a result, the quality of bitrate distribution, traffic routing, and fault recovery becomes much better.

OTT infrastructure is gradually evolving toward self-healing systems capable of detecting and resolving issues automatically.

For OTT providers in 2026, minimizing buffering and downtime is no longer just a technical objective — it is a business necessity.

As competition intensifies, investing in reliable OTT app development services is the best way for brands to secure interruption-free streaming, stronger viewer retention, and long-term growth.

Reducing Buffering and Downtime: Operational Best Practices for OTT Platforms was originally published in Code Like A Girl on Medium, where people are continuing the conversation by highlighting and responding to this story.

June brought a modest increase in real estate sales across Waterloo Region, but buyers remained highly selective and home prices continued to soften.

A total of 650 homes sold during the month, representing a 2.7% increase from the 633 sales recorded in May. However, sales remained 4.4% below June 2025 levels. Both the average and median sale prices also declined year-over-year.

The Waterloo Region real estate market remains active, but it is not forgiving. Buyers are responding when they see clear value, while homes that are overpriced, poorly prepared or incorrectly positioned are having a much more difficult time generating meaningful interest.

Compared with May 2026 and June 2025:

• 650 homes sold: Up 2.7% from May, but down 4.4% year-over-year
• $730,668 average sale price: Down approximately 1.9% from May and 6.5% year-over-year
• $690,000 median sale price: Down 5.0% year-over-year
• 1,401 new listings: Down 3.8% from May and 7.5% year-over-year
• 2,053 homes available for sale: Up 1.5% from May, but down 6.7% year-over-year
• 27 average days on market: Unchanged from June 2025
• 4.1 months of inventory: Down slightly from 4.2 months one year ago
• 100.9% of the most recent list price received: Compared with 101.2% in June 2025

Cornerstone Association of REALTORS®

The month-over-month picture was mixed. More homes sold in June, but prices softened and selling timelines generally lengthened compared with May.

Year-over-year, sales, prices, new listings and overall inventory all remained lower.

Beyond the statistics, buyers continue to respond most strongly to homes that are properly prepared, accurately priced and effectively positioned from the beginning.

Today’s buyers have access to more market information than ever. They are comparing each property against competing listings, recent sales, neighbourhood trends, condition, location and overall value.

Strategic pricing is no longer simply about attracting online views or showing activity. It is about creating enough interest and confidence to motivate qualified buyers to act.

The sellers achieving the strongest results are generally those who fully commit to the selling process. They follow the recommended preparation and staging plan, address the details that matter and price according to current market conditions rather than past expectations.

We saw this firsthand with 2 recent listings priced above $1 million. Both homes were priced at current market value rather than intentionally underpriced, and both sold within days, above asking and in multiple offers.

In each case, the sellers fully committed to the recommended preparation, staging, pricing, marketing and launch strategy.

Not every home requires extensive renovations or a major financial investment before selling. The key is understanding which improvements will influence buyers, where money should and should not be spent, and how to position the property so it stands out from competing homes for sale in Waterloo Region.

Single-family homes continued to outperform the townhouse and condominium segment in June.

• 430 sales: Up 2.9% from May, but down 2.5% year-over-year
• $838,386 average sale price: Down 1.7% from May and 7.0% year-over-year
• $775,000 median sale price: Down 0.8% from May and 6.1% year-over-year
• 23 average days on market: Up from 20 days in May and unchanged from June 2025
• 3.4 months of inventory
• 101.4% of the most recent list price received

Cornerstone Association of REALTORS®

Year-to-date single-family home sales were essentially unchanged from 2025, increasing by just 0.1%.

With fewer months of inventory and shorter selling timelines than other property categories, the single-family segment continues to experience stronger relative demand.

Detached homes that are well maintained, properly presented and priced in line with recent neighbourhood sales can still attract significant buyer interest. However, buyers remain highly sensitive to condition and perceived value, particularly when comparing similar homes within the same price range.

The townhouse, semi-detached and condominium segment continues to offer buyers more choice and greater negotiating power.

• 220 sales: Up 2.3% from May, but down 7.9% year-over-year
• $520,128 average sale price: Down 2.8% from May and 7.0% year-over-year
• $525,000 median sale price: Down 4.5% from May and 5.4% year-over-year
• 35 average days on market: Up from 30 days in May and unchanged from June 2025
• 5.4 months of inventory
• 100.0% of the most recent list price received

Cornerstone Association of REALTORS®

With more inventory and longer selling timelines than the single-family segment, this portion of the Waterloo Region housing market remains especially price sensitive.

Accurate pricing and strong presentation become even more important when buyers have several comparable properties to choose from. Small differences in monthly fees, updates, layout, parking, location and overall condition can have a meaningful impact on buyer interest.

Sellers in this category should also be prepared for buyers to take more time, compare more options and negotiate more carefully than they may have during previous markets.

Nationally, Canada’s housing market continued to improve gradually in June.

Home sales increased by 0.5% from May, marking a third consecutive monthly increase and placing activity approximately 7% above March levels. The National Composite MLS® Home Price Index was unchanged from May, while national housing inventory remained close to its long-term average.

The Canadian Real Estate Association also revised its housing-market forecast in July. CREA now expects national home sales to decline modestly by 1.4% in 2026 following a weaker first half of the year, but anticipates a more active second half.

Importantly for the Waterloo Region real estate market, Ontario is now the only province forecast to record an annual increase in home sales in 2026.

National sales are then forecast to rise by 3.7% in 2027 as stable interest rates, modest economic growth and pent-up demand gradually bring more buyers back into the market.

On July 15, the Bank of Canada held its overnight rate at 2.25% for a sixth consecutive meeting. Canada’s annual inflation rate also eased to 2.8% in June from 3.2% in May.

Taken together, these developments support a cautiously optimistic outlook. A dramatic rebound is not expected, but stable interest rates, moderating inflation and improving activity in Ontario may help strengthen buyer and seller confidence as we move toward the fall market.

June demonstrated that strong selling results are still possible, but they are not automatic.

The homes performing best are generally those that are:

• Thoughtfully prepared before reaching the market
• Priced according to current conditions
• Professionally staged and photographed
• Marketed directly to the most likely buyers
• Positioned clearly against competing properties
• Launched with a coordinated strategy from the outset

A home does not need to be perfect, but it does need a clear plan.

That plan should consider the property itself, the surrounding neighbourhood, competing listings, recent sales, the target buyer and the realities of the current market.

Overpricing a home to “test the market” can be especially risky. The first days of a listing are often when buyer interest is strongest. If the price does not align with the home’s condition and competition, buyers may move on before a price adjustment is made.

For buyers, the current Waterloo Region housing market continues to offer more choice, more time to make informed decisions and greater negotiating opportunities than the highly competitive markets of recent years.

That does not mean every home will sell below asking or without competition. Well-priced homes in desirable neighbourhoods can still sell quickly and receive multiple offers.

However, buyers generally have more opportunity to complete proper due diligence, compare available properties and negotiate based on condition, recent sales and market value.

Working with a knowledgeable local real estate team remains important, particularly when evaluating whether a property is priced fairly or determining how aggressively to approach an offer.

June brought slightly stronger sales activity than May, but Waterloo Region home prices remained under pressure and buyers continued to be selective.

The opportunity for a strong result still exists. However, preparation, pricing, presentation and marketing matter more in this market than they did when limited inventory was driving nearly every property toward a quick sale.

Whether you are considering buying, selling, downsizing or relocating, your strategy should be based on current neighbourhood-level information rather than broad headlines or sale prices from several months ago.

If you are wondering what your home may be worth in today’s Waterloo Region real estate market, our team would be happy to provide a personalized market assessment and help you understand the best strategy for your property.

The post Waterloo Region Real Estate Market Report | July 2026 appeared first on Kitchener Waterloo Real Estate Agent - The Deutschmann Team.

If you’re a leader, or in any kind of leadership position, of course, you need vision, integrity, communication & emotional intelligence. But honestly, we have been saying the same things about leadership since the invention of LinkedIn. And while all of those qualities matter, there is genuinely so much more to being a good leader.

As a coach, when I read some of the conversations around leadership, I sometimes wonder whether we are developing leaders or simply finding creative ways to describe the ability to just be a decent human being. So, I want to talk about some of the more basic qualities that don’t always make it onto a leadership competency framework. The things that may sound simple, but actually mean a lot to your team.

Not: “I don’t know, but let me find out.” Just: “I don’t know.”
You are a leader. You are not Google with a job title.
You do not need to have every answer, know every detail or be the smartest person in every room you walk into. Your job is not to know everything.
Your job is to create an environment where people feel comfortable enough to ask questions, share ideas & work out the answers together.

There is something deeply reassuring about a leader who can say: “I’m not sure. Let’s figure it out.” Because the moment you stop pretending to know everything, you give everyone else permission to stop pretending too & honestly, that is usually when the best thinking begins.

This sounds obvious. It isn’t. Especially when:

• You have already explained something three times.
• The person in front of you is making a mistake you made five years ago.
• You are under pressure & everything feels urgent.

A good leader understands that people do not all learn at the same speed, process information in the same way, or gain confidence on the same timeline. Patience does not mean lowering your standards. It means giving people enough space to meet them. Also, if you have to give feedback, you should be able to do it without making the person feel like a personal inconvenience.

You can be honest without being condescending. Or you can be direct without being difficult & you can hold people accountable without making them afraid of you. Because feedback should help people become better at what they do. It should not be an opportunity for you to demonstrate how much you know, how frustrated you are, or how quickly you would have done it yourself.

Everything cannot be urgent. Sometimes the deadline is genuinely critical & sometimes you’re just stressed. A real leader knows the difference. Because your anxiety can quickly become everyone else’s workload.

If your team can only succeed when you are the smartest person in the room, you have not built a team. You have built a very expensive fan club.

A good leader hires people who know things they don’t. People who challenge them & occasionally have better ideas. And then they don’t take it personally.

Your team succeeding does not make you less important. In fact, that is the point.

“I’m sorry I spoke to you that way.” Not: “I’m sorry, but you were also being difficult.” That is not an apology. That is a performance review with emotional lighting.

Remember being new or being nervous before a meeting? Remember making a mistake & waiting for your manager’s reaction. Remember not knowing who to ask or wanting to speak but being afraid you would sound stupid?

If you forget what it felt like to be at the beginning, you may eventually become the reason other people are afraid to begin.

Sometimes your team wins. Not you. Your team.
You do not need to remind everyone that you were in the room when the idea happened. You do not need to explain how you approved it. You can just say: “That was their work. They did an excellent job.” And mean it. Your LinkedIn profile will survive.

Not every quiet employee is disengaged. Not every person who doesn’t speak in meetings lacks confidence. Not every person who doesn’t want to join Friday drinks has a culture problem.

Sometimes people are tired. Sometimes they are introverts, they have a life outside work. A good leader supports people without constantly trying to redesign their personalities.

Because leadership is humbling. You will send an email with the wrong attachment. You will confidently say something that makes absolutely no sense. You will walk into the wrong meeting.

You will have a deeply profound leadership moment & then immediately trip over a chair. It happens. You should be able to laugh. Because the best leaders I have encountered are not the ones who have perfected leadership. They are the ones who are self-aware enough to notice when they are getting it wrong.

They know when to speak.
When to listen.
When to push.
When to step back.
When to give feedback.
When to give people time.
When to say, “I was wrong.”
And when to stop calling every problem a “learning opportunity” & admit that everyone is simply very tired.

And perhaps this is where emotional intelligence matters most. In my opinion, it is probably the most important quality a leader can have. Not because it sounds good on a leadership competency framework, but because it affects everything.

How you speak to people.
How you give feedback.
How you handle pressure.
How you respond when you are wrong.
How you make people feel when they are still learning.
Because leadership is not about becoming the most impressive person in the room.
It is about making the people around you feel more capable, more confident & more able to do their best work.

People may not remember every strategy you created or every meeting you led. But they will remember how they felt around you. I’ve worked with some truly exceptional leaders, & I know I’ve done some of my best work around the leaders who made me feel trusted enough to do it. Whether they felt safe enough to ask questions. People will remember;

Whether they could make mistakes & recover.
Whether your feedback helped them grow or simply made them feel small.
Whether you gave them time.
Whether you gave them credit.
Whether you were patient when they were still learning.
And whether, somewhere along the way, you made them believe they could do more than they thought they could.
Because ultimately, the most underrated leadership quality of all is simply this: Being a human being before being a leader.

That, to me, is leadership.

The Leadership Qualities Nobody Puts on the Job Description was originally published in Code Like A Girl on Medium, where people are continuing the conversation by highlighting and responding to this story.

I used to think Kafka was one of those tools you just name-drop in interviews and hope nobody asks a follow-up question. “We’d use Kafka for that” is a sentence that has gotten a lot of engineers through a lot of rounds without anyone actually explaining what happens after you say it.

So here’s my attempt at the version I wish I’d had going in. Top down, starting from a dumb example and ending at the stuff that actually separates a senior answer from a staff answer.

Imagine you’re running a website that shows real-time World Cup stats. A goal happens, you push an update. A player gets booked, you push an update. Simple enough with one server: a producer puts events on a queue, a consumer reads them off and updates the site.

Now blow the tournament up to a hypothetical 1,000 teams, all playing at once. Your single queue is drowning. Your consumer has its mouth under a firehose. You need more servers.

Here’s where it gets interesting. If you just randomly spray events across new servers, you get chaos. Goals get scored before kickoff. Players get booked for fouls that haven’t happened yet, because ordering just broke.

The fix is almost embarrassingly simple once you see it: distribute events by game ID. Every event for one game always lands on the same partition, so within that game, order is preserved. This is the entire idea Kafka is built around. Everything else is commentary.

• Broker — one server in the cluster. More brokers, more storage, more clients served.
• Partition — an ordered, append-only log. This is the actual unit of scale.
• Topic — a logical grouping of partitions. This is what you publish to and subscribe from.
• Producer / Consumer — write to topics, read from topics. Kafka doesn’t care what’s inside the message.

One thing that trips people up: a topic and a partition are not the same axis. Topic is logical, partition is physical. A topic can span partitions across many different brokers.

Kafka can be either, and the difference comes down to consumption pattern, not the underlying mechanics. Both modes track progress with offset commits.

As a queue: one consumer in a group handles a message, and it’s effectively done (Kafka still holds onto it based on retention, but logically it’s consumed).

As a stream: the log sticks around, it can be replayed, and multiple independent consumer groups can read the same data at their own pace.

Reach for the queue pattern when you have async work (transcode this video whenever), or when order matters (a virtual waiting room), or when you want producer and consumer to scale independently.

Reach for the stream pattern when you need continuous real-time processing (aggregating ad clicks as they happen), or when several totally different consumers need to see the same events (pushing live comments to multiple downstream services).

The Message Body

• Four fields, all technically optional: value (the actual payload), key, timestamp, and headers.
• Order within a partition is decided by offset (position in the log), not by timestamp.

How a message finds its partition (two steps)

• Step 1: Kafka hashes the key and hash(key) % num_partitions to pick a partition. No key? It falls back to a default partitioner that spreads messages round the partitions.
• Step 2: the cluster controller’s metadata tells the producer which broker holds that partition, and the message is sent straight there.

Once it lands: the immutable log

• Messages are appended only, never edited in place.
• Old data leaves only through retention (time/size limits) or compaction (keeping just the latest value per key).
• That immutability is what makes replication simple, recovery fast, and avoids a whole class of bugs that come from mutable state.

Durability: leader-follower replication

• One broker is the leader for a partition, handling all writes (and by default, reads).
• Followers replicate passively in the background.
• If the leader dies, an in-sync follower gets promoted.
• acks=all is the strongest guarantee: a message is only acknowledged once every in-sync replica has it.

Consumers pull, they’re never pushed to

• A deliberate design choice: consumers set their own pace, failure handling stays simple, and one slow consumer can’t take down the whole pipeline.

Key path: the message’s key gets hashed to pick a partition, the leader broker for that partition takes the write, followers replicate it, and it lands in the log at the next offset — ordered by position, not by timestamp.

This is the section that’s easy to skip when you’re first learning Kafka, and the section that gets asked about the moment you’re past mid-level.

One broker on decent hardware holds around 1TB and can push something like a million messages a second. That number is doing a lot of hand waving, since it depends heavily on message size and hardware, but it’s a reasonable anchor to reason from.

A couple of hard rules that come up fast in practice:

• Keep individual messages under 1MB.
• Never put a video file or a big blob directly into Kafka. Drop it in S3, and put the S3 pointer in the message instead.

Kafka is a log, not a filesystem. Treat it like one.

Adding brokers only helps if your topics already have enough partitions to spread across them. This is where an interview answer should live: not “we’ll add more brokers,” but “here’s how I’m choosing the partition key.”

The classic setup: you’re aggregating ad clicks, partitioned by ad ID, and a celebrity ad drops. One partition melts while the rest sit idle.

There are four moves here, and a good answer picks the right one for the situation instead of reciting all four:

1. Salt the key — append a random suffix (or a hash of something high-cardinality) to spread one hot key across multiple partitions.
2. Repartition with a better key — if one dimension is naturally skewed, partition on something more evenly distributed instead.
3. Over-partition upfront — provision more partitions than you think you need, so a spike has somewhere to spread to.
4. Isolate the hot key — give known hot entities (a celebrity account, a major ad campaign) their own dedicated partition or topic, so they don’t drag down everyone else’s throughput.

Worth internalizing: Kafka is always available, sometimes consistent.

If an interviewer asks “what happens when Kafka goes down,” that’s honestly not a very realistic question, and it’s fine to push back on it gently. What’s actually realistic is a consumer dying.

When that happens:

• Its partitions get rebalanced across the surviving consumers.
• On restart, it picks up from its last committed offset.

The catch: don’t commit that offset until the real side effect (writing to blob storage, whatever it is) is actually durable, or you’ll lose work on a crash.

• Producers get automatic retries. Pair that with idempotent producer mode so retries don’t create duplicates.
• Consumers get nothing out of the box. SQS gives you this for free, Kafka doesn’t. You build it yourself: a retry topic, a dedicated consumer for it, and a dead letter queue for anything that fails too many times.

This is actually why some designs pick SQS over Kafka outright, just to skip building this by hand.

Batching messages and compressing them (GZIP, Snappy, LZ4) both help, but neither moves the needle as a good key does. If you only have time to talk about one lever in an interview, make it this one.

Default is 7 days, controlled by retention.ms or retention.bytes. Need longer history for a design? Turn the dial up, and be ready to talk about the storage cost that comes with it.

If you remember nothing else: producers write to topics, topics are made of ordered append-only partitions spread across brokers, consumers pull from them, and almost every interesting design decision in the system comes down to how you pick your partition key. Everything above is really just detail on that one idea.

I used to think the interview-ready version of Kafka was knowing the vocabulary. It’s not. It’s being able to say “here’s how I’d pick the key” without blinking, and being honest that Kafka going down is a less interesting question than a consumer dying mid-batch.

Kafka is always available, sometimes consistent. Design accordingly!

I Said “We’d Use Kafka” in a Dozen Interviews Before I Actually Understood It was originally published in Code Like A Girl on Medium, where people are continuing the conversation by highlighting and responding to this story.

Bicep is a declarative language for describing and deploying Azure resources

Bicep 3.6k 2 issues need help Updated Jul 22

Asynchronous Python PostgreSQL driver written in Rust

Rust 360 Updated Jul 20

New generation PostgreSQL database adapter for the Python programming language

Python 2.5k 2 issues need help Updated Jul 20

A fast PostgreSQL Database Client Library for Python/asyncio.

Python 8.1k Updated Feb 27

We’re delighted to share some exciting news and updates at Child Witness Centre.

The post Summer Newsletter: Bright & Uplifting Highlights 🌞😎 first appeared on Child Witness Centre.

Wow! Today's K-W Record advises us that our vaunted LRT (Light Rail Transit) is having more than teething pains. The lawsuit by  GrandLinq is for $110 million. That's a chunk of change . Regardless of who's right, who's wrong and whether or not we taxpayers yet again end up on the hook; it tends to make us at the very least ask the question: "Are we getting value for money in our political governance?" Or do we have a lot of dead wood on regional council who are simply literally bums in chairs pretending to be administrators and managers of the public interest? Is it possible that half or more of them simply show up in order to receive their pay cheques with absolutely no  concern for the issues or the public interest? It has been said that the greatest and most important skill of a politician is their acting abilities. Pretending to care and pretending to want to resolve problems and disputes would seem beneficial in giving hope and confidence to citizens and residents.

If and when the entire truth is exposed around the destruction of our fabulous water resources; I predict there will be a wholesale abandoning of the ship of state. Politicians may quickly decide that early retirement sure beats being shamed and harassed into resigning mid term. I predict that as early as tomorrow or as late as the August 21 deadline for registering to run in this fall's municipal election; many rats will give varying excuses for stepping down. 

The Region have most recently mistreated Wilmot residents both with the still surreptitious huge land grab as well as the refusal to acknowledge well interference even after breaking the 1980 agreement with Wilmot over the Wilmot Centre Wellfield pumping. They have also broken faith with Woolwich (Elmira) residents for the last 36 years regarding our contaminated local aquifers caused by both private, industrial greed and negligence as well as by provincial oversight gross failures.  The Region's day of reckoning is overdue.

♦

Whatever organizations decree these kinds of things have seen fit to announce that there are not one but two “National Crème Brûlée” days, July 21 and July 27. Perhaps it is an indication of how popular the classic dessert is, so the laurels are likely well-deserved.

It’s true that at one time or another every chef makes a crème brûlée and just about every restaurant has it among its desserts; spend a few moments scanning menus, and I’m sure you will find several.

But popular hardly does it justice: there are crème brûlée recipes, attributed to Francois Massialot, dating to the French court of 1692. That’s over 300 years of the treat.

A custard of scalded milk, sugar and egg yolks, crème brûlée means “burned cream” which entails creating and baking in a water bath a soft, silken custard and chilling it before adding sugar to the top and caramelizing it, either under a hot broiler (in a restaurant kitchen, a salamander) or the fun way with a propane torch.

The key is to keep a cool, silky interior while getting just the right crispness – and not a rock-solid layer of impenetrable sugar – on the top for a well-balanced crunch.

Another reason for the dual national days, aside from its deliciousness, is the versatility that a crème brûlée has: that custard is a blank slate that can scrumptiously admit a vast array of sweet and savoury ingredients, from simple vanilla and chocolate to lavender and maple-bacon.

[Banner image/Wikimedia Commons]

Check out my latest post National Crème Brûlée Day from AndrewCoppolino.com.

Musy, S. L., Dresmann, H., Tomonaga, Y., Sano, Y., & Schilling, O. S. (2025). Modeling a geologically complex volcanic watershed for integrated water resources management in Mt. Fuji, Japan. Scientific Data, 13 (1). doi.org/10.1038/s41597-025-06380-z

CLICK HERE TO READ THE ARTICLE.

“Although HGS supports both finite element and finite difference methods, the present model was developed using the finite element approach. Accordingly, mesh generation was carried out with the finite element mesh generation software AlgoMesh using line and polygon vector files as input. The catchment contours, resampled at a 400 m resolution, define the outer extent of the mesh.”

Fig. 4. Set up for the integrated hydrogeological model of Mt. Fuji catchment (Japan); (a) Elemental zones in the porous medium domain, corresponding to the different hydrofacies in Table 1, as well as the lake and riverbeds (RB) and fault elements, corresponding to the lake and river beds, resp. to the fault zone; (b) Elemental zones for the overland flow domain, corresponding to the categories in Table 3; (c) Model boundary conditions: blue diamonds represent the critical depth boundary conditions for the surface domain in the Suruga Bay area, on the river outflows and on the catchment contours. The Fuji River Termination (SW) and Kise River effluent (SE) are set to no-flow boundary conditions (red spheres). The green boxes represent the fixed head for the subsurface domain in the Suruga bay area, and to the river elevation in the North and East outlets (not visible from this point of view). For the lateral subsurface boundaries for which no other boundary conditions are indicated, as well as for the base of the model, no flow conditions were imposed (not shown).

This publication presents a three-dimensional geological and integrated hydrological modelling dataset developed for the Mt. Fuji volcanic watershed in Japan. This study leverages HydroGeoSphere (HGS) to simulate coupled surface–subsurface flow and transport processes in a geologically complex volcanic catchment, addressing long-standing challenges in representing groundwater flow pathways and hydrologic interactions in structurally heterogeneous mountain environments. The resulting dataset provides a physically consistent modelling framework to support interdisciplinary water resources research and scenario-based hydrologic simulations.

Hydrologic analyses in volcanic terrains are often limited by sparse subsurface observations and simplified conceptual representations of hydrofacies structure. While geological datasets and monitoring networks provide valuable constraints, they rarely capture the full complexity of fractured volcanic aquifers and fault-controlled flow systems. By integrating stratigraphic interpretation, hydrofacies mapping, land-cover parameterization, and numerical mesh development within a HydroGeoSphere modelling workflow, this research establishes a catchment-scale framework capable of representing interactions between surface water, groundwater, and vegetation processes under realistic boundary conditions.

The study applied the HGS model to the Mt. Fuji watershed using a structured workflow that combined geological cross-sections, borehole data, hydrofacies surfaces, and land-use datasets to construct a three-dimensional representation of subsurface structure and hydrologic properties. Simulations successfully reproduced major surface-water features while capturing groundwater flow behaviour across contrasting aquifer thicknesses separated by regional fault systems. Results demonstrated that even a computationally efficient model configuration could reproduce realistic hydrologic system behaviour while supporting sensitivity analyses and scenario-based simulations for future research applications.

Key findings showed that integrated geological–hydrological modelling provides a robust foundation for evaluating groundwater dynamics in volcanic catchments, where structural uncertainty and limited calibration data often restrict predictive modelling efforts. The dataset enables further investigation of fault-controlled flow discontinuities, hydrofacies uncertainty, and climate-driven hydrologic variability within a unified modelling framework designed for extension through automated calibration and scenario testing.

HydroGeoSphere proved essential in enabling this work due to its ability to simulate fully integrated surface flow, variably saturated subsurface flow, discrete fracture flow, vegetation–land–water interactions, density-dependent transport, and winter hydrological processes within a single modelling platform. These capabilities allowed the researchers to construct a catchment-scale representation of the Mt. Fuji hydrologic system that captures the multi-process complexity characteristic of volcanic watersheds.

This research provides critical insights for integrated watershed modelling and groundwater resource assessment in geologically complex regions, demonstrating that advanced modelling approaches like HydroGeoSphere can support the development of reproducible, extensible hydrologic datasets for interdisciplinary research and long-term water management planning.

Abstract:

This dataset provides high-resolution 3D geological and integrated hydrological models of Mt. Fuji watershed in Japan. The watershed’s complex volcanic and tectonic setting, large spatial extent, and limited subsurface data present significant challenges for integrated hydrological modeling. Diverse geological datasets – borehole logs, geological maps, and hydrofacies surfaces – were collected, processed, and used to construct and validate a 3D geological model suitable for integrated hydrological simulations. Building on this, a 3D numerical model for integrated hydrological simulations was constructed. The repository includes 3D hydrofacies surfaces in raster format, numerical mesh files, and input configurations necessary to run simulations with the integrated surface-subsurface hydrological simulator HydroGeoSphere. The preparation of heterogeneous geological data, construction of hydrofacies surfaces, generation of the numerical mesh, and setup of the integrated hydrological model are described in a streamlined, reproducible workflow suited for volcanic contexts and transferable to other geologically complex or data-limited regions. These resources are intended to reduce trial-and-error iterations and support further research in groundwater assessment, model calibration, climate impact studies, and hazard mitigation.

CLICK HERE TO READ THE ARTICLE.

The most comprehensive authentication framework

TypeScript 29.3k 1 issue needs help Updated Jul 22

Authentication for the Web.

TypeScript 28.3k Updated Jul 22

The Database Toolkit for Python

Python 12k 4 issues need help Updated Jul 21

A database migrations tool for SQLAlchemy.

Python 4.3k Updated Jul 20

Open-source vector similarity search for Postgres

C 22.3k Updated Jul 11

♦Exciting progress is underway at 115 University Avenue East as construction continues to move forward and new life returns to this important community space.

While renovations are ongoing, the site is already active in meaningful ways. Weekly market pickups and Community Supported Agriculture (CSA) pickups are bringing people together and improving access to fresh, local food. At the same time, the urban garden is thriving, continuing its legacy as a place of growth, connection, and hands-on learning.

These early activities offer a glimpse of what’s to come.

Construction at 115 University is progressing well, and we’re excited about the opportunities the renovated space will offer. The vision centers on creating a flexible, inclusive environment that supports a wide range of community needs.

Planned features include:

• Teaching space for skill-building and group learning
• A learning kitchen to support cooking programs, nutrition education, and shared meals
• A calming room, designed as a sensory-friendly space similar to a Snoezelen room

These additions will allow the building to support diverse programming and provide welcoming spaces for people with varying needs and experiences.

There is also strong potential to collaborate with community partners, creating opportunities to host programming that extends the impact of the space even further.

As shared in our previous article, A Community Place for Everyone, 115 University Avenue has played an important role in supporting people for many years. The building has been home to day supports, horticulture activities, and social opportunities for adults with intellectual and developmental disabilities. Its gardens and flexible indoor spaces helped create opportunities for connection, routine, and meaningful participation.

Significant upgrades are now underway to improve accessibility, functionality, and comfort throughout the building. With the roof and windows already completed and interior work progressing, the space is being thoughtfully updated to better support a wider range of uses. While the building itself is not expanding, the redesigned interior will allow for more flexible programming and greater community use.

Once complete, 115 University will support a wide range of opportunities, including:

• Senior drop-in programs
• Expanded supports for adults with complex needs
• Horticulture and therapeutic programming
• On-site training and skill development
• Community events and gatherings

Thanks to a generous family donation and partial funding from the Ministry of Children, Community and Social Services, we have made strong progress. However, additional support is still needed to bring the full vision to life.

Monthly giving is a powerful way to help us finish what has begun. Ongoing donations provide reliable support that allows us to plan, build, and open our doors to the community.

♦ Learn more about monthly giving and support the project:
kwhab.ca/monthly-giving/

Every contribution brings us closer to reopening this space!

As construction continues and the gardens grow, we’ll keep sharing updates, stories, and ways to get involved. The momentum is building, and the future of 115 University Avenue East is full of possibility.

Together, we are creating a place where everyone feels welcome, connected, and supported.

♦

♦

The post Progress Continues at 115 University Avenue East appeared first on KW Habilitation.

The Experts in Lived Experience Council is beginning to take shape as a meaningful and empowering part of KW Habilitation’s future.

In its early stages, the Council is bringing together people who draw on their own lived experience to guide conversations, share insights, and build confidence in using their voices. It’s a space where people can grow as leaders, learn from one another, and explore how their perspectives can influence change. Through regular meetings and supportive discussions, members are developing skills in communication, advocacy, and decision-making.

As the Council continues to develop, its role will expand. There will be opportunities for members to contribute to committees, provide input on programs, and help shape the direction of services and supports at KW Habilitation. Their voices will help ensure that decisions reflect real experiences and priorities.

The long-term vision is clear: a strong, confident group of people who are actively involved, respected, and heard—helping to influence not only KW Habilitation, but the broader community as well.

The post People with Lived Experience Building Leadership Skills appeared first on KW Habilitation.

At KW Habilitation, our new strategic plan didn’t begin in a boardroom. It began with people. The people who live this work every day. The people we support. Their families. Our staff. Our partners. Our community.

We believe that the strongest plans are shaped by real experiences and by listening deeply to the voices that matter most. That belief guided how this plan came to life.

Working with Holly Hendershot and Christa Haanstra, we brought together a wide range of perspectives from across our community. Through conversations, surveys, interviews, and shared planning sessions, we asked important questions:

• What’s working well?

• Where do we need to grow?

• What matters most for the future?

The responses were thoughtful, honest, and incredibly valuable. In total, more than 220 people helped shape this plan, ensuring it reflects not just ideas, but lived experiences, shared priorities, and a collective vision for what comes next. Every voice contributed to a clearer understanding of who we are today and who we want to become.

The plan will reflect the belief that people with developmental disabilities are not simply included, they are active members of our community. People whose ideas, talents, relationships, and perspectives help shape and strengthen the communities we all share. This is the future we are working toward.

Starting this Fall, we’ll be sharing more about our strategic plan; our priorities, our goals, and how we’ll bring this vision to life. The plan will be shared in plain language and available to everyone.

For now, we want to recognize and thank everyone who contributed their voice, their experience, and their perspective. We’ll be sending each of those people an update on the final plan. This plan belongs to all of us.

The post Building Our Strategic Plan—Together appeared first on KW Habilitation.

In early June, KW Habilitation had the opportunity to take part in the Global Leadership Exchange (GLE)—an international gathering that connects leaders across disability, mental health, substance use, and addictions to share ideas, challenges, and solutions.

Our CEO, Ann Bilodeau, along with Jamie Russell, Director of HR, and Cherylyn Sawatzky, Manager of Administration, joined leaders from around the world for a week of learning, collaboration, and dialogue across Toronto and Ottawa.

As part of this experience, we also had the privilege of hosting guests from Scotland—Michael Stewart and Charlie McMillan—for a local conversation that brought global insights directly into our organization.

The first half of the Exchange brought people together for a series of “Matches”; small group sessions where participants explored specific topics, sharing experiences and perspectives from their own countries.

The Developmental Services Workforce Initiative (DSWI) was selected as one of the Match topics, bringing together leaders from the developmental services, disability, mental health, and substance use sectors from five countries. As part of the DSWI, KW Habilitation presented and contributed to conversations about building a strong, sustainable workforce for today and tomorrow. It was a unique opportunity to exchange ideas, learn from different systems, and explore shared challenges.

A key theme throughout the discussions was the importance of lived experience. Families and people with lived experience shared candid insights about what they expect from services and personal supports, reinforcing that meaningful change happens when the voices of those most impacted help shape decisions.

The conversations highlighted an important truth: building stronger systems and a more inclusive workforce requires collaboration, innovation, and a commitment to centering lived experience in everything we do.

♦The Exchange continued in Ottawa, where global leaders gathered for the Network Meeting. Across sessions and keynotes, several themes emerged:

• Collaboration is essential—no single organization or system can solve complex challenges alone

• Inclusion must be intentional and embedded in policy, practice, and culture

• Lived experience must shape decisions, not sit at the margins

• Leadership requires adaptability, shared accountability, and the courage to rethink systems

Speakers and participants shared perspectives on disability reform, system transformation, and the importance of aligning policy with lived realities.

A powerful keynote from Sandra Pronteau highlighted the intersection of disability, identity, and culture—reminding participants that inclusion is deeply connected to belonging, community, and opportunity.

♦During their time in Canada, Michael Stewart and Charlie McMillan joined us at KW Habilitation for a reflective conversation with staff, leadership, Board representation, and people with lived experience.

Together, we explored a central idea that echoed throughout the Exchange:
the importance of listening to “experts by experience.”

Inclusion is not only about being present—it’s about being heard, valued, and able to influence decisions.

Charlie also spoke about the role of allyship, describing it as creating space rather than taking it. He shared a simple but powerful example from a previous Exchange: when given the opportunity to speak with Queen Máxima of the Netherlands, he redirected the conversation to a delegate with lived experience, ensuring their voice was front and centre.

It was a small act, but one that reflected a bigger principle: meaningful inclusion requires intention.

While systems and structures may differ around the world, the GLE reinforced something important:
many of our challenges—and opportunities—are shared.

Being part of this global dialogue strengthens our work locally. It pushes us to think differently, act collaboratively, and continue centering lived experience in everything we do.

This is just one step in a larger journey. As we continue to share more about our strategic direction, the insights from the Global Leadership Exchange, and the voices of those with lived experience, will continue to guide the path forward.♦

♦

The post Centering Lived Experience: Reflections from the Global Leadership Exchange appeared first on KW Habilitation.

I don't know that to be true but I guess I'm hoping it is so because there are at least two people on that committee (Technical Remediation Advisory Committee) that I believe to be inherently honest. Indeed it is likely to be a couple more but I just don't know them well enough to confirm that. Generally speaking I do know the deadbeats etc. well enough and know who they are.

Jen Lyndall of Integral possibly may decide never to work for Lanxess and her old buddy Hadley ever again. Or otherwise if she has no problem sleeping at night by counting sheep jumping over dead animals, livestock and or human beings.   

I'm going to repeat last Saturday's health criteria here for those with a serious bent for eye blurring numbers. These are the health standards for dioxins/furans and for Total DDT both in creekbank soils and in the sediments on the bottom of the Creek (Canagagigue). None of the criteria change based on depth i.e. surface versus subsurface soils and surface and subsurface sediments.

Soils:               DDT      .078 ppm (parts per million)

Sediments:      DDT      .00119 ppm.

. 

Soils:              dioxins/furans      7  ppt. (parts per trillion)

Sediments:     dioxins/furans       .85 ppt

DDT   in   fish     tissues                 14 ppb. (parts per billion)

dioxins/furans in fish tissues             .71 ppt (parts per trillion)

These are the numbers/concentrations that Jen Lyndall of Integral has utterly failed to put on her Tables and Figures.  Likely/possibly they are buried somewhere in her report. Or not. Starting from Figure 4-24 and going to Figure 4-63 the data tells TRAC, the public and most certainly the politicians absolutely nothing worthwhile without the health criteria being clearly marked on each and every Figure.  Is this failure Jen Lyndall's or did Lanxess (Hadley ?) ensure that this vitally important information was not to be found where it should be?

BRANTFORD - An eighth inning RBI single made the difference as the Brantford Red Sox took down Kitchener 3-2 Sunday afternoon at Arnold Anderson Stadium.

Dionys Rodriguez went the distance for Kitchener, striking out six in eight innings of work. He walked three and gave up three runs on eight hits in the loss.

Brantford scored two runs in the first, but Kitchener responded with two runs in the seventh, including an RBI single by Malik Williams to drive in his brother Josh.

Yosvani Penalver and Malik Williams both registered two hits in the loss.

Kitchener drops to 10-16, while Brantford improves to 9-16. 

The Panthers remain half a game up on the Red Sox for sixth in the CBL, but trail Guelph by five games for the final playoff spot.

The Panthers welcome Toronto this Thursday for Oktoberfest Night at Jack Couch Park.

First pitch flies at 7:05 p.m.

GET YOUR TICKETS NOW and get ready to #PROSTTheJack!

How does Google search manage to locate a particular web page among billions of other pages within seconds?

How does your contact app manage to find the contact you’re searching for without any delays?

How does Netflix recommend new content to you immediately?

The answer to all the above questions is Data Structures and Algorithms, or DSA.

It shows up when you’re learning programming, preparing for interviews, designing systems, and solving real-world engineering problems. It appears in college lectures, in LinkedIn posts, and in interviews.

With so much attention around it, you would expect every developer to have a solid understanding of DSA. But that’s rarely the case.

And honestly, for most people, DSA feels like a nightmare. The theory is heavy, the problems feel random, and half the time you don’t even know where to begin. If that sounds like you, you’re not alone. Most developers feel exactly this way and just don’t say it out loud.

But here’s something that often gets lost in all the interview preparation advice: DSA is not just an interview topic.

Yes, understanding DSA can help you perform better in technical interviews. But its real value goes far beyond that. Every day, the applications we use rely on data structures and algorithms to store, organize, retrieve, and process information efficiently.

When you search for a contact on your phone, it appears almost instantly. When social media apps load thousands of posts in a smooth, organized feed, there’s a system working behind the scenes to make that possible. These aren’t just product features, they’re practical applications of DSA.

The impact becomes even more obvious when you start building software yourself. Two developers can solve the same problem and get the same result, but the quality of their solutions can be very different. One writes code that continues to perform well as users and data grow. The other writes code that works today but struggles when the application starts to scale.

That’s where DSA makes a difference. It helps you choose the right way to organize data and the right approach to solve problems efficiently.

So this series isn’t about memorizing hundreds of LeetCode solutions. It’s about understanding the ideas behind them, seeing how they apply to real-world software, and building the intuition to recognize when and why a particular approach works.

Let’s break it into two parts:

DataStructure:

A data structure is simply a way of storing and organizing data so that it can be accessed and modified efficiently. Think of it as the container that holds your data.

Algorithm

An algorithm is a set of steps used to solve a problem or accomplish a task. Think of it as the process that operates on the data.

In simple terms:

• Data Structures decide how data is stored.
• Algorithms decide how data is processed.

They two work together. Choosing the right data structure often makes it possible to use a more efficient algorithm.

Still feels a bit hard to picture? here are some things you already use every day that will make it click.

Imagine a spice rack in your kitchen. The spices are arranged in a fixed order, and you look through them one by one until you find the one you need. That’s very similar to how an array works

Now think about your contacts app. You type a name, and the correct contact appears almost instantly without scrolling through every entry. That’s similar to how a hash map works.

And what about a recipe? A recipe gives you a sequence of steps that must be followed in a particular order to achieve a result. That’s essentially an algorithm.

The interesting part is that you’ve already been interacting with concepts like these long before you ever heard the term DSA. Software engineering simply gives them names and uses them to solve problems at scale.

At this point, you might be wondering:

“I’ve already built projects. I write code every day. Things seem to work fine. Why do I need to learn DSA?”

That’s a fair question.

Imagine you need to find a specific user in a database containing one million records. One approach is to check users one by one until you find the right person. In the worst case, that could mean a million comparisons.

Now imagine using a data structure that lets you jump directly to the user you need. Instead of searching through a million records, you find the answer almost instantly.

The result is the same. The experience is completely different.

That’s the difference DSA creates. It’s often the reason one application feels fast and responsive while another feels slow and frustrating.

For people preparing for interviews, DSA is one of the primary ways companies evaluate problem-solving ability. Interviewers aren’t just checking whether your code produces the correct output. They’re looking at how you approach the problem, how efficiently you solve it, and whether you understand the trade-offs behind your decisions.

For developers already working in the industry, the value shows up in the software they build. As applications grow, the choices you make about storing and processing data become increasingly important. A solution that works perfectly for a hundred users can struggle with a million.

Understanding DSA helps you write software that doesn’t just work today, it continues to work when the data grows, the traffic increases, and the complexity of the system expands.

Every data structure exists because it solves a specific kind of problem.

That’s one of the biggest mindset shifts you’ll make while learning DSA. Data structures aren’t arbitrary concepts that someone invented for interviews. Each one was designed to make certain operations faster, easier, or more efficient.

Here’s a quick preview of some of the most common ones:

You don’t need to memorize this table right now. The important takeaway is that every structure has a purpose. As we move through this series, you’ll start recognizing the situations where each one shines.

If data structures are about how you store things, algorithms are about what you do with them. Each type of algorithm is designed to answer a specific kind of question.

• Searching helps you find something efficiently.
• Sorting arranges data into a useful order.
• Recursion solves a problem by breaking it into smaller versions of itself.
• Dynamic Programming avoids repeating work by remembering previous results.
• Greedy Algorithms make the best choice available at each step.
• Backtracking explores multiple possibilities until it finds a valid solution.

At first, these may sound like a collection of unrelated techniques. They’re not. They’re patterns.

And that’s the key idea that makes DSA much easier to learn.

Learning DSA isn’t about memorizing hundreds of algorithms. It’s about recognizing patterns and knowing when to apply them.

Many people approach DSA as a giant list of things to memorize.

That’s usually where the frustration begins.

You don’t need to know every algorithm ever created. You don’t need to memorize solutions to hundreds of problems. What you need is the ability to look at a problem and recognize the pattern hiding underneath it.

Once you start thinking in patterns instead of individual questions, DSA becomes far less intimidating and much more intuitive.

Every chapter in this series will follow the same approach.

We’ll start with a real-world problem instead of a random puzzle.

Then we’ll:

1. Identify the pattern behind the problem.
2. Understand the intuition.
3. Walk through an example step by step.
4. Implement the solution in code.
5. Explore common variations.
6. Learn the signals that tell you when to use that pattern again.

The goal isn’t just to solve one problem. The goal is to train your brain to recognize the same pattern when it appears in a completely different form.

That’s the journey we’re starting together.

Welcome to Episode 0.

Before You Write a Single Line of Code, Let’s Talk About DSA was originally published in Code Like A Girl on Medium, where people are continuing the conversation by highlighting and responding to this story.

Structured Outputs

Python 15.1k 7 issues need help Updated Jul 22

A high-throughput and memory-efficient inference and serving engine for LLMs

Python 86.9k 36 issues need help Updated Jul 22

SGLang is a high-performance serving framework for large language models and multimodal models.

Python 30.6k 15 issues need help Updated Jul 22

Retrying library for Python

Python 8.7k Updated Jul 15

♦

Not that it’s at all new, but I’ve recently discovered piquette, a wine-based beverage that has an ancient and interesting history, if one that flies under the radar.

I picked up a can or two of “P’tit Piquette” at a Quebec-based winery, Little Red Wagon, in Clarendon, which is about 80 kms northeast of Ottawa. But I’ve also noticed it seems to appear in a few other places in eastern Ontario and western Quebec.

Though perhaps primarily a French beverage, what adds an interesting layer of meaning is the drink’s historic role in labour culture that goes back a very long time.

For workers in ancient Roman wineries, the drink was essentially a perquisite of their chores and lucubration: workers were permitted to scoop off the remnants of the primary wine-making process, for which they had sweated and toiled but likely couldn’t afford to buy, in order to imbibe in a second batch.

They would collect the used wine skins, the gnarly stems and seeds and the mushed-up grape viscera — the flotsam and jetsam of the process, if you will — add some water and a dose of some source of sugar and give it all a second ferment.

Perhaps that previous labour relationship is akin to talented cooks today who sweat and toil to prepare and serve the finest (and most expensive meals) at premium restaurants but whose wage likely precludes them from eating such costly food themselves? Piquette-style wines were something the labourers could afford — and make themselves.

Today, the drink itself is a low ABV-bevie that is sparkling in nature — and contributes, you might say, to the “upcycling” and reduced waste of a circular economy in that the pomace is rejuvenated and re-hydrated to re-kickstart the fermentation process.

Mild in flavour, piquette has a bit of fizz to it and a low-alcohol hit for those sipping, but it may be something of an acquired taste, I have to say, similar, perhaps, to low-intervention natural wines, which often have just a touch of funk.

Regardless, it might be something interesting to try. There are some piquette producers in Ontario: Traynor and Tawse; in Quebec: Chateau de Cartes, Lieux Communs and Entre Pierre et Terre as well as Little Red Wagon.

Check out my latest post Piquette: wine leftovers for the “labouring class” from AndrewCoppolino.com.

Regarding Tables 3-3 to 3-6 which describe Total DDT and Dioxins/Furans TEQ (toxic equivalency) generally in Creek Reaches 1-4 except for the last Table which oddly only describes Reach 4 (the Lanxess site). These Tables also represent both surface and subsurface Soils and Sediment readings. Sediments of course are in the bottom of the Creek beneath the water and soils refer to creekbank soils above the waterline. 

Previously mentioned by myself is the fact that in four pages of Tables;  Dioxins/Furans over the four Creek Reaches plus Background (below Reach 1/Grand River) and with 889 samples over many years have an average of 99.87% detection rate. This is beyond incredible, is not remotely normal or ubiquitous and speaks to massive past and ongoing releases of Dioxins and Furans downstream from the Uniroyal/Lanxess property. THIS IS BEYOND SHAMEFUL and no wonder TRAC is so tightly controlled by agenda, membership, meeting times, minutes and limited public access and less.

Total DDT detections are also high although not at the same level of Dioxins/Furans.  The lowest detection rate through five locations is 10% and the highest 100% (twice). The average detection rate in the four Reaches plus Background (Grand River) is 57% . Keep in mind this is for DDT only albeit in both Sediments and Soils both surface and subsurface. This also is not "normal" nor ubiquitous.

Regarding concentrations above health criteria the results are startling. Sediment detections are very high for both surface and subsurface DDT and in fact ALL detections from the highest to the lowest EXCEED the health criteria of .00119 ppm. (parts per million) again for Reaches 1-4 and Background (Grand River). Soil detections for DDT on the other hand while ALL maximum concentrations per area (Reach etc.) EXCEED the health criteria of .078 ppm.; minimum concentrations are all below the health criteria.

Dioxins/Furans maximum concentrations in surface Sediments ALL exceed the health criteria of .85 ppt (Parts per trillion) while only two of five areas (4 Reaches & Background Grand River) of the minimum concentrations exceed the health criteria. Subsurface Sediments maximum concentrations for Dioxins/Furans ALL EXCEED the health criteria whereas only one of five of the minimum concentrations for the five areas exceeds the health criteria. 

Dioxin'Furan Soil maximum concentrations ALL exceed the heath criteria of 7 ppt. whereas 0 of the five minimum concentrations exceed the health criteria. This is the same for both surface Soils and subsurface Soils.  

The title above states that TRAC never do necessary followups to ridiculous presentations. Let me add the following. Maybe they do privately but this is a public process and needs to be clarified to the public each and every time a deceptive, dishonest or blatantly foolish and non factual presentation is made.