._ Bakay Ádám
👋 Hi, I'm

Bakay Ádám

Crafting modern digital experiences with cutting-edge technologies. Specialized in PHP, React, Next.js, and scalable backend solutions.

PHP
Laravel
React
Next.js
Node.js
TypeScript
Docker
Bakay Ádám

About Me

Passionate about creating digital solutions that make a difference
10+

Years Experience

50+

Projects Completed

30+

Happy Clients

10+

Technologies

My Story

I'm a passionate full-stack developer with over 5 years of experience creating innovative web solutions. I specialize in modern technologies like React, Next.js, Node.js, and cloud platforms.

My approach combines technical expertise with creative problem-solving to deliver exceptional digital experiences that exceed client expectations.

Experience

Senior Full-Stack Developer
Tech Solutions Inc.
2021 - Present

Leading development of scalable web applications using React, Node.js, and cloud technologies.

Frontend Developer
Digital Agency
2019 - 2021

Specialized in creating responsive, user-friendly interfaces with modern frameworks.

Computer Science Degree
University of Technology
2015 - 2019

Bachelor's degree with focus on software engineering and web technologies.

My Skills

Technologies and tools I use to bring ideas to life
🎨
Frontend Development

⚛️

React

65%

▲

Next.js

60%

🔷

TypeScript

88%

🟨

JavaScript

95%

🎨

Material-UI

75%

💨

Tailwind CSS

70%

⚙️
Backend Development

🟢

Node.js

65%

🐘

PHP

90%

🔴

Laravel

80%

🍃

MongoDB

65%

🐬

MySQL

85%

📦

MSSQL

80%

🛠️
Tools & DevOps

🐳

Docker

85%

☁️

AWS

75%

📚

Git

90%

💻

VS Code

95%

🎯

Azure

80%

📮

Postman

80%

Always learning and exploring new technologies
Kubernetes
GraphQL
React Native
Vue.js
Python

Featured Projects

A showcase of my recent work and technical capabilities
All
Full-Stack
Frontend
Backend
Web App
Data Viz
E-Commerce Platform
Full-Stack

Modern e-commerce solution built with Next.js, featuring real-time inventory, payment integration, and admin dashboard.

Next.js
TypeScript
Stripe
MongoDB
2.5K
45
Live Demo
Task Management App
Web App

Collaborative project management tool with real-time updates, drag-and-drop functionality, and team collaboration features.

React
Node.js
Socket.io
PostgreSQL
1.8K
32
Portfolio Website
Frontend

Responsive portfolio website with modern design, smooth animations, and optimal performance scores.

Next.js
Material-UI
Docker
Vercel
3.2K
67
API Gateway Service
Backend

Microservices API gateway with authentication, rate limiting, monitoring, and auto-scaling capabilities.

Node.js
Docker
Redis
AWS
1.1K
28
Real-time Chat App
Full-Stack

Modern chat application with end-to-end encryption, file sharing, and video calling capabilities.

React
WebRTC
Socket.io
Express
2.1K
54
Data Analytics Dashboard
Data Viz

Interactive dashboard for data visualization with real-time charts, filters, and export functionality.

React
D3.js
Python
FastAPI
1.7K
39

Let's Work Together

I'm always excited to take on new projects and collaborate with innovative minds
Send me a message

0/1000 characters

Email
bakay.adam@example.com
Follow Me

Latest Tech News

Stay updated with the latest developments in React, Next.js, PHP, and Godot
React
Gutenberg Block Validation Errors and How to Fix Them

Originally published on wow-themes.com. If you're building a custom Gutenberg block and the editor suddenly says "This block contains unexpected or invalid content", this post explains why it happens and how to add dynamic classes and conditional markup without triggering it. For new block developers the error is confusing. You change something small, like adding a wrapper or setting a CSS class from an attribute, and every existing block on the page breaks. I'll use a real example to show what's going on: an offcanvas drawer block whose handle can be a button or an image, and which opens from the left, top, right or bottom. The goal A custom offcanvas drawer block in the block editor. The user chooses where the drawer opens from: left, right, top or bottom. The handle is either a button or an image. The drawer content accepts nested (inner) blocks. Simple on paper. The trouble is all in the validation logic. How block validation actually works A static block stores its HTML in the post content. When the editor opens that post, WordPress takes the block's saved attributes, runs your save() function again, and compares the result with the HTML stored in the database. If they don't match, the editor can't be sure it understands the markup, so it marks the block as invalid instead of silently overwriting it. The Block Editor Handbook's section on validation has the details. That's why the error usually shows up when: you change save() after posts were already saved with the old markup, save() outputs something that differs between runs for the same attributes, or save() renders a component from @wordpress/components, which is built for the editor UI, not for saved markup. edit() is never part of the comparison. It only controls what you see while editing. The problem in our example The block attributes: "attributes": We tried to render the handle like this: <Button className="offcanvas-drawer-handle"> <img src={attributes.handleImage.url} alt="" /> Button> The moment that

