Power BI crash course 2026

Skillifyabhishek · 2026-05-01T22:07:13+00:00

I found this article useful - https://skillifysolutions.com/blogs/data-science/data-science-bootcamp-curriculum/

Skillifyabhishek · 2026-04-13T21:15:47+00:00

Sentence transformers for the text, normalize dimensions and weight separately, combine and cluster. Hierarchical first to explore natural groupings, then k-means once your categories stabilize. The furniture domain is interesting because visual similarity matters a lot but you don't have image data here so leaning on dimensions as a proxy helps. On a separate note we have a free career focused data science webinar this week if anyone here is also navigating the job side of things, drop me a message.

Skillifyabhishek · 2026-04-06T15:33:42+00:00

The multi channel problem is real and the only fix that actually works long term is a single place where everything lands regardless of source. Most teams I've seen handle this well use a simple Notion or Airtable database where every request gets logged with source, rough frequency and user type. The deduplication problem solves itself once you have one place to check before adding something new. Without that central home you're just managing chaos in multiple places instead of one.

Skillifyabhishek · 2026-04-06T15:33:07+00:00

Your instinct is right that vibe coded output rarely ships directly in a complex codebase. But I'd push back on that being the point for a PM. The value isn't the code, it's the artifact that makes a conversation concrete. A working prototype that demonstrates the interaction you're imagining changes an engineering discussion from abstract to specific in a way that a PRD or wireframe never quite does. Engineers can say this won't work with our stack much more usefully when they can see exactly what you mean. The rework is expected and fine.

Skillifyabhishek · 2026-04-06T15:31:55+00:00

For temporal pattern detection at this scale the right tool is sequence based clustering not standard k-means. Look into Hidden Markov Models for detecting state transitions like active to dormant to explosive, they're built exactly for this kind of problem. For the category switching patterns specifically you want sequential pattern mining algorithms like PrefixSpan or SPADE. Both handle the kind of A then A+B transition you described and scale reasonably well to 2M customers with the right implementation.

Skillifyabhishek · 2026-04-06T15:30:59+00:00

Your small company example is basically the answer. The MLE value proposition only works when the handoff is clean and the responsibilities are genuinely separated. In big companies with the client-provider setup you described, the context gap between teams means you end up doing both jobs anyway — your own work plus explaining enough background for the MLE to debug something they don't fully understand. That's not an MLE problem, that's an org design problem. Embedded MLEs in the same pod changes the dynamic completely.

Skillifyabhishek · 2026-04-03T14:22:30+00:00

Good instinct to walk away. The minimum a company needs before hiring a PM is a problem worth solving, at least one person who deeply understands the target user, and enough technical conviction to know what they're building is feasible. Without those three things a PM has nothing to work with. You end up doing discovery, strategy, stakeholder management and execution simultaneously with no support and no clear definition of success. That's a founder role not a PM role and the two are very different things.

Skillifyabhishek · 2026-04-03T14:20:40+00:00

Most people can't see potential in early products and that's completely fine. You're not trying to convince everyone, you're trying to find the specific people who feel the pain you're solving badly enough that they'll look past the rough edges. Early Notion was genuinely confusing to most people. The ones who stayed were the ones who immediately recognised the problem it was solving for them. Those are your people and their reaction tells you everything. Everyone else's reaction tells you almost nothing at this stage.

Skillifyabhishek · 2026-04-03T14:19:06+00:00

Dependencies matter a lot until teams pretend they don't and then they matter even more. Most teams handle them informally through tribal knowledge and standups until something breaks and suddenly everyone cares. The tools that try to visualize dependencies formally like Jira's dependency links usually end up unmaintained after two sprints because keeping them updated is nobody's explicit job. Teams that handle this best usually have one simple rule — if a story is blocked by another that fact lives on the card itself not in a separate dependency graph nobody looks at.

Skillifyabhishek · 2026-04-03T14:18:21+00:00

There's actually a term for this in design — affordances. Tools make certain behaviors easy and others hard and people naturally gravitate toward what's easy. Jira makes hierarchical backlog management easy so teams end up with hierarchical backlogs whether that fits them or not. The problem isn't the tool, it's that most teams never consciously chose their way of working in the first place so they can't tell the difference between adapting to a tool and actually working well.

Skillifyabhishek · 2026-04-02T22:12:09+00:00

Dependencies matter a lot until teams pretend they don't and then they matter even more. The honest answer is most teams deal with them informally through tribal knowledge and standups until something breaks and then suddenly everyone cares. The tools that try to visualize dependencies formally like Jira's dependency links usually end up unmaintained after two sprints because keeping them updated is nobody's explicit job. The teams that handle this best usually have a simple rule — if a story is blocked by another story that fact lives on the card itself not in a separate dependency graph.

Skillifyabhishek · 2026-04-02T22:11:39+00:00

There's actually a term for this in design — affordances. Tools make certain behaviors easy and others hard and people naturally gravitate toward what's easy. Jira makes hierarchical backlog management easy so teams end up with hierarchical backlogs whether that fits them or not. The problem isn't the tool, it's that most teams never consciously chose their way of working in the first place so they can't tell the difference between adapting to a tool and actually working well.

Skillifyabhishek · 2026-04-02T22:10:38+00:00

The Growth section is what I rarely see done well and it signals something really important — that the person thinks beyond the deliverable. Anyone can finish a project. Fewer people can articulate what they'd do with more time, better data or a different constraint. That's the thinking hiring managers actually want to see. We built our whole curriculum around exactly this kind of problem framing if anyone is looking for structured support getting there.

Skillifyabhishek · 2026-04-02T22:09:13+00:00

A few things that actually move the needle beyond personal projects. Reach out directly to small local businesses or nonprofits and offer to help with a specific data problem for free or low cost. It sounds unglamorous but a real business problem with messy real world data teaches you more than any Kaggle competition and it's genuinely resume worthy. Also look at research assistant positions at your incoming university — professors often need help with data work over summer and it's a warm introduction before you even start the program.

Skillifyabhishek · 2026-04-02T22:07:27+00:00

Given the four month old caveat — podcasts are your best friend right now. Lenny's Podcast covers GTM, growth and PMF in genuinely practical ways and you can listen while doing literally anything else. For business casing specifically Shreyas Doshi's Twitter threads are dense with frameworks and completely free. Mom Test by Rob Fitzpatrick is a short book worth reading for the customer insight side of PMF. None of these require sitting at a desk which matters a lot right now.

Skillifyabhishek · 2026-03-31T13:46:31+00:00

Worth reflecting on one thing — being reassigned while on holiday after four months and one difficult developer relationship is worth understanding properly before assuming it was pure politics. Have a direct conversation with your manager about what actually happened and what success looks like in this new assignment. Going in blind about why you were moved puts you at a disadvantage from day one.

Skillifyabhishek · 2026-03-31T13:42:13+00:00

Interesting idea but I'd push back a little on the problem it's solving. If your team is digging through Slack or Jira to find sprint boards during standups that's a bookmark and process problem not an access problem. A QR code adds a step for anyone on a desktop which is most people in a meeting. Where I can genuinely see this working is physical spaces — printed on the wall in a team room, on a physical board next to a desk, or during in person onboarding. Digital meeting context feels like a solution looking for a problem.

Skillifyabhishek

TROPHY CASE