SShortSingh.
Back to feed

Raslak Hub adds automatic clock-in for construction crews using site geofences

0
·2 views

Raslak Hub, field software for construction and service firms, lets workers clock in and out automatically when their phone detects arrival at or departure from a project site. The developers, who test the system with their own Helsinki construction crew, built it to stop unbilled hours caused by manual timesheets that workers estimate at week's end. Site locations come from supervisor-set coordinates, street addresses, or the average of past clock-ins, and the default geofence radius is generous at 600 metres to avoid false clock-outs caused by poor GPS. Short visits, brief gaps, and trips like fetching tools are filtered out, while automatic entries stay correctable and require supervisor approval before payroll or invoicing. Location tracking is opt-in, and manual two-tap clocking remains available.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Blockchain bootcamp chapter 3: running a local node with Ganache

This chapter of a blockchain bootcamp series shows developers how to run a local blockchain node for free, disposable testing. It follows Emma, a front-end engineer tasked with building a block-viewing widget, who struggles with dense documentation and a slow testnet setup. The lesson recommends Ganache, a development tool for Ethereum and similar platforms, and requires Node.js 16 or higher. Readers install Ganache via npm and start a node that provisions pre-funded test accounts. The chapter then moves on to building a short script that connects to the node using the Web3.js library.

0
ProgrammingDEV Community ·

Why Sidebar Icons Look Uneven Even at Identical Sizes

Setting every sidebar icon to the same 24 × 24 dimensions does not ensure they look visually consistent. Icons can differ in internal padding, silhouette shape, and detail density, so some appear heavier or smaller than others. Stroke thickness, corner style, and fill approach also affect how balanced the icons feel side by side. The article recommends auditing the artwork itself before adding CSS overrides, and choosing a single icon family that covers all required navigation concepts. It also offers a sample sidebar component using flex sizing and currentColor to keep icons predictable.

0
ProgrammingDEV Community ·

Managing LLM API Rate Limits: Handling TPM, RPM, Retries and Fallbacks

A DEV Community piece highlights the importance of rate limits when an application works with multiple LLM APIs. It explains that limits on tokens per minute (TPM) and requests per minute (RPM) must be tracked carefully. The article points to retry logic and fallback models as key tools for avoiding failed requests. Properly handling these factors, it argues, helps applications keep running smoothly.

0
ProgrammingDEV Community ·

MCP server publishes failing scores on a public lost-response retry contract

A developer team scored its own MCP server against a public test contract for handling lost responses after mutating tool calls. The contract addresses MCP issue #3394, which reports that retrying a mutating call can re-execute external effects. The scoring was published before the run, and each assertion is graded separately as pass, fail, or unproven, with no aggregate score. The team's own baselines show failures, including a production run that produced two effects for one logical operation and a mismatched-parameter retry that executed as a normal new call. The contract is a draft under joint review with an external collaborator and is designed for independent reproduction by anyone.