Nov 22, 2026
devto
Read More
React
I failed a mock interview I built. Here is how it works

I build Sottava, a job board for engineers that reads about 2,100 company hiring systems every hour. This week I shipped a practice interview, and I tried it first on a real Frontend Engineer (React) posting. I answered "I don't know" to 7 of the 10 questions. The report said: Apply after brushing up. That was the point. A practice interview that only flatters you is useless the day before the real one. Questions from the posting, not a question bank The model reads the posting and your CV and writes 10 questions in three parts: A warm-up about your recent work. Five on what this posting asks for. Each one shows the line of the posting it comes from, and the code checks that the quote really appears in the posting before showing it. Four harder ones: two practical scenarios, working with others, and a mistake you made. Feedback you can read between questions After each answer you get one line on what came through and one on what is missing, plus what a strong answer to this question would cover. When something important is left open, the interviewer asks one follow-up, never more. "I don't know" is an answer Real interviews have questions you can't answer. Here, "I don't know" shows what the interviewer wanted to hear and an honest way to say you haven't done it, from what your CV does show. It never invents experience for you. From gaps to a study plan Every "I don't know" becomes a study page: a few YouTube videos and the right pages of the docs. The links come from a web search, and every one is checked before it is shown: YouTube through its oEmbed endpoint, pages by actually opening them. From memory, the model got 0 or 1 real video IDs per topic, so the check is not optional. The verdict At the end you get a short answer to the question people actually have: is this job worth applying for, and why, judged only from your answers against the posting. No job in mind yet? There is a general practice built from your CV alone, for the role it points to. Numbers A full session is about $0.05 in model calls, so the first practice is free, report included. Try it on a job you actually want: https://sottava.com/jobs. I read every piece of feedback.

Nov 22, 2026
devto
Read More
React
Passkeys in TypeScript: A Zero-Dependency WebAuthn Library for Browser, Node.js and Android

