{"id":245,"date":"2020-01-26T18:01:27","date_gmt":"2020-01-26T09:01:27","guid":{"rendered":"https:\/\/erkanyildiz.me\/blog\/?p=245"},"modified":"2025-08-28T03:59:12","modified_gmt":"2025-08-27T18:59:12","slug":"essential-standards-every-software-engineer-should-know","status":"publish","type":"post","link":"https:\/\/erkanyildiz.me\/blog\/essential-standards-every-software-engineer-should-know\/","title":{"rendered":"Essential Standards Every Software Engineer Should Know"},"content":{"rendered":"<p>In software engineering, many problems are solved more easily when everyone agrees on the same way to represent things. That's where standards come in. They ensure consistency across systems, programming languages, and platforms. Here are some essential ones every software engineer should know:<\/p>\n<h2><a href=\"https:\/\/en.wikipedia.org\/wiki\/ISO_8601\">ISO 8601<\/a> - Representation of dates and times<\/h2>\n<p>If you've ever struggled with confusing date formats like <code>03\/04\/05<\/code>, you'll appreciate ISO 8601. It defines a universal way to represent dates and times, like <code>2020-01-26T17:45:06Z<\/code>. Using it avoids ambiguity and keeps your data globally consistent.<\/p>\n<h2><a href=\"https:\/\/en.wikipedia.org\/wiki\/List_of_ISO_639-1_codes\">ISO 639<\/a> - Language Designator<\/h2>\n<p>This standard assigns two- or three-letter codes to languages, such as <code>en<\/code> for English or <code>ja<\/code> for Japanese. It's used in applications, websites, and APIs to mark content with the right language. Without it, multilingual systems would be a mess.<\/p>\n<h2><a href=\"https:\/\/en.wikipedia.org\/wiki\/ISO_15924\">ISO 15924<\/a> - Script Designator<\/h2>\n<p>Not all languages share the same writing system, and ISO 15924 solves that by giving each script a code. For example, <code>Latn<\/code> stands for the Latin alphabet and <code>Cyrl<\/code> for Cyrillic. This is especially important for internationalization and typography handling.<\/p>\n<h2><a href=\"https:\/\/en.wikipedia.org\/wiki\/ISO_3166-1#Current_codes\">ISO 3166<\/a> - Country \/ Territory \/ Region Designator<\/h2>\n<p>When you see <code>US<\/code> for the United States or <code>JP<\/code> for Japan, that's ISO 3166 at work. It standardizes country codes used in everything from domain names to payment systems. Without it, global commerce and data exchange would be chaotic.<\/p>\n<h2><a href=\"https:\/\/en.wikipedia.org\/wiki\/IETF_language_tag\">RFC 5646<\/a> - IETF Language Tag<\/h2>\n<p>This builds on ISO standards to create detailed language tags like <code>en-US<\/code> (American English) or <code>zh-Hant<\/code> (Traditional Chinese). It's widely used in web development to identify languages and regions with precision.<\/p>\n<h2><a href=\"https:\/\/en.wikipedia.org\/wiki\/IEEE_754\">IEEE 754<\/a> - IEEE Standard for Floating-Point Arithmetic<\/h2>\n<p>Every time you perform a calculation with decimals in code, you're relying on IEEE 754. It defines how floating-point numbers are represented and how operations like addition and division behave. Knowing this helps explain why <code>0.1 + 0.2<\/code> might not equal <code>0.3<\/code> in many systems.<\/p>\n<h2><a href=\"https:\/\/en.wikipedia.org\/wiki\/Universal_Coded_Character_Set\">ISO\/IEC 10646<\/a> - Universal Coded Character Set (Unicode)<\/h2>\n<p>This is the backbone of Unicode, the standard that makes emojis, accented characters, and scripts from all over the world work seamlessly across systems. Without it, text encoding would still be fragmented and inconsistent, like in the old days of ASCII vs. Shift-JIS vs. ISO-8859.<\/p>\n<p>--<\/p>\n<p>Mastering these standards won't just make you a better engineer, it will make your work more robust and future-proof.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In software engineering, many problems are solved more easily when everyone agrees on the same way to represent things. That&#8217;s where standards come in. They ensure consistency across systems, programming languages, and platforms. Here are some essential ones every software engineer should know: ISO 8601 &#8211; Representation of dates and times If you&#8217;ve ever struggled [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-245","post","type-post","status-publish","format-standard","hentry","category-development"],"_links":{"self":[{"href":"https:\/\/erkanyildiz.me\/blog\/wp-json\/wp\/v2\/posts\/245","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/erkanyildiz.me\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/erkanyildiz.me\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/erkanyildiz.me\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/erkanyildiz.me\/blog\/wp-json\/wp\/v2\/comments?post=245"}],"version-history":[{"count":9,"href":"https:\/\/erkanyildiz.me\/blog\/wp-json\/wp\/v2\/posts\/245\/revisions"}],"predecessor-version":[{"id":254,"href":"https:\/\/erkanyildiz.me\/blog\/wp-json\/wp\/v2\/posts\/245\/revisions\/254"}],"wp:attachment":[{"href":"https:\/\/erkanyildiz.me\/blog\/wp-json\/wp\/v2\/media?parent=245"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/erkanyildiz.me\/blog\/wp-json\/wp\/v2\/categories?post=245"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/erkanyildiz.me\/blog\/wp-json\/wp\/v2\/tags?post=245"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}