Kalina Zografska

I am excited to share that I have successfully passed the Professional Scrum Product Owner I (PSPO I) certification from Scrum.org. This certification validates my knowledge of the Scrum framework and my ability to support and enable value creation and delivery. Earning PSPO I shows my understanding of how to bridge the gap between strategy and agile product management in order to create valuable products using Scrum.

15

1 Comment

BDD is the only sustainable TDD I’ve ever done in my career. I've done a lot (LOT) of unit testing. Almost all of it falls into a couple of categories: - Figure out an implementation, then create a test afterwards - Or a variant: figure out the happy path, then unit test all the ways it could go bad - Discover a bug, fix it, write a test to pin it down for the future Which are all good! I love unit tests. It's just that I've most often seen them written after the code was built and guided by the implementation as opposed to guiding the implementation. But I've actually done BDD for extended times on real projects where our first move was to start by writing the tests first - and it is wonderful. You have a real sense of what needs to be done next - you're either staring at an empty step definition that needs to be written (i.e. a new test), a currently failing step you need to fix, or a bunch of green lights that will watch your back on a refactor.

6

2 Comments

I am excited to share that I have successfully passed the Professional Scrum Product Owner I (PSPO I) certification from Scrum.org. This certification validates my knowledge of the Scrum framework and my ability to support and enable value creation and delivery. Earning PSPO I shows my understanding of how to bridge the gap between strategy and agile product management in order to create valuable products using Scrum.

9

1 Comment

I am excited to share that I have successfully passed the Professional Scrum Product Owner I (PSPO I) certification from Scrum.org. This certification validates my knowledge of the Scrum framework and my ability to support and enable value creation and delivery. Earning PSPO I shows my understanding of how to bridge the gap between strategy and agile product management in order to create valuable products using Scrum.

25

6 Comments

Hey Scrum Masters ! Curious about "TDD" and "BDD" in your DevOps talks? Let's simplify these terms! TDD (Test-Driven Development): Developers first write a test for a new function, then the code to pass the test, and refactor as needed.  Repeat for perfection. Benefits of TDD: ✅ Guarantees code quality.   ✅ Serves as live documentation.   ✅ Facilitates easy updates.   ✅ Promotes clean, modular design. BDD (Behavior-Driven Development): Starts with defining expected behavior in simple language, followed by tests, then coding.  Involves everyone from developers to business folks. Benefits of BDD: ✅ Enhances team communication.   ✅ Aligns development with business needs.   ✅ Clears up any confusion. Let’s integrate TDD and BDD into our Agile development to level up our teamwork and output! 📈 Want to deep dive? 𝐂𝐡𝐞𝐜𝐤 𝐨𝐮𝐭 𝐨𝐮𝐫 𝐀 𝐭𝐨 𝐙 𝐒𝐜𝐫𝐮𝐦 𝐓𝐨𝐨𝐥𝐤𝐢𝐭-  https://lnkd.in/gpS_qQ8r #agilecoaching #scrum #scrummaster #agilecoach #agile‍‍‍‍‍‍‍

61

4 Comments

Alright, it's a little behind schedule, but v4.15.0 of Nebula Logger is now available! This release brings several new features & bugfixes to the managed package (as well as few small enhancements to the unlocked package). Some of the highlights for anyone upgrading from v4.14.0 to v4.15.0: Key Features ✅ OmniStudio Logging: Built-in support to easily log from OmniStudio, a much-requested feature! ✅ Loosely-Coupled Dependencies: ISVs and consultants can now seamlessly leverage Nebula Logger without requiring it as a dependency. ✅ Enhanced JavaScript Logging: A new getLogger() function makes JavaScript logging even easier & provides improved support for logging in LWC lifecycle events Other Enhancements ℹ️ Dynamic highlights and related list components for flexipages, leveraging Salesforce's Winter '25 features. ℹ️ New list views and formula fields on logging objects, improving usability and visibility. ℹ️ Apex updates for better HttpRequest logging, async context handling, and more flexible LogEntryEventBuilder methods. ℹ️ Optimized internal performance and streamlined sf CLI commands to align with Salesforce’s latest standards. Bugfixes 🐞 Enhanced regular expressions for data masking sensitive info (e.g., SSNs). 🐞 Fixes to Apex context handling, long code snippets, and visibility rules on console tabs. More details are available in the release notes: https://lnkd.in/eBKVkfZr #Observability #Logging #Salesforce #SalesforceAdmins #SalesforceDevelopers #SalesforceArchitects #OpenSource #Apex #OmniStudio #ISV #LWC