Passwords get phished, reused and leaked. Passkeys (built on the W3C WebAuthn standard) fix that: the private key never leaves the user's device, every login is bound to your domain, and users sign in with a fingerprint, face or PIN. The hard part is the server side. You have to decode CBOR and COSE keys, parse X.509 certificates, check origins, challenges, flags and signature counters, and get every one of those checks right. I built @xkid1/webauthn to handle all of that in one package. It's a zero-dependency, security-first WebAuthn / passkeys library written in strict TypeScript, and it runs in browsers, Node.js, Deno, Bun, Cloudflare Workers, Electron and React Native (Android). xkid1 / webauthn Zero-dependency, security-first WebAuthn / passkeys toolkit for browsers, Node.js, Electron and React Native (Android). Client ceremonies, server verification and Android Credential Manager bridge. @xkid1/webauthn Zero-dependency, security-first WebAuthn / passkeys for every runtime: browsers, Node.js, Electron, React Native (Android) and edge workers. Written in strict TypeScript. Zero runtime dependencies. It ships its own CBOR, COSE, ASN.1/X.509, base64url and UTF-8 code, built only on WebCrypto. Small and tree-shakeable. It is pure ESM with sideEffects: false and separate /client, /server and /android entry points. The client entry is about 10 kB gzipped. Secure by default. It enforces exact origin allowlists, checks challenges in constant time, and makes every challenge single-use. It checks the RP ID hash, UP/UV and BE/BS flags, the algorithm allowlist, signature counters (clone detection) and the 1023-byte credential-ID limit. Its parsers have bounds checks, depth limits and length-bomb protection. Customisable. Every setting has a safe default you can override: algorithms, UV policy, attestation policy and trust anchors, counter policy, timeouts, cross-origin rules, plug-in attestation verifiers, an injectable WebCrypto and clock, a custom… View on GitHub Why another WebAuthn library? Zero runtime dependencies. CBOR, COSE, ASN.1/X.509, base64url and UTF-8 are all implemented in the package, on top of WebCrypto only. No transitive supply chain to audit. Small and tree-shakeable. Pure ESM, sideEffects: false, and separate /client, /server and /android entry points. startRegistration + startAuthentication is about 4.2 kB brotli. Secure by default. Exact origin allowlists, constant-time challenge comparison, single-use challenges, RP ID hash checks, UP/UV and BE/BS flag checks, an algorithm allowlist (RS1 is never accepted), RSA ≥ 2048 bits, signature counter clone detection, and strict, bounds-checked parsers. WebAuthn Level 3. JSON serialisation, hints, passkey autofill (conditional mediation), auto-register (conditional create), getClientCapabilities() and the Signal API. Every attestation format. packed, tpm, android-key, android-safetynet, fido-u2f, apple and none are verified out of the box. Runs everywhere and is SSR-safe. Importing it never touches window, so it works with React, Next.js, Vue, Nuxt, Angular, SvelteKit, Solid and Electron. Install npm i @xkid1/webauthn # or: yarn add @xkid1/webauthn / pnpm add @xkid1/webauthn Entry point Use it in @xkid1/webauthn/client Browser, Electron renderer, WebView @xkid1/webauthn/server Node.js ≥ 20, Deno, Bun, Cloudflare Workers @xkid1/webauthn/android React Native / native Android (Credential Manager bridge) How to add passkey login: the server (Node.js) A passkey flow has two ceremonies, registration and authentication. Each is one request for options and one request to verify. Here's the whole server with Express: import { createWebAuthnServer, MemoryChallengeStore } from '@xkid1/webauthn/server'; verifyRegistration returns plain JSON-friendly values (id, publicKey, counter, transports, deviceType, backedUp, aaguid…), so you can store them in any database without extra encoding. The challenge is stored server-side under sessionKey and deleted the moment it's used, so a replayed response fails. If you'd rather manage challenges yourself, pass expectedChallenge instead. How to add passkey login: the browser On the client, createWebAuthnClient calls the four endpoints above for you: import { createWebAuthnClient, isWebAuthnSupported } from '@xkid1/webauthn/client'; Already have an HTTP layer? Use the low-level functions instead: import { startRegistration } from '@xkid1/webauthn/client'; await api.post('/webauthn/register/verify', { response }); Passkey autofill (conditional mediation) in React Show saved passkeys right in the username field's autofill menu: 'use client'; import { useEffect } from 'react'; import { cancelCeremony, isConditionalMediationAvailable, startAuthentication, } from '@xkid1/webauthn/client'; export The repository has the same recipe for Vue/Nuxt, Angular, Svelte/SvelteKit and Electron. Passkeys in React Native (Android) React Native has no navigator.credentials; Android passkeys go through Jetpack Credential Manager. The /android entry point handles the JavaScript side (JSON normalisation, validation and error mapping), and you supply a small native module: import { NativeModules } from 'react-native'; import { createAndroidPasskeyClient } from '@xkid1/webauthn/android'; On the server, allow the app's signing-key origin and serve Digital Asset Links: import { androidOriginFromFingerprint, buildAssetLinks } from '@xkid1/webauthn/android'; // SHA-256 of your app's signing certificate createWebAuthnServer({ rpId: 'example.com', rpName: 'Example', origins: ['https://example.com', androidOriginFromFingerprint(FP)], }); The README includes a ~40-line Kotlin module you can copy. Errors you can actually act on Every failure is a single WebAuthnError type with a stable code and a hint that tells you how to fix it: import { isWebAuthnError } from '@xkid1/webauthn/client'; catch (e) { // user cancelled throw e; } Messages and hints never include challenges, keys, signatures or user handles, so they're safe to log. On the server, error.toJSON() returns { name, code, message, hint } without the stack, ready to send back from an API. Secure defaults, customisable when you need it Every option has a safe default, and options can only make verification stricter or opt in explicitly. None of them loosens a check silently. import { createAndroidKeyVerifier, createWebAuthnServer } from '@xkid1/webauthn/server'; origins: ['https://example.com'], supportedAlgorithms: [-8, -7, -257], // EdDSA, ES256, RS256 (the default) requireUserVerification: true, attestation: 'direct', trustAnchors: [appleWebAuthnRootDer], requireTrustedAttestation: true, attestationVerifiers: { 'android-key': createAndroidKeyVerifier({ requireTeeEnforced: true }), }, You can also plug in your own challenge store (Redis, a database), your own attestation verifiers, an injected WebCrypto, or a custom clock for tests. How it's tested A software authenticator produces real signed ES256, EdDSA and RS256 responses, so tests exercise actual cryptography instead of canned fixtures. Negative tests for every security check: each tampered input must be rejected with the right error code. End-to-end tests against the packed tarball. CI builds the package, installs it offline into a fresh app (which fails if it has any dependency), and runs registration and sign-in over real HTTP. A separate CBOR encoder is used there so the library never verifies data it encoded itself. Bundle-size budgets enforced in CI, plus benchmarks in Node, Bun, Deno, Chromium, Firefox and WebKit. Verification is fast too: about 5,000 registrations/s and 2,500 sign-ins/s on Node 26. FAQ What is the difference between WebAuthn and passkeys? WebAuthn is the W3C browser API and protocol for public-key authentication. A passkey is a discoverable WebAuthn credential, usually synced across a user's devices by Apple, Google or a password manager. @xkid1/webauthn supports both synced passkeys and device-bound security keys. Does it support FIDO2 and FIDO U2F security keys? Yes. FIDO2 is WebAuthn plus CTAP2, and @xkid1/webauthn is a FIDO2 relying-party library: it creates the options and verifies the responses from any FIDO2 authenticator, such as a YubiKey, Touch ID, Windows Hello or an Android phone. Older FIDO U2F (CTAP1) security keys also work through WebAuthn, and their fido-u2f attestation is verified. Credentials registered with the legacy U2F JavaScript API (appid extension) aren't supported, so users re-register those keys once. Does it work with Next.js, Nuxt and other SSR frameworks? Yes. Importing the package never touches window or navigator, so it's safe in server components and SSR. Call the client functions from the browser only. Can I use it on Cloudflare Workers, Deno or Bun? Yes. The server entry point only needs globalThis.crypto (WebCrypto), with no node:* imports and no Buffer. Do I need attestation? Usually not. The default, attestation: 'none', is the most privacy-friendly choice and fits most consumer apps. Turn on direct attestation with trustAnchors only if you need to know which authenticator model created a credential, for example in enterprise deployments. Does it support iOS? In Safari and WKWebView, yes, through the /client entry point. For React Native on iOS, bridge to ASAuthorizationPlatformPublicKeyCredentialProvider; the server side is identical. Try it git clone https://github.com/xkid1/webauthn.git cd webauthn && yarn install && yarn demo Open http://localhost:5173 to register a passkey, sign in, try passkey autofill, and change every registration and authentication option from the Advanced Settings panel. 📦 npm: @xkid1/webauthn 💻 GitHub: xkid1/webauthn 🔐 Spec: W3C WebAuthn Level 3 It's MIT-licensed and at v0.1.0. Feedback, issues and stars are very welcome. If you add passkeys to your app with it, tell me in the comments! 🚀

