https://jsokit.com/blog/tags/generator/ Recent content in Generator on JsonKit Blog Hugo en © 2025 JsonKit Sun, 10 May 2026 17:07:26 +0000 https://jsokit.com/blog/posts/uuid-generator-algorithms-from-v1-to-v4-implementation/ Sun, 10 May 2026 17:07:26 +0000 https://jsokit.com/blog/posts/uuid-generator-algorithms-from-v1-to-v4-implementation/ UUID Generator Algorithms: From v1 to v4 Implementation Building a distributed system recently, I needed globally unique IDs. Started with auto-increment database IDs, then hit a wall with sharding—different databases would generate conflicting IDs. After some research, I went with UUID. Here’s what I learned. What is UUID? UUID (Universally Unique Identifier) is a 128-bit unique identifier, typically shown as a 36-character string: 550e8400-e29b-41d4-a716-446655440000 The format is 8-4-4-4-12, separated by hyphens. https://jsokit.com/blog/posts/building-a-tailwind-css-class-name-generator-from-string-concatenation-to-visual-builder/ Tue, 05 May 2026 20:05:30 +0000 https://jsokit.com/blog/posts/building-a-tailwind-css-class-name-generator-from-string-concatenation-to-visual-builder/ Building a Tailwind CSS Class Name Generator: From String Concatenation to Visual Builder What’s the most painful part of writing Tailwind CSS? It’s not memorizing class names—it’s debugging a long string like flex justify-center items-center p-4 bg-blue-500 and not knowing which class is taking effect or which one is being overridden. Today let’s build a visual Tailwind class name generator that turns class assembly into building blocks. Core Design: State-Driven, Not String Concatenation Many people’s first instinct is string concatenation, but a better approach is using a Set for state management: https://jsokit.com/blog/posts/table-generator-implementation-from-data-editing-to-multi-format-output/ Tue, 05 May 2026 17:05:30 +0000 https://jsokit.com/blog/posts/table-generator-implementation-from-data-editing-to-multi-format-output/ Table Generator Implementation: From Data Editing to Multi-Format Output When writing technical documentation, I often need to insert tables. Hand-writing Markdown tables is manageable, but converting to HTML or CSV is tedious. Let’s build a tool that edits once and outputs in multiple formats. The Essence of Three Table Formats Markdown Tables: Pipe-Separated | Name | Age | City | | --- | --- | --- | | John | 30 | NY | | Jane | 25 | LA | The core is using | to separate cells, with the second row as the separator line (alignment). https://jsokit.com/blog/posts/building-a-sitemap-generator-xml-structure-and-seo-best-practices/ Fri, 01 May 2026 18:59:48 +0000 https://jsokit.com/blog/posts/building-a-sitemap-generator-xml-structure-and-seo-best-practices/ Building a Sitemap Generator: XML Structure and SEO Best Practices I was doing SEO optimization for my blog recently when Google Search Console kept complaining about my sitemap. Opening sitemap.xml, the format was fine, but the configuration was a mess: every page had priority 1.0, changefreq was always “always”—basically telling search engines “this whole site is spam.” So I built my own sitemap generator and dug into the technical details and SEO best practices. https://jsokit.com/blog/posts/rest-api-documentation-generator-from-manual-maintenance-to-one-click-automation/ Wed, 29 Apr 2026 17:07:25 +0000 https://jsokit.com/blog/posts/rest-api-documentation-generator-from-manual-maintenance-to-one-click-automation/ REST API Documentation Generator: From Manual Maintenance to One-Click Automation Every backend developer knows this pain: the API changed but the docs didn’t; new team members stare at outdated documentation in confusion; during integration, parameter descriptions turn out to be the exact opposite of actual behavior. Manually maintaining API docs is not only time-consuming—it’s inherently prone to drifting out of sync with the code. Let’s talk about how a REST API documentation generator solves this problem, and dive into the technical implementation details. https://jsokit.com/blog/posts/building-a-visual-regex-generator-from-zero-to-match/ Tue, 28 Apr 2026 14:26:37 +0000 https://jsokit.com/blog/posts/building-a-visual-regex-generator-from-zero-to-match/ Building a Visual Regex Generator: From Zero to Match Regular expressions are powerful but notoriously hard to remember. Even experienced developers need to look up syntax for email validation or IP matching. I built a Regex Generator to make this easier. Here’s how it works. The Problem with Regex Cryptic syntax: \d, \w, \s are manageable, but (?=...), (?:...), (?!) are confusing Hard to debug: One wrong character and nothing matches — no clear error message No visualization: A long regex string is just a wall of symbols The generator aims to solve these with clickable buttons and instant visual feedback. https://jsokit.com/blog/posts/from-template-strings-to-standard-practices-building-a-readme-generator/ Sun, 26 Apr 2026 09:00:41 +0000 https://jsokit.com/blog/posts/from-template-strings-to-standard-practices-building-a-readme-generator/ From Template Strings to Standard Practices: Building a README Generator Project is done. Now, how to write the README? Many developers (including myself) have been there: the code is solid, but the README is an afterthought. It’s not about lack of motivation—it’s the repetitive work of structuring sections, finding badges, formatting text. Recently added a README generator to JsonKit. Here’s the technical breakdown. The Standard README Structure Let’s look at what mature READMEs include: https://jsokit.com/blog/posts/random-data-generator-mock-data-best-practices-and-implementation-details/ Sat, 25 Apr 2026 15:03:10 +0000 https://jsokit.com/blog/posts/random-data-generator-mock-data-best-practices-and-implementation-details/ Random Data Generator: Mock Data Best Practices and Implementation Details Creating test data manually is fine for a few records, but generating 100 test entries? That’s torture. During a recent project, I hit a wall: the backend API wasn’t ready, but the frontend needed data for debugging. QA needed edge cases. Demos required realistic user data. So I built a random data generator and dove into mock data best practices. https://jsokit.com/blog/posts/from-reed-solomon-to-canvas-building-a-high-quality-qr-code-generator/ Fri, 24 Apr 2026 15:29:48 +0000 https://jsokit.com/blog/posts/from-reed-solomon-to-canvas-building-a-high-quality-qr-code-generator/ From Reed-Solomon to Canvas: Building a High-Quality QR Code Generator A recent project required “nicer looking” QR codes. Most tools I found just produced black-and-white squares or slapped a logo on top. I wanted something more refined, so I dug into QR code internals. QR Code: More Than Black and White QR Code (Quick Response Code) was invented by Denso Wave in 1994. A QR Code contains: Position Markers: Three corner squares for orientation Timing Patterns: Alternating black/white lines for alignment Version Info: QR code size (versions 1-40) Format Info: Error correction level and mask pattern Data Area: Actual content The key is Reed-Solomon error correction. https://jsokit.com/blog/posts/security-pitfalls-in-password-generators-from-mathrandom-to-cryptogetrandomvalues/ Mon, 20 Apr 2026 17:22:10 +0000 https://jsokit.com/blog/posts/security-pitfalls-in-password-generators-from-mathrandom-to-cryptogetrandomvalues/ Security Pitfalls in Password Generators: From Math.random to crypto.getRandomValues I was building a password generator tool recently and discovered that many online implementations have serious security flaws. What seems like a simple password generation task actually hides numerous pitfalls. The Fatal Problem with Math.random The simplest implementation looks like this: function generatePassword(length) { const chars = 'ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789' let password = '' for (let i = 0; i < length; i++) { password += chars.