Here is a frustration every experienced developer eventually hits: you already know how to program. You have built real things. You understand what a class is, what a promise is, why you would reach for a hash map instead of an array. And yet every time you try to pick up a new language, the tutorial in front of you opens with “a variable is a container that stores a value.”<\/p>\n\n\n\n
There is a better way to do this. Instead of re-learning programming dressed in new syntax, you need a translation layer \u2014 here is the concept you already know, here is how it is expressed in this language, and here is the handful of ideas that are genuinely new.<\/em> That is the entire gap. Most tutorials don’t close it because they are not built for people who already know how to code.<\/p>\n\n\n\n Cognate.dev<\/strong> is built for exactly that.<\/p>\n\n\n\n A cognate, linguistically, is a word that shares a root across two languages but shows up in a slightly different form \u2014 “actual” in English and “actual” in Spanish look almost the same and mean something subtly different. Language learners use cognates as shortcuts: recognize the pattern once, and a huge chunk of new vocabulary stops being new.<\/p>\n\n\n\n Programming languages are full of the exact same thing. A Open the site and the landing page says exactly what it’s for, right in the first line:<\/p>\n\n\n\n Same brain, new syntax.<\/strong><\/p>\n<\/blockquote>\n\n\n\n That’s not just a tagline, it’s the entire design constraint. Below it, four short promises, and I want to be honest about each one because they’re not just marketing copy \u2014 they’re commitments I had to actually build against:<\/p>\n\n\n\n Scroll past that and you hit the actual point of the homepage: a grid of language tracks. Right now it’s honest about where things stand \u2014 Python is marked Live<\/strong>, Rust and Go are Planned<\/strong>, Java is just an Idea<\/strong> sitting there as a placeholder. I didn’t want a landing page that pretends to be more finished than it is. Each card even carries its own accent color, so as more tracks ship, the page will visually feel less like one language and more like a shelf of them.<\/p>\n\n\n\n Most comparison-based teaching material has a quiet flaw: it tries to force an analogy onto everything<\/em>, and the moment the analogy breaks, the learner is quietly misled instead of helped.<\/p>\n\n\n\n The Python tutorial \u2014 the first track live on the site \u2014 is built to resist that. It’s honest, repeatedly, about where the comparison stops working:<\/p>\n\n\n\n I’d rather a learner walk away knowing “this one’s genuinely new, pay attention” than have them assume every new language concept has a tidy JS box to fit into.<\/p>\n\n\n\n
\n\n\n\nThe idea in one line<\/h3>\n\n\n\n
for<\/code> loop is a cognate. A class constructor is a cognate. async<\/code>\/await<\/code> is a cognate \u2014 even in cases (we’ll get to this) where what’s happening underneath is completely different. Cognate.dev exists to teach those pairs explicitly, instead of pretending you’re starting from zero.<\/p>\n\n\n\n
\n\n\n\nWhat you actually land on<\/h3>\n\n\n\n
\n
\n
\n\n\n\nWhy “the gaps get flagged” is the part I care about most<\/h3>\n\n\n\n
\n
asyncio<\/code> for I\/O, threading<\/code>, multiprocessing<\/code> \u2014 because of the Global Interpreter Lock, a thing with no JS analog at all. The tutorial says this outright instead of hand-waving past it.<\/li>\n\n\n\ntry\/except\/else\/finally<\/code> gets called out for its else<\/code> clause, which has no slot in JS’s try\/catch\/finally<\/code> at all.<\/li>\n<\/ul>\n\n\n\n
\n\n\n\nIt’s not just reading \u2014 it runs<\/h3>\n\n\n\n