Nov 22, 2026
devto
Read More
PHP
The remove.bg API shuts down on December 1: keep your code by changing one URL

remove.bg's standalone site and self-serve API close on 1 December 2026. Every call to https://api.remove.bg/v1.0/removebg stops working that day, including the npm and PyPI wrappers, remove.bg's CLI and the shop plugins built on it. I built Cutmatte, an API that takes the same requests. Migration is two changes: - https://api.remove.bg/v1.0/removebg + https://api.cutmatte.com/v1.0/removebg X-Api-Key: your Cutmatte key Try it with a free preview: curl -H "X-Api-Key: $CUTMATTE_API_KEY" \ -F "image_file=@photo.jpg" -F "size=preview" \ -o result.png https://api.cutmatte.com/v1.0/removebg What stays the same Endpoints, parameters (size, type, format, crop, scale, position, bg_color, bg_image_url, roi, channels, shadow_type=drop), response formats (PNG, JPG, WebP, ZIP, JSON base64), headers and error codes. Tested with the npm remove.bg 1.3.0 package, PyPI removebg 0.4, remove.bg's CLI and the samples from its API page: 34 of 34 checks pass. What is different No 3D or car shadows (a documented 400), type=auto reports other, and the first request after a quiet period takes 15–35 s while a GPU starts, so use a 60 s timeout. Results differ from photo to photo: run your own typical images through the free previews (50 a month) before you switch production. Checklist before 1 December Search code, env vars, CI secrets and no-code tools for api.remove.bg. Record your remaining remove.bg credits: a screenshot is enough for free Cutmatte credits, up to 1,000. Download invoices from your remove.bg account while you can. Point one environment at the new URL and run your usual images through it. Guide with Node.js, Python, PHP and Ruby examples: https://cutmatte.com/migrate/

Nov 22, 2026
devto
Read More
Tech
How does shading analysis improve solar panel layout design accuracy?

Shading analysis improves solar panel layout design accuracy by quantifying how much energy is blocked by obstructions, so row spacing, tilt, string grouping, and inverter choices rest on calculated losses instead of estimates. It replaces assumptions with hour-by-hour irradiance data, which keeps yield predictions and electrical designs aligned with real site conditions. The biggest gains […] The post How does shading analysis improve solar panel layout design accuracy? appeared first on Power Wattz Solar | Off Grid Solar Solutions | Battery Backups.

Nov 22, 2026
pandwsolar
Read More
React
I Built Brickday: A Gamified Productivity App with XP, Levels, Streaks, and Custom Rewards

I've been exploring an interesting question: Can we borrow progression mechanics from games to make everyday productivity more engaging? That exploration resulted in Brickday — a browser-based productivity application that transforms task completion into a simple progression system. Instead of just maintaining a to-do list, users earn experience points, progress through levels, build activity streaks, and redeem custom rewards. The application is now live. Live Demo: https://sadique010.github.io/Brickday/ Product Overview Brickday is built around three primary modules. 1. Task Management and XP Allocation Users can create tasks with a title, description, difficulty, and recurrence schedule. The application supports three difficulty levels: Difficulty XP Easy 10 Medium 15 Hard 20 When a task is completed, the corresponding XP is awarded. Other functionality includes: Creating, editing, and deleting tasks. Pending and completed task views. Daily and weekly recurring tasks. Completion confirmation and a time-limited undo mechanism. 2. Custom Reward Economy Users can define their own rewards and assign an XP cost to each. The reward system uses two separate values: earned: Total lifetime XP accumulated. spent: Total XP redeemed through rewards. The available balance is calculated as: balance = earned - spent This separation is important because level progression depends on lifetime XP rather than the remaining spendable balance. Redeeming a reward therefore affects the available balance without reversing level progression. 3. Profile and Activity Tracking The profile module provides an overview of user progression. It includes: Current level. XP progress toward the next level. Lifetime XP earned. Total tasks completed. Current activity streak. Recent reward redemption history. Monthly activity heatmap. These statistics are derived from the application's persisted state. Implementing the Level Progression I wanted a progression curve that was simple to understand but gradually increased the effort required to advance. The level threshold is calculated using: The application determines the current level by comparing lifetime XP against successive thresholds. For example: Level 1: 0 XP Level 2: 50 XP Level 3: 150 XP Level 4: 300 XP Level 5: 500 XP The progress bar then calculates the user's position between the current and next level thresholds. Handling Recurring Tasks Recurring tasks introduce an additional state-management challenge. A task should be completed only once within its recurrence period, but it should become available again when that period ends. Brickday supports: Daily recurrence. Weekly recurrence, using Sunday as the start of the week. Each recurring task tracks the period in which it was completed. When the current period changes, completed recurring tasks are reset. This allows the same task to contribute to progression again in a subsequent period. Technology Stack I deliberately kept the project lightweight. Technology Purpose HTML5 Document structure CSS3 Styling and responsive layout React 18 Component-based UI HTM JSX-like templating React Hooks State and lifecycle management LocalStorage Client-side persistence The application is currently contained in a single HTML file. React, ReactDOM, and HTM are loaded through CDNs, so there is no build process or package installation required. Data Persistence Brickday currently uses browser LocalStorage for persistence. The application stores its state under: The persisted state includes tasks, rewards, activity records, lifetime XP, spent XP, and redemption history. This makes the application easy to run and deploy without a backend. There are also some deliberate limitations in the current implementation: No user authentication. No cloud database. No cross-device synchronisation. Progress is tied to the browser's local storage. These are important considerations for any future expansion. Design Decisions I wanted the interface to have a distinct visual identity rather than resemble another conventional SaaS dashboard. The design uses: Bricolage Grotesque typography. A soft, colourful visual palette. Strong borders and offset shadows. Difficulty-based task card colours. Responsive layouts. Reduced-motion support. The objective was to make the interface approachable while keeping the actual workflow straightforward. What's Next? Brickday is an early product experiment. The larger question I'm interested in exploring is how game-inspired mechanics can support consistent behaviour without turning productivity into another source of pressure. There is a fine line between making progress rewarding and making users optimise for points instead of meaningful work. That's a design problem worth exploring. Try It Out Live application: https://sadique010.github.io/Brickday/ I'd appreciate feedback, particularly on the progression system, XP economy, and overall user experience. Discussion: Do you think gamification can meaningfully improve personal productivity over the long term, or does it eventually become another layer of distraction? Thanks for checking out Brickday! webdev #react #javascript #productivity #buildinpublic

Nov 22, 2026
devto
Read More