93

7 Comments

QUESTION: should you assume that just because your prospect is in a regulated industry they are "following the STANDARD"? ... Answer: in my experience, no. You shouldn't. Because behind the term "regulated industry" there is a fair variety of situations. You are in #Avionics and write software that gets onto planes? Best to follow #DO178C or you won't fly. Unless you are in military projects. There, the line becomes murkier. DO-178C, sure, but only to a point. FDA Cybersecurity Guidelines or Principle of Software Validation (#medicaldevices )? Still enforced by the government, but with a less prescriptive text. Expect some variations. Automotive's #ISO26262? Auto-regulation. In my experience, the variation is even greater. So, whether you are in #sales or the technical counterpart in #presales, no you should not assume they are following the standard the way YOU would do it. Which doesn't mean that there is no space for evangelization. Quite the contrary, in fact!

2

I am excited to share that I have successfully passed the Professional Scrum Product Owner I (PSPO I) certification from Scrum.org. This certification validates my knowledge of the Scrum framework and my ability to support and enable value creation and delivery. Earning PSPO I shows my understanding of how to bridge the gap between strategy and agile product management in order to create valuable products using Scrum.

15

2 Comments

Hey Google, when I Google, I want you to Google. ➡️ Keep my original query, at all times. Never translate, or even worse, rewrite it. ➡️ Keep interface language and query language separated, at all times. Just because my interface language is Dutch, doesn't mean I want my output in Dutch. This was really straightforward when you did just Search. But now with GenAI taking over, you're conflating the 2, big time. ➡️ Show. Me. Websites. Google has turned into my number 1 source checker. It's where I go to when ChatGPT tells me to always check stuff myself. So please show me endless lists of search results. Thanks from someone who still remembers your very first user interface: an empty page and a search box 💜 #heygoogle #propersearchisstillabusinesscase

70

16 Comments

I published my first blog post about statically deobfuscating the Lazy Importer. Please check it out and don't forget to let me know your thoughts. Blog Link: https://lnkd.in/eW-9QV_2 .

4

In 2021, I tried to understand how tech compensation really works - at least in the Netherlands. I published "the trimodal nature of software engineering salaries" article. Time for an update: Back then, based on ~100 data points (and my own experience as a hiring manager,) I suspected that there are three, distinctively different compensation bands for software engineers: 1. Local companies (Tier 1) Most local businesses that benchmark to the numbers on most salary comparison sites. They usually offer close to – and sometimes slightly above – what government positions advertise for senior engineering roles. 2. Ambitious local companies (Tier 2) Startups, scaleups, and more ambitious local companies that want to hire and retain the best people, locally. 3. Companies benchmarking across a region (Tier 3). Big Tech companies, hedge funds and scaleups that hire across regions, frequently hire from abroad, and often compete with fellow Big Tech giants for talent. Curiously, the third tier (Tier 3) seemed to be missing from most public compensation data sources. Since publishing the model, I've both received lots of feedback suggesting it applies to the US, Canada, UK, Europe and many other countries. I've since then also collected far more data points, manually tagged companies by tier, and can finally confirm that yes, this model holds up when compared with actual data. Here is the longer analysis (and the stats behind this graph below) in yesterday's The Pragmatic Engineer issue. Read it here: https://lnkd.in/e7FV4gBB

708

43 Comments

In Tendermint Consensus there are three main steps 1: Prevote 2:PreCommit 3:Commit Tendermint consensus use Aura algorithm for block authoring and secondly block goes into finalise state. Secondly its forkless and most importantly if block is not finalised in given time then it throws out and all transactions are again sent to transaction pool and will execute again. #substrate #polkadot #rust

3

🚀 Exciting News for Developers! Join us on Friday, November 15th for an in-depth session on the upcoming new major version of the Fluent UI Blazor library. This release brings groundbreaking Web Components and major architectural innovations to take your web development to the next level. With Vincent Baaij https://www.dotnetconf.net 🔍 What to Expect: Overview of New Features: Explore the latest enhancements, including cutting-edge Web Components. Architectural Changes: Understand the performance, scalability, and maintainability improvements in the new architecture. Migration Guide: Yes, there will be breaking changes! But we’ll guide you with practical tips and best practices to smoothly transition your projects. Hands-On Demos: Watch the new features in action with live coding demonstrations. 📅 Don’t miss out! Mark your calendar and get ready for this transformative session. #Blazor #FluentUI #WebDevelopment #WebComponents #Architecture #Migration #LiveCoding #TechTalk #WebInnovation

38

2 Comments

This is, hands down, the best book I ever read about agile transformations. By far. Unlike in way too many other publications, the authors do not prattle about meta challenges and high-level concepts. They explain problems and provide approaches how to move from "Plan-Do" to "Envision-Evolve". And above all, they always cycle back to the key challenge: Being able to respond to your customers’ needs – quickly. Because that’s why we do this, not because we want to have a very beautiful scrum implementation. Go ahead and take a look into it, especially if you are in a leadership position. I found it very valuable. EDGE - Value-Driven Digital Transformation. By Jim Highsmith, Linda Luu, David Robinson.

36

3 Comments

Today we are talking about autotesting. About pains and issues, and especially about solutions. Enjoy! https://lnkd.in/et7rvrgQ #magento #software #graphql #postman Postman

23

Resharing this as endorsement - tech compensation is *at least* bimodal, and likely trimodal (depending on your location). This article is a great read for all engineers, to help explain the market and know their worth. I saw this firsthand in my job search last year. There were local companies in the Chicago area that capped out at ~120-160k for senior roles, and then larger firms (especially in finance and tech) that reached ~180-200k. But it wasn’t until I got into interviews with large public tech companies that I saw base salaries of 200k+ advertised, and total compensations reaching from 250k to 500k and up! Gergely Orosz's articles on this topic have been a huge help to me. If I had stuck to what I saw in the local market, I would've drastically limited my options and short-changed myself. The surge in remote work has made it more possible than ever to work for some of the best companies in the world, and even with lots of return-to-office happening, there are still plenty of great and well-paying companies out there. So if you're on the market (or thinking about it), keep this in mind! 🚀

6

Developers these days are so darned lazy. And cheap. OK, sorry, that was not fair. Developers have always been lazy and cheap. I was really surprised by this when I started out as a software developer, fresh out of college 25 years ago. I noticed that whenever my more experienced colleagues were asked to add new functionality, the first thing they did was to check if there was pre-existing code that did the job. Preferably free. This blew my mind. But as I thought more about it, it made sense. Especially after I attended a Business Strategy class at Southern Methodist University SMU Cox School of Business. Build vs Buy vs Reuse is a part of Business Strategy. Why build or buy something if it is freely available? When we start with something good-enough that is freely available, we can customize it to our needs. And if it is well-maintained, we get free upgrades. This frees up more time and money for us to build things that no one else can build as well as us, which makes customers very happy. It reduced the TCO (total cost of ownership) of our solutions and it increases our EBITDA, which usually makes investors very happy, which makes the board of directors very happy. So it turns out that developers are not only lazy and cheap, but they are also strategic and there is a lot we can learn from them. Especially when it comes to building Software Product Development Lifecycles. You may be tempted to reject the pre-existing frameworks and build your own because none of them are good enough for you. Newsflash! You might think you are unique and special and nobody is solving the specific kinds of problems you are. Maybe yes, maybe no. You are just as unique as every other snowflake. And while you might be doing something nobody else has done before, you don't need to develop your own SDLC. Think like a developer. Be lazy, cheap and strategic. Start with a pre-existing framework, make use of all the free training available on the market, and customize only what you need to. Your EBITDA will go up and your customers, investors and Board of Directors will be happy. You are welcome.

14

4 Comments