5 exercises — using notably/importantly/crucially/interestingly/significantly and other stance markers correctly in tech blog posts, RFC discussions, performance reports, and post-mortems.
0 / 14 completed
1 / 14
A tech blog post states: "_____, the team chose to migrate to a microservices architecture before establishing proper service boundaries." Which stance marker best signals that this decision was surprising or counterintuitive?
Option C is correct."Interestingly" is an attitudinal stance marker — it signals the writer's evaluation that the information is surprising, noteworthy, or counterintuitive. It frames the reader's expectation before they process the content. "Importantly" and "significantly" are evidential/evaluative stance markers that signal relevance or magnitude, not surprise. "Crucially" signals high stakes or criticality. Choosing the right stance marker depends on what attitude the writer wants to project: surprise (interestingly), significance (importantly), criticality (crucially), or magnitude (significantly).
2 / 14
An RFC discussion comment states: "_____, this implementation does not handle the case where the token has already expired at the time of validation." Which stance marker most appropriately signals a critical gap that must be addressed?
Option C is correct."Crucially" signals that the information is of high criticality — it must be addressed, not merely noted. In RFC discussions and technical reviews, "crucially" is appropriate when identifying a gap or issue that could affect correctness, security, or interoperability. "Notably" (option B) would downplay the severity. "Interestingly" (option A) is too light for a security-relevant gap. "Surprisingly" (option D) expresses personal emotion and is too informal for standards-track documents. In technical contexts: crucially > importantly > notably for escalating urgency.
3 / 14
A performance report states: "_____, the new indexing strategy reduced average query time by 78%." Which stance marker is most appropriate for presenting a measured, quantified result?
Option B is correct."Significantly" is the best choice for quantified performance findings because it signals that the result is large in magnitude — consistent with the 78% figure. It is an evidential stance marker that frames the result as statistically or practically meaningful. "Interestingly" (option A) would suggest the writer finds the result unexpected, which may not be appropriate in a formal report. "Crucially" (option C) implies the finding is a decision-making inflection point — potentially true, but the primary frame is magnitude, not criticality. "Notably" (option D) is weaker and slightly informal for a report with precise figures.
4 / 14
A technical blog post about database design states: "_____, many teams implement a shared database schema for microservices, which directly undermines service autonomy." Which stance marker signals that this is a significant observation the reader should pay attention to?
Option A is correct."Notably" is well-calibrated for a technical blog post observation: it signals "this is worth paying attention to" without overstating urgency ("crucially") or implying the reader should already know ("obviously"). Stance markers should match the genre and audience. In a blog post, "notably" introduces a surprising or important pattern without being alarmist. "Obviously" and "basically" (options C and D) are problematic in technical writing: "obviously" can alienate readers who do not find it obvious; "basically" signals over-simplification.
5 / 14
An engineering post-mortem states: "_____, the on-call alert fired 40 minutes before the service degradation became customer-visible." Which stance marker most accurately frames this as positive and unexpectedly early?
Option C is correct."Encouragingly" is an attitudinal stance marker that signals the writer's positive evaluation of the finding. In post-mortems, presenting early-warning successes with "encouragingly" models good incident culture — it acknowledges what worked well. "Importantly" (option B) would flag significance without the positive dimension. "Significantly" (option D) quantifies magnitude. "Unfortunately" (option A) is the wrong polarity entirely. Post-mortems benefit from calibrated stance markers that distinguish between problems ("alarmingly", "critically"), neutral observations ("notably", "interestingly"), and positives ("encouragingly", "promisingly").
6 / 14
John (Lead Engineer) sent this Slack message to the team after discovering a bug: "I'm genuinely surprised that the authentication flow is failing with anonymous users. We've explicitly tested this path."
The word 'surprised' is a strong stance marker indicating disbelief or disagreement with an assumption. 'Unexpected' would be too general. 'Problematic' focuses solely on the negative consequence, while 'urgent' implies immediate action without acknowledging the root cause. This choice highlights John's feeling that something went wrong despite their efforts.
7 / 14
David (API Developer) drafted this PR description: "Based on our recent performance testing, we've implemented a new caching layer that reduces API response times by approximately 65% for common queries. This represents a substantial improvement."
'Remarkable' is a suitable stance marker when presenting quantifiable performance improvements. It emphasizes the positive outcome. 'Negligible' would diminish the achievement, and 'questionable' introduces doubt without supporting evidence. The description clearly frames the caching layer as a success.
8 / 14
John (Lead Engineer) sent this Slack message to the team after discovering a bug: "I'm genuinely surprised that the authentication flow is failing with anonymous users. We've explicitly tested this path."
The word 'surprised' is a strong stance marker indicating disbelief or disagreement with an assumption. 'Unexpected' would be too general. 'Problematic' focuses solely on the negative consequence, while 'urgent' implies immediate action without acknowledging the root cause. This choice highlights John's feeling that something went wrong despite their efforts.
9 / 14
David (API Developer) drafted this PR description: "Based on our recent performance testing, we've implemented a new caching layer that reduces API response times by approximately 65% for common queries. This represents a substantial improvement."
'Remarkable' is a suitable stance marker when presenting quantifiable performance improvements. It emphasizes the positive outcome. 'Negligible' would diminish the achievement, and 'questionable' introduces doubt without supporting evidence. The description clearly frames the caching layer as a success.
10 / 14
Sarah, a junior developer, posted this comment on a code review: "I'm honestly concerned that the error handling isn't robust enough for unexpected input. We should definitely add more checks."
The phrase 'I'm honestly concerned' is a strong stance marker indicating a degree of dissatisfaction with the code. It goes beyond simply stating a problem; it conveys genuine worry about its implications. The other options – insufficient, uncertain and worried – lack the direct emotional expression that defines this marker's impact. This reflects a desire for proactive change.
11 / 14
Mark, an API developer, sent this message in a Slack channel: "Frankly, I think this API endpoint is needlessly complex. We could simplify it significantly without impacting functionality."
'Frankly' is a classic stance marker used to inject a degree of directness and judgement into an opinion. It signals that Mark isn't just stating a preference; he's presenting it with a clear, potentially challenging tone. The other options – neutral, skeptical, and reflective – lack this element of assertive critique. Using 'frankly' is appropriate for constructively questioning design decisions.
12 / 14
Emily drafted this PR description: "As a result of the recent performance bottleneck identified in service X, we've implemented a new queueing mechanism. This should improve throughput by an estimated 30%."
'As a result' is a crucial stance marker that highlights the causal relationship between the identified bottleneck and the implemented solution. It demonstrates that the change was directly driven by a problem. The other options – informative, suggestive, and objective – don't convey this sense of consequence or justification. This phrasing strengthens the rationale behind the PR.
13 / 14
Tom, a senior engineer, posted in a standup update: "To be honest, we're still struggling with the integration of module Y into the main workflow. It's proving more challenging than anticipated."
'To be honest' is a very common stance marker used to preface admissions of difficulty or problems. It signals openness and transparency about the team's challenges, fostering trust and collaborative problem-solving. The other options – formal, reserved, and detached – would be less suitable in this context, as they lack the directness needed for an honest update.
14 / 14
Lisa wrote this comment in a code review: "Given the limitations of our current infrastructure, it's unlikely we'll be able to achieve optimal performance with this approach. We should explore alternative solutions."
'Given' establishes a conditional relationship between the constraints of their environment and the feasibility of the proposed approach. It frames the decision as one made *because* of those limitations. This is a strong stance marker indicating that the current solution isn't viable due to external factors. The other options don't capture this crucial element.
What will I practise in "Stance Markers in Technical Writing — Grammar Exercise"?
Practise using notably, importantly, crucially, interestingly, and significantly correctly in tech blogs, RFC discussions, and technical reports. 5 exercises.
How many exercises are in this module?
This module has 14 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the grammar rule and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Grammar exercises?
Browse the full Grammar hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain grammar rules in prose; this exercise tests and reinforces those rules through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.