21–30 of 54 posts
Given that we probably all live in a virtual simulation of some sort, isn't everything code? A more interesting question would be, "what isn't code?"
A great all around introduction to programming. It poses an interesting question which I think it doesn't really answer well: "What Is the Relationship Between Code and Data?" I can easily understand what a "program" is. It is a set of instructions we give to the computer for it to do something we want it to do. But what is "data"?
> But what is "data"? It's a sequence of bits. You take reality (or whatever you want) and represent it as bits. That sequence of bits is called "data".
Data is the plural of datum. A datum is a piece of information. Of course not any piece information is automatically a datum, as that noun implies a certain structured nature or a normative perspective on that piece of information.
Certain information only became commonplace because it became a datum first. Before using family names as an identifier many people had no family names, they were identified by their first name and by the places they grew up in.
A great all around introduction to programming. It poses an interesting question which I think it doesn't really answer well: "What Is the Relationship Between Code and Data?" I can easily understand what a "program" is. It is a set of instructions we give to the computer for it to do something we want it to do. But what is "data"?
Given that we probably all live in a virtual simulation of some sort, isn't everything code? A more interesting question would be, "what isn't code?"
Sound approaches to knowledge must operate in the opposite direction, drawing insights from observation of phenomena existing in the world.
Assuming that the world is as we deduce it to be, without then proceeding to check that the world behaves in accordance with our deduction, is a failure that delayed the advance of knowledge until the use of the scientific method became widespread.
A great all around introduction to programming. It poses an interesting question which I think it doesn't really answer well: "What Is the Relationship Between Code and Data?" I can easily understand what a "program" is. It is a set of instructions we give to the computer for it to do something we want it to do. But what is "data"?
It isn't surprising to me that the best software developers I have met have been those who either had no computer science degree or got it after having some degree or major interest in another field, typically a liberal arts or science field. Liberal arts are actually the study of systems in disguise because of the need to connect together various ideas, events, etc. that do not necessarily have clear delineations or relationships.
A great all around introduction to programming. It poses an interesting question which I think it doesn't really answer well: "What Is the Relationship Between Code and Data?" I can easily understand what a "program" is. It is a set of instructions we give to the computer for it to do something we want it to do. But what is "data"?
or the age old joke: "The good thing about (data) standards is there are so many of them!"
> This is real. A Scrum Master in ninja socks has come into your office and said, “We’ve got to budget for apps.” Should it all go pear-shaped, his career will be just fine.
It's funny how organizations manage not to fall apart with so many people with so different motivations. For example, an SWE can despair in 2022 because they work on Openstack bugfixing or on mainframe JCL2 batch jobs, but here this exec worries about his position being undermined by some software project.
This is a somewhat myopic and outdated description of what "code" or "software" is. I'm writing an article on this, but software is a much broader idea and domain than just getting computers to do something. At a minimum, it includes getting a computer to do something, communicating between humans and not humans and computers, and encoding a domain. All this adds up to software being "executable knowledge", which mak…
I'm not arguing against people from other fields bringing valuable insight; I'm disputing that CS doesn't also involve the study of complex heterogeneous systems or that it is about "coding".
Seems like you're describing a bootcamp or coding school instead.