Well, you'll probably eventually get bored with sys admin work if programming is a really interesting hobby for you. Consider taking a couple of classes, perhaps just for resume purposes, and while at the job take the initiative to program some systems for them on your spare time if necessary. I've hired people that have come into programming on the exact route that I'm describing.
Yes, you'd probably never get an interview. If someone has zero experience *and* zero "official" education then it's difficult to get an interview for a job programming.
However, your solution is interesting. Using the null termination for your temporary space is an interesting way of saving a byte. But you're right, I'd prefer an actual variable to be used.
Cool - nice - that's probably as readable as it can get with pointers. Having said that, I prefer a non-pointer implementation with just using []. It compiles to something very similar and is much easier to understand as it uses the simpler concept of arrays as opposed to the "tricky" (for many) concept of pointers.
You're obviously a good programmer - that's not in question. My concern when I hire people is that they be good, and they appreciate that others may not be as good. It's a gray area for sure.
You would be incorrect. I prefer people to either write the code the way I asked and *then* tell me why it shouldn't be done that way, OR they should tell me beforehand why they *won't* do it a certain way, and why.
The only problem I would have with hiring you is the potential diplomacy issues.;)
Mathematicians do some crazy divide, remainder, often recursive solution. Most just confuse themselves.
The bit sifting method is the way to go in my experience. However, most programmers don't know about bits - they've been programming in Java for too long.:) Here we go - I've really started a debate now!!!!
How about something else.. It's a little more subjective, but implement the same function but where you attempt to balance minimal memory usage with readability. Assume you are a contractor and all code is to be passed off to the internal development team afterwards, so it must be maintained by someone else that you don't know.
The first solution is the easiest and simplest, although I'm not sure about the strlen repetition.
I'm not actually sure that the last two solutions you did will actually work... It's early here.:)
When I'm asking this question I want someone to write a function that uses minimal memory but is still readable. Then, if they know other ways to optimize even further, they can get bonus points by offering to implement addition solutions that would save X more bytes, but would unfortunately be not as readable. Doing exactly what I say (i.e. minimal memory usage!) is not necessarily the exact answer to the question. Reject authority!:)
In an interview, I used to tell people that they could use strlen, but not other string functions. I stopped telling people that a couple of years ago and sometimes people give a solution like yours. If you weren't an axe murderer and you actually gave me the real solution afterwards (after I clarify I want *you* to implement it), then you'd definately be in the running to get a job.:)
BTW - your solution allocates about 4 squigabytes of memory, but that's OK because it all gets allocated by someone else, so it doesn't count.;)
Fair enough. Your solution is good and allocates very little memory. However, I would also accept a solution that allocated one more byte and was more readable.:)
Let's do it! Somebody start the patent application, and I'll start to work on some kind of multicast-IP-over-AM-MP3 thing so that we can make it sufficiently complicated.
Yes, it took me several years before I became a good programmer. Perhaps at the age of 15 or 16 or so, especially because it was a hobby thing. It should take less time if you have a teacher, and a job where you do it for 40 hours week.:)
Something I believe strongly is that learning at an early age is the only way to be *really* good at thinking in a different way. I started to program in assembly language when I was 12, so I have a different way of thinking about numbers than most people do. I'm not sure that it's as easy to teach an 18 year old the kinds of things that a more moldable child can learn.
There are some people that just have the right kind of brain for programming. Often they like logic puzzles, crosswords, and so on. These people will usually make better programmers than those that don't like puzzles because they're confusing and boring, and just started to program at the age of 25 because that's where the money is.
I'm jaded though - I've interviewed far too many shitty programmers, and seen far too many people in programming that went on a VB programming course in 2000 and complained for the next three years that they couldn't get a job.
Besides, what's wrong with Amplitude Modulation? Stereo sound is over-rated and will never catch on - people can only concentrate on one thing at a time.
Re:IP will give these no advantage at all.
on
TCP/IP Speakers
·
· Score: 4, Insightful
You're right that XLR and existing technologies would be better for *highly* accurate stereo imaging. However, this is an in-ceiling speaker designed for rich geeks and their in-home audio systems. Stereo imaging does not work in these environments and they are often wired in mono. Imagine listening to The Beatles and their insane stereo imaging in your kitchen! Drums near the stove, and the guitar over by the fridge - doesn't work.
Mono is also how 99.9% of retail/hospitality locations are wired, even the high end ones where they spend hundreds of thousands of dollars on the installations.
Also, forget about audiophiles and whether they would like these speakers. Audiophiles will never install in-ceiling speakers, and if they do it's purely for "background music" purposes around the house.
I believe that this product is for the rich geek that wants to be able to utilize his already-CAT5-wired home and be able to show off to their other rich geek friends.
You're absolutely correct, except perhaps in the last paragraph. Programming is as much about aptitude as it is about education and experience. Some people will *never* be good programmers no matter what you do with them.
I have programmed (in many different languages) since I was about 9 and regard myself as a good programmer - who doesn't?;) Anyway, I now hire and manage programmers and have interviewed probably about a hundred people for programming positions. Most of them are total shit. They couldn't program their way out of a paper bag. Their resume looks great and they have all the acronyms and say the right things. Then I ask them to code a function to reverse the order of a string with allocating as little extra memory as possible. Less than 50% of people can do it right. A simple algorithm like this is easy to check in your head and they just don't get it.
One of the other more "nasty" questions I ask is for people to do a number to hex-string conversion algorithm. I've only have ONE person do it right. Most just stare at me. They don't understand binary! They mostly have CS degrees so they were taught, but their brains don't really get it. It's very interesting because most people don't understand what a number is at a base level - it's astounding. I could go on...
I have to agree and disagree. It is true that a GOOD programmer can code easily without leaking memory. But it is also true that most programmers are not good! Look around - most are adequate at best. As a percentage, there are very few really good programmers out there - I would guess under 10%. Therefore, any tool that helps the adequate programmer fuck things up less is a good thing in most instances as it will save a ton of time/money.
Obviously, there are some applications (OS/real-time/audio/video) that require more deterministic outcomes and not some "silly" garbage collection or VM hanging around.
In summary, pick the right tool for the job and understand the limitations of those doing the work.
"Those votes are about as useful and meaningful as putting a referendum on the ballot calling for the city to have more sunny days"
You're absolutely right. The problem with these kinds of projects is that it preys on the general cluelessness of the masses. This is the thought process I think most people go through:
-There is a traffic problem
-Something must be done to fix the traffic problem
-The monorail is indeed "something" and carries people
-The monorail will therefore fix the traffic problem
Everyone so far has been talking about noise, cost, whatever. The main issue that I see is the one of CAPACITY. At the time the people voted for the monorail it was a "secret" as to how long the platforms will be. Doesn't sound like a huge deal at first glance, but look again. There is a limit to how often you can take a train through a station. It has to stop, the passengers get on/off, and then it has to start. I understand that you're optimistically looking at 2 minutes, but realistically looking at more like 3 minutes or so. The second variable is station length. The longer the station, the bigger the train, the more people can get on and off for each station visit. Therefore, on the most critical limiting factors in capacity is the station length. But it's a fucking secret when you have to vote on it? Consider that this is NOT Las Vegas or Disney world. You cannot make the station length the length of 3 city blocks - this is DOWNTOWN and so the stations have to be smaller.
Yes, they published capacity figures of X thousand people per day. As far as I recall, those figures were for the entire DAY and not realistic in terms of rush hour and getting to and from work. This isn't Disney World - we're talking rush hour here. What I want to know, and what I've NEVER been told is:
-How many people can this monorail between the hours of 7am and 9am to get INTO Seattle?
-How many people currently, on the proposed monorail route, get into Seattle during that time window?
-Is the difference between those numbers actually significant, or are we just spending a shit load of money on something that only 2% of commuters will use? Or is it 30%?
Someone give me the answers, please! And give me the answers 5 year ago before I have to vote on this issue.
Totally agree. I just got involved in my (first) accident with some "lady" that decided to turn left in front of me at a traffic light. She "didn't see me". She had young kids in the back of her car too - I dread to think what could have happened to them if I didn't hit the brakes FAST with my lovely ABS system. They could be seriously injured or dead right now. Stupid bitch.
Anyway, I was going 30 and she was going about 5mph. Was she a dangerous driver? Yes! Were either of us speeding? NO!
It seems to be the case that there are two types of dangerous drivers. First, the morons that drive recklessly, drink and drive, cut people up, etc. These people tend to *also* drive fast. The second type is a member of the "oblivious masses" that can only see things that are in front of them. To these people mirrors are odd devices that have limited use. Sometimes their motto seems to be "slow is safe!" regardless of the situation. They don't understand road rules, they make bad decisions (not deliberately - they're not reckless in a deliberate sense) and that causes accidents. The lady I hit falls into this second category. She probably thinks she's a "safe" driver because she never goes over the speed limit. Remember, "slow is safe!".
Likewise, we can split safe drivers into two different categories - ones that stick to the speed limit and ones that don't. 60mph at night in the pouring rain may be an appropriate limit at that point in time, but it bears no similarity with that same stretch of road on a Sunday afternoon in dry sunny conditions. The speed limit is a conservative limit, given that it is not practical to have a variable limit across large sections of freeway. Just because you drive the speed limit doesn't in itself make you a safe driver.
Finally, it will always be true that people that drive slower than me are morons, and people that drive faster than me are idiots.:)
Using Vonage does not require using your computer. It plugs into your broadband connection and allows you to use your normal phone. In addition, Vonage charge something like $40 to get set up, and then the first month is free. So I don't think setup fee or hassle is the reason...
It could be the rates though - I moved away from England several years ago and so I don't remember how much they charge.
I also signed one, because I had to otherwise my job would have dissapeared. It had sections of non-compete (3 or 6 months) and also sections of non-solicitation which are perhaps more important because they prevent you from leaving and taking your buddies or customers with you. Often, the non-solicitation is more enforceable because they do not prevent you from being able to make a living and do not affect your "right to work".
The problem with your response is that while every Slashdot reader may know what you say to be true (faster, 64bit, less heat), the rest of the world has no fucking clue. And they're the ones that actually buy most of the computers. Yes yes, they're "stupid" and they should just "RTFM" and learn all about technical shit that us geeks just love, but they won't because they don't care.
If AMD actually did some really good marketing, then perhaps "normal" people could be made aware of the glorious advantages of the AMD chips. Only when Dell gets hundreds of emails a day saying, "I want an AMD chip - they're way better - won't buy your shit", will Dell think about changing. Right now, they don't have to...
So AMD don't have the capacity to meet Apple's demand, but Apple's demands are "tiny"? And Intel are the ones having capacity issues right now...
I don't think I'm the only one that's confused.
AMD and Intel both make consumer chips anyway - I don't think it would be a big deal to siphon off a few hundred chips here and there, wrap it in a white, shiny box and sell it to a starving artist.
I would hate to be the guy running the development group. Imagine the job posting on Moster:
ATM development group seeks legacy OS/2 developer to work on old ATM systems using legacy UI libraries. Candidates with no ambition are preferred. We pay lots of money because if you want this job, you're the only one out there.
A hacker disconnects the Ethernet cable and plugs in his laptop. He follows the DNS scam as mentioned by a previous poster. He spends the next 4 hours getting root access and puts on a fake shell! While packing up his geek toys, a truck drives through store front and just removes the ATM so they can cut into it later and steal the cash!
See how insecure Windows is!!! Couldn't have happened with OS/2...
Slashdot Mirror
Well, you'll probably eventually get bored with sys admin work if programming is a really interesting hobby for you. Consider taking a couple of classes, perhaps just for resume purposes, and while at the job take the initiative to program some systems for them on your spare time if necessary. I've hired people that have come into programming on the exact route that I'm describing.
However, your solution is interesting. Using the null termination for your temporary space is an interesting way of saving a byte. But you're right, I'd prefer an actual variable to be used.
Ever considered a career in programming?
You're obviously a good programmer - that's not in question. My concern when I hire people is that they be good, and they appreciate that others may not be as good. It's a gray area for sure.
The only problem I would have with hiring you is the potential diplomacy issues. ;)
Mathematicians do some crazy divide, remainder, often recursive solution. Most just confuse themselves.
The bit sifting method is the way to go in my experience. However, most programmers don't know about bits - they've been programming in Java for too long. :) Here we go - I've really started a debate now!!!!
How about something else.. It's a little more subjective, but implement the same function but where you attempt to balance minimal memory usage with readability. Assume you are a contractor and all code is to be passed off to the internal development team afterwards, so it must be maintained by someone else that you don't know.
I'm not actually sure that the last two solutions you did will actually work... It's early here. :)
When I'm asking this question I want someone to write a function that uses minimal memory but is still readable. Then, if they know other ways to optimize even further, they can get bonus points by offering to implement addition solutions that would save X more bytes, but would unfortunately be not as readable. Doing exactly what I say (i.e. minimal memory usage!) is not necessarily the exact answer to the question. Reject authority! :)
BTW - your solution allocates about 4 squigabytes of memory, but that's OK because it all gets allocated by someone else, so it doesn't count. ;)
Fair enough. Your solution is good and allocates very little memory. However, I would also accept a solution that allocated one more byte and was more readable. :)
Now, could anybody else make it any *more* complicated? I can still just about understand what it is you're doing, so we're not quite there yet. ;)
Let's do it! Somebody start the patent application, and I'll start to work on some kind of multicast-IP-over-AM-MP3 thing so that we can make it sufficiently complicated.
Something I believe strongly is that learning at an early age is the only way to be *really* good at thinking in a different way. I started to program in assembly language when I was 12, so I have a different way of thinking about numbers than most people do. I'm not sure that it's as easy to teach an 18 year old the kinds of things that a more moldable child can learn.
There are some people that just have the right kind of brain for programming. Often they like logic puzzles, crosswords, and so on. These people will usually make better programmers than those that don't like puzzles because they're confusing and boring, and just started to program at the age of 25 because that's where the money is.
I'm jaded though - I've interviewed far too many shitty programmers, and seen far too many people in programming that went on a VB programming course in 2000 and complained for the next three years that they couldn't get a job.
Besides, what's wrong with Amplitude Modulation? Stereo sound is over-rated and will never catch on - people can only concentrate on one thing at a time.
Mono is also how 99.9% of retail/hospitality locations are wired, even the high end ones where they spend hundreds of thousands of dollars on the installations.
Also, forget about audiophiles and whether they would like these speakers. Audiophiles will never install in-ceiling speakers, and if they do it's purely for "background music" purposes around the house.
I believe that this product is for the rich geek that wants to be able to utilize his already-CAT5-wired home and be able to show off to their other rich geek friends.
I have programmed (in many different languages) since I was about 9 and regard myself as a good programmer - who doesn't? ;) Anyway, I now hire and manage programmers and have interviewed probably about a hundred people for programming positions. Most of them are total shit. They couldn't program their way out of a paper bag. Their resume looks great and they have all the acronyms and say the right things. Then I ask them to code a function to reverse the order of a string with allocating as little extra memory as possible. Less than 50% of people can do it right. A simple algorithm like this is easy to check in your head and they just don't get it.
One of the other more "nasty" questions I ask is for people to do a number to hex-string conversion algorithm. I've only have ONE person do it right. Most just stare at me. They don't understand binary! They mostly have CS degrees so they were taught, but their brains don't really get it. It's very interesting because most people don't understand what a number is at a base level - it's astounding. I could go on...
Obviously, there are some applications (OS/real-time/audio/video) that require more deterministic outcomes and not some "silly" garbage collection or VM hanging around.
In summary, pick the right tool for the job and understand the limitations of those doing the work.
You're absolutely right. The problem with these kinds of projects is that it preys on the general cluelessness of the masses. This is the thought process I think most people go through:
-There is a traffic problem -Something must be done to fix the traffic problem -The monorail is indeed "something" and carries people -The monorail will therefore fix the traffic problem
Everyone so far has been talking about noise, cost, whatever. The main issue that I see is the one of CAPACITY. At the time the people voted for the monorail it was a "secret" as to how long the platforms will be. Doesn't sound like a huge deal at first glance, but look again. There is a limit to how often you can take a train through a station. It has to stop, the passengers get on/off, and then it has to start. I understand that you're optimistically looking at 2 minutes, but realistically looking at more like 3 minutes or so. The second variable is station length. The longer the station, the bigger the train, the more people can get on and off for each station visit. Therefore, on the most critical limiting factors in capacity is the station length. But it's a fucking secret when you have to vote on it? Consider that this is NOT Las Vegas or Disney world. You cannot make the station length the length of 3 city blocks - this is DOWNTOWN and so the stations have to be smaller.
Yes, they published capacity figures of X thousand people per day. As far as I recall, those figures were for the entire DAY and not realistic in terms of rush hour and getting to and from work. This isn't Disney World - we're talking rush hour here. What I want to know, and what I've NEVER been told is:
-How many people can this monorail between the hours of 7am and 9am to get INTO Seattle? -How many people currently, on the proposed monorail route, get into Seattle during that time window? -Is the difference between those numbers actually significant, or are we just spending a shit load of money on something that only 2% of commuters will use? Or is it 30%?
Someone give me the answers, please! And give me the answers 5 year ago before I have to vote on this issue.
Many thanks.
Anyway, I was going 30 and she was going about 5mph. Was she a dangerous driver? Yes! Were either of us speeding? NO!
It seems to be the case that there are two types of dangerous drivers. First, the morons that drive recklessly, drink and drive, cut people up, etc. These people tend to *also* drive fast. The second type is a member of the "oblivious masses" that can only see things that are in front of them. To these people mirrors are odd devices that have limited use. Sometimes their motto seems to be "slow is safe!" regardless of the situation. They don't understand road rules, they make bad decisions (not deliberately - they're not reckless in a deliberate sense) and that causes accidents. The lady I hit falls into this second category. She probably thinks she's a "safe" driver because she never goes over the speed limit. Remember, "slow is safe!".
Likewise, we can split safe drivers into two different categories - ones that stick to the speed limit and ones that don't. 60mph at night in the pouring rain may be an appropriate limit at that point in time, but it bears no similarity with that same stretch of road on a Sunday afternoon in dry sunny conditions. The speed limit is a conservative limit, given that it is not practical to have a variable limit across large sections of freeway. Just because you drive the speed limit doesn't in itself make you a safe driver.
Finally, it will always be true that people that drive slower than me are morons, and people that drive faster than me are idiots. :)
I have never called 911 from my POTS line, and I don't plan on doing so in the future! Avoid unforseen emergencies - that's my advice. ;)
It could be the rates though - I moved away from England several years ago and so I don't remember how much they charge.
I also signed one, because I had to otherwise my job would have dissapeared. It had sections of non-compete (3 or 6 months) and also sections of non-solicitation which are perhaps more important because they prevent you from leaving and taking your buddies or customers with you. Often, the non-solicitation is more enforceable because they do not prevent you from being able to make a living and do not affect your "right to work".
If AMD actually did some really good marketing, then perhaps "normal" people could be made aware of the glorious advantages of the AMD chips. Only when Dell gets hundreds of emails a day saying, "I want an AMD chip - they're way better - won't buy your shit", will Dell think about changing. Right now, they don't have to...
So AMD don't have the capacity to meet Apple's demand, but Apple's demands are "tiny"? And Intel are the ones having capacity issues right now... I don't think I'm the only one that's confused. AMD and Intel both make consumer chips anyway - I don't think it would be a big deal to siphon off a few hundred chips here and there, wrap it in a white, shiny box and sell it to a starving artist.
ATM development group seeks legacy OS/2 developer to work on old ATM systems using legacy UI libraries. Candidates with no ambition are preferred. We pay lots of money because if you want this job, you're the only one out there.
A hacker disconnects the Ethernet cable and plugs in his laptop. He follows the DNS scam as mentioned by a previous poster. He spends the next 4 hours getting root access and puts on a fake shell! While packing up his geek toys, a truck drives through store front and just removes the ATM so they can cut into it later and steal the cash!
See how insecure Windows is!!! Couldn't have happened with OS/2...