SINGAPORE EVENT GUIDES
A career change, a new hobby, a few people who share your interests. Start with what you need, then work out which events are worth your time.
Search upcoming events →559 guides in total · Showing 37–65 of 65 in technical communities
Choose the situation that fits what you need.
UX researcher testing form recovery
Follow the submitted, rejected and corrected states so a critique can see whether the person understands the error and retains unrelated work.
UX researcher checking persistent field context
Inspect the filled state so the field’s purpose remains understandable when its placeholder is no longer visible.
UX researcher reviewing visual information
Use the reader’s task to distinguish essential visual information from decoration, and prepare a comparison that can be reviewed without the image.
Product manager evaluating a restricted demo
Trace the demonstrated step, each dependency’s actual state and the observation still missing before calling a prototype an end-to-end service.
Product manager clarifying a final action
Define the successful action’s actual state, recipient and editability, then critique the complete flow with neutral predictions rather than treating a preferred button label as proof of understanding.
Analyst plotting incompatible coordinates
Prepare a small map example that distinguishes the source coordinate system, parameter names and output format before blaming the chart.
Developer displaying a nearby address
Review the meaning of a reverse-geocoding result before using its first building as the location people should visit.
Analyst handling unnamed buildings
Inspect field-level missing values before deleting location records or inventing names to make a map look complete.
Developer distinguishing failed and empty lookups
Review controlled result, valid-empty and failure examples so an unsuccessful lookup does not tell users that the data is absent.
Junior developers with a bug too large to explain
Prepare a permitted small replay with expected and observed behaviour, preserve what reduction changes, and ask a clinic for one diagnostic next step.
Junior developers whose API demo loses records
Distinguish a successful request from a complete dataset and prepare a pagination question peers can reproduce.
Junior developers seeking useful review of a small change
State the behaviour a small change must protect, compare cases that expose a wrong version, and keep local test evidence separate from upstream guarantees and project acceptance.
Spreadsheet users investigating mismatched report totals
Compare the question, row unit, input version, period and exclusions behind two totals, then retain the definition and the evidence still missing before refining the chart.
Analysts whose saved report changes on refresh
Choose learning sessions that help explain when data was collected and why a saved number can differ after refresh.
Spreadsheet learners whose merge inflates a total
Use two fixed fictional tables to show the intended matching rule, expected row count and repeated amount before asking for help with a join or merge.
Developers choosing their first practical security format
Compare the task, help and feedback actually offered, then choose an authorised practice format whose evidence answers your learning question.
Developers exploring incident coordination
Map an observation, the explanation still unknown and the role owning the next question, then retain what changed during a permitted fictional tabletop.
UX researchers worried their case overstates a small study
Show recruitment, task conditions and assistance beside a limited study’s observations, then separate a defensible finding from a broader recommendation.
UX researchers with a persuasive but ambiguous journey map
Make each journey-map interpretation traceable to a permitted observation, an alternative explanation and the check still missing.
UX practitioners choosing between two different research questions
Read a prototype task result beside its instructions and assistance before treating it as evidence that somebody would adopt the product.
Cloud engineers whose release plan lacks a rollback decision
Compare a stated failure condition with the components an authorised practice reversal actually restores, then record the state still different or unexamined.
Cloud engineers with dashboards but unclear alert ownership
Follow a defined task failure from the supplied signal to its recipient, next evidence question and authorised owner, while keeping repeated notifications and unresolved causes separate.
Robotics engineers whose search results target business adoption
Match the participant role, intended output and permitted material to the question you need answered before choosing adoption discussion, a supplied exercise or technical peer review.
Robotics builders comparing a bench demo with an operating task
Record what the demonstration actually showed, compare its conditions with one operating task and prepare a bounded acceptance question without inventing a pass threshold.
Climate technology practitioners evaluating a pilot comparison
Trace totals, delivered work and changed conditions before attributing a pilot result to the technology.
Technical practitioners asked to turn an energy demo into an emissions claim
Keep a component measurement separate from the wider environmental statement it is being used to support.
Junior developers whose dataset download produces a message
Trace preparation, file access and parsing separately before changing your CSV reader.
Junior developers moving a public-data exercise between environments
Treat the service domain and selected dataset as one environment-specific configuration.
Spreadsheet learners whose period labels became exact dates
Ask what a row represents before turning a month or quarter label into a day on a chart.