Unimaginative Username
kiwifarms.net
- Joined
- May 27, 2025
You have it backwards, Bitcoin is the input and CP is the output.int coins = 25;
int *cp = &coins;
What is the output of cp?
nigger
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You have it backwards, Bitcoin is the input and CP is the output.int coins = 25;
int *cp = &coins;
What is the output of cp?
nigger
I'd get the depth of the tree, allocate a buffer like 3x the size for it because that should be enough, and then use that buffer as a stack, so I can do the recuesive solution without actual recursion.In passing, this tree inverting problem always sounded like some crazy fourth-dimension flipping thing, like what, are you supposed to make the leaves the root somehow, invert the relations or something weird. But it's actually just a stupid tree traversal gotcha puzzle, like if you do it recursively then they ask you "but what if the tree has 1000 trillion nodes, what about then think of the stack retard" and if you don't do it recursively they ask if you can't handle recursion. Cool beans
Wouldnt the actual output of cp be the address of coins?You have it backwards, Bitcoin is the input and CP is the output.
I'll link to something written very well that I find explains this nicely: Houyhnhnm ComputingThe problem with a lot of CRUD stuff is there are specific bespoke business requirements that have to be added in that often cannot just be done as a generic form or form builder. Often trying to make something generic with a bunch of rules often leads to something known as the "inner platform effect".
Houyhnhnm computing systems are based on the premise of small modular entities that each do one thing well; and these entities can be combined inside a common platform that does its best to reduce the discontinuity between using and programming. To Houyhnhnms, there is no difference between using and programming; if anything, the difference between a programmer and a user, is that the programmer knows there is no difference between using and programming.
In a Houyhnhnm computing system, programmers do not write standalone applications in non-autistic cases; instead, they write new modules that extend the capabilities of the platform.
Part of this "Inner-platform effect" is because our modern systems are so shitty that this becomes the only option. I try to do just about everything in GNU Emacs, but there's just no other good way to do some of the things Emacs enables on our current systems. The very notion of an immutable yet opinionated kernel betrays the system as one in which things may be added, but not really modified in any meaningful way, unless the program is explicitly designed for it. This is one reason, I suppose, why sh programs are so popular: They're always distributed, and used, as their source code and have no protections whatsoever against any tweaks. Every program should be like this without a very good reason.Because of the high barrier to communication between applications in Human computer systems, these applications tend to grow into big hulking pieces of software that try to do everything — yet can’t. Indeed, even a picture editor will need to edit text to overlay on pictures, to email the pictures, to browse the filesystem looking for pictures to edit, to search pictures by date or by location, etc. It needs to be extensible to accept new file formats, new color schemes, new filters, new extraction tools, new analyses, new generation techniques, new scanning sources, new social networks on which to publish pictures, etc. Soon, it becomes a platform of its own, its own extension API, its own scripting language, its own plugin ecosystem, its own configuration system, its own sandboxing infrastructure. Every successful application grows this way, until it does many of the same things as all the other applications, all of them badly, except those within its own application core.
In a Houyhnhnm computing system, a picture editor will handle picture editing, and picture editing only — and do it well. It will delegate sending email, browsing the filesystem, searching for pictures, etc., to suitable other modules of the common platform. Instead of extensions being available for a single application, they will be available to all software. Thus, whereas Human computer systems feature one unwieldy file selector for each application, Houyhnhnm computing systems instead will have a single file selection service for the entire platform. All the improvements ever made to file selection will be available to all activities instead of only a single application: preview of contents, browsing history, restriction and search by type or by many criteria beside filename hierarchy, relevance to context, selection or tagging of multiple files instead of one at once, automatic refresh of search results, generation of content on demand, etc. Security will notably be improved by each component only having access to the capabilities it needs, containing any security breach by construction.
I see a lot of this on Hacker News. They claim to capable of writing decent software, but I never see any examples of it. Their job doesn't let them write good software, but then they're too tired to write it in their spare time either, but they're definitely able to do it; they went to a bootcamp after all. They're lying to themselves because the only other choice is recognizing their pathetic nature. Plenty of programmers are like this.And you would be wrong. The incentives behind modern software are what create shit software.
i.e., "Show me the incentives, and I will show you the outcome."
It's not engineering because there are no real standards. When I think of an engineer, I think of someone who loses his license and maybe goes to prison for fuckups. Software unintentionally kills people, but no programmer faces real consequences for that, at least not most of the time.Software engineering isn't a traditional engineering discipline. Maybe it should be called something else, and thus why people are often called/call themselves "developers", "programmers" and "hackers".
An understanding of computer science is often not required at all to build good software. Knowing algorithms well enough to whiteboard them isn't a requirement to be able to build good software.
I'll segue to another point I've made in this thread previously. I'm sure we're familiar with bell curves, and we can imagine people with no computing experience whatsoever on the left end, and the best hackers on the right end. Technology, like HyperCard and Emacs, gets made by people on the right end, but then enables those on the left end to write useful software. The video game Myst was originally a HyperCard stack. There are countless stories of men who had never used a computer going out, buying a Macintosh, and just creating in it until they made seriously impressive work they could share or even sell. There's the story about secretaries using Emacs and automating their work through keyboard macros or whatever, not understanding they were programming. These people never could've made the systems they used, but how many of us could build a nuclear reactor before they existed?Not only did he not know the basic things, but he also did not see anything bad about his lack of knowledge. These fucking people have no standards.
This is the only point I am going to reply to because tbh, I feel like the rest of this conversation I had years ago.I see a lot of this on Hacker News. They claim to capable of writing decent software, but I never see any examples of it. Their job doesn't let them write good software, but then they're too tired to write it in their spare time either, but they're definitely able to do it; they went to a bootcamp after all. They're lying to themselves because the only other choice is recognizing their pathetic nature. Plenty of programmers are like this.
I think this gets to the core of why Google uses those types of interview questions. There are no objectively right answers, which means that all American applicants can get it "wrong", which can then be presented to the Department of State as proof that there are no qualified applicants and more H-1B visas are needed.In passing, this tree inverting problem always sounded like some crazy fourth-dimension flipping thing, like what, are you supposed to make the leaves the root somehow, invert the relations or something weird. But it's actually just a stupid tree traversal gotcha puzzle, like if you do it recursively then they ask you "but what if the tree has 1000 trillion nodes, what about then think of the stack retard" and if you don't do it recursively they ask if you can't handle recursion. Cool beans
Now, I am not an American, so I am not fully aware of all the problems that you guys are facing there, but I highly doubt that these interview questions are intended to bring more Indians in your country.I think this gets to the core of why Google uses those types of interview questions. There are no objectively right answers, which means that all American applicants can get it "wrong", which can then be presented to the Department of State as proof that there are no qualified applicants and more H-1B visas are needed.
Try python. It is an easy language to start with, and it is used almost everywhere.What's a good mid level programming type job for someone who already has a science degree but little programming experience?
Is it web development, databases, cloud shit? I know little about this stuff but I'm looking to change careers soon.
Whenever I ask questions like this all the programmers say I shouldn't bother or that this or that language won't exist soon. Very unhelpful
The problem is you're competing against no-lifers who have done nothing but programming since before puberty. You're better off going into operations and fixing people's broken systems.a science degree but little programming experience?
On the other hand, I'm on year 15 of my software engineering career, working at 5 different companies and so far I'm the only person who fits your "no-lifer who coded since before puberty" description out of all the people I've worked with. Nowadays most devs are normies or normy-adjacents who write their first line of code at university, or later.The problem is you're competing against no-lifers who have done nothing but programming since before puberty. You're better off going into operations and fixing people's broken systems.
Most devs are mortgage devs and don't give a shit outside of work.On the other hand, I'm on year 15 of my software engineering career, working at 5 different companies and so far I'm the only person who fits your "no-lifer who coded since before puberty" description out of all the people I've worked with. Nowadays most devs are normies or normy-adjacents who write their first line of code at university, or later.
Maybe it's different if you build compilers for a living or work in game dev.
Lisp is a homo icon.I have a question for the guys who have learned or used Lisp.
What is the appeal of the language? I've got the wizard book for free, and do not know if I want to learn the language or not. Does the stuff written in the book transcend the language itself?
The last time I checked, it was Rust.Lisp is a homo icon.![]()
I don't know where you are from but these question are only meant to disqualify American applicants so that they can then turn around and hire fellow jeets. They don't have to give different applicants the same interview or compare results from the interviews. Its all closed and proprietary but people figure out the scam, nevertheless. Nowadays, they simply say that Americans are a 'poor cultural fit' for jobs in American companies and that's that.Now, I am not an American, so I am not fully aware of all the problems that you guys are facing there, but I highly doubt that these interview questions are intended to bring more Indians in your country.
Forgive me for brevity this time. Common Lisp is a language where I can look at design decisions, and although some are odd, none are wrong. There are no glaring flaws with the language as one finds in others, nothing it makes impossible in a standard function just because no one noticed at the time, as an example. It's very pleasant to use a language with such a design. It's also got a very interesting history. Common Lisp's UNWIND-PROTECT dates back to TECO, as an example. It's an excellent starting point for further learning because of this.I have a question for the guys who have learned or used Lisp.
What is the appeal of the language?
Yes, most certainly. It'll induct anyone who truly learns it into the school of The Right Thing and influence his future designs in ways unlike most other languages.Does the stuff written in the book transcend the language itself?
How is operations different from programming, or is it a subset of it?The problem is you're competing against no-lifers who have done nothing but programming since before puberty. You're better off going into operations and fixing people's broken systems.
Front line help desk versus code monkey.How is operations different from programming, or is it a subset of it?
If you have no experience, you will need to go in on the junior level. I read relatively often that companies aren't hiring many juniors. I don't know whether this is true because it is dependent on location.What's a good mid level programming type job for someone who already has a science degree but little programming experience?
Most jobs will require you to know something about all three. Unless it is some massive megacorp.Is it web development, databases, cloud shit? I know little about this stuff but I'm looking to change careers soon.
There will always be a need even with AI. However there are many roles in the field that aren't programming but are related, e.g., quality assurance, Security (Blue team / Red Team), Operations, site reliability, etc.Whenever I ask questions like this all the programmers say I shouldn't bother or that this or that language won't exist soon. Very unhelpful