![]() |
50 incompetent mofos
|
Quote:
You told him to wait and he did. It was then up to you to tell him to stop waiting. What if you had started it in a few days, then finished and contacted him and he said "Oh, sorry man, I didn't wait, I had someone else do it so I don't need what you worked on". You would be pissed, right? |
Quote:
As you said, there's a mighty fine difference between a developer (scripter) and an actual programmer. I have "banged off" a few apps in C# using Visual Basic Express but nothing much beyond that as I've never had the time to devote to learning it properly. |
Quote:
|
Well, 35 years in systems & programming at a bunch of $1+Billion companies. A couple of honors degree. Another $250k in additional training, and still going.
I dont' really work in web stuff, but, have learned PHP to go along with the other dozen or so languages that I have worked with over the years. I agree with Libertine that a lot them burn out by the time they are 35(or moved up into management). Most only got in for the money anyways. There are only a few like myself(maybe 2-5%) that actually enjoy it, and don't go the management route. Been a manager a few times, and I get bored trying to figure out how many pencils I have to budget for, etc. Although putting me under MBAs working as Project Leaders with no programming experience is just inviting me to take them out to the parking lot. As Warchild pointed out, there are some pretty complex stuff that the larger companies have had time to develope. Also there are Enterprise packages that are 100s of millions of lines of code. This stuff doesn't run on PCs though. Figure $20 million for hardware, plus another $10 million for software. Quote:
Also, I've seen newbies load everything into tables and then try to update with them. Nice way to get into multiple cross locks. Actually had a college stop teaching that stuff, because we don't allow it out in the real world. Warchild: On high access files(Client Master, etc.) you might want to look into DB fragmentation. Split your master file into different files based on how often each field is accessed. Use joining or extra reads to pick up the additional info only as needed. For huge transaction files try partitioning so that each user/date gets a new file. Creates a zillion files, but you just enumerate the required files as you need them for consolidated stuff. You can also pickup some performance by arranging Ifs/Cases in the most often used order. Quote:
|
any of you high end programmers want to do a well paid, interesting project hit me up on icq 2417874
|
Quote:
|
It's funny how I notice the "real programmers" here noting that php is lame and this and that. Just shows how little you do know about PHP. PHP is coded in C# by the way...may want to think about that long and hard.
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
j/k... kind of. |
Quote:
As long as other humans stay out of the way and don't distract (that costs 30 mins trying to find out what you were doing) - it's nice to inject levels of 'intelligence' into code and make it useful. Tho sure would not be doing it for $30-$50/hour - that's not even a biz. |
Quote:
|
PHP is a set of routines written in C that usurps other third party libraries written in C and creates a hodgepodge system of bizarrely named routines which usually do things, but sometimes don't do what you expect, depending on the release, the day of the week, the season, phase of the moon, et al..
Perl used to be, but it's been capable of rewriting itself, in itself, for quite a few years, now. :thumbsup |
perl sucks...
|
Quote:
|
Quote:
TRUE = 1 FALSE = 0 This creates problems when it doesn't define (or care) about the data, wether it's a string, or a numeric. For instance: strpos. If you have: Code:
$data="hello"; In C you get around this by declaring data types, but with PHP you have to use the '===' test directive, which is basically a really lame way of saying 'if this literally means the same as that'. There's plenty of strange things with different functions as libraries, and PHP have grown over the years - sometimes a function is binary safe, so you can pass anything, other times, you can only use strings. It's messy, but it's getting better. |
Hahaha...
I'm not a school-taught anything (well, journalism / creative writing), but I hate that shit myself; putting in triple equals sometimes to test a false is retarded compared to double equal. I only deal with building websites. Personally, I find it difficult, sometimes, to try and find the right "framework" for my task at hand. There's PHP frameworks to help make my duties more efficient (smarty, off the top of my head) and there's Java ones ( spring, off the top of my head). Plus a bazillion others, such as Ruby on Rails -- one I've played with a little and though I hate saying the moniker of "R.O.R", I do dig how quick a website can be prototyped with it. Anyway, all that shit aside, I think there's a disconnect between how laymen refer to those who do work by using terms like "programmer" / "coder" / "whatever". In the end of my babble .... Grouchy, thanks for hooking up Wolfy. Quote:
|
Quote:
I don't do php, so tell me if I'm wrong: You tested for the "string position" of "h" and it retuned position zero, which means it was found!! The first index of a string is "0", so it found "h" in the very first index of the string "hello". Then you do a boolean test on the result for the "echo", correct?. You can only do a boolean test of a result that will return either 0 or 1 and nothing else. Change the "h" to "o" $testfor="o"; $test=strpos($data, $testfor); And it returns "4" right? If the "h" was not found then the function either returns "-1" or "string::nopos", right? Neither of those are boolean values. Your example doesn't illustrate a problem with php, instead it illustrates that you tried to do a boolean test on a non-boolean result. Right??? |
The problem is not programmers. I bet there are plenty good programmers around here.
The reason why flakes are always brought to discussion is because of the cheap webmasters. I've had several gfy'ers shit themselfs when they hear $60/h quotes so they naturally get the cheaper coder and come back to complain on gfy few weeks later. Flakes exist only because theres a market for cheap programmers that do a half assed job. |
Quote:
|
Quote:
Another way of writing it would be if ($test != FALSE) { echo "Found." } else { echo "Not found." } See the link on strpos above; my shorthand was a little difficult to read if you're not familiar with the nuances of PHP, but it's valid. Code:
<?php |
Quote:
You are already destined to fail and you are already losing money if you even consider hiring a programmer for under 100/hr to create and maintain something critical to your business. |
Quote:
tell that to the gfy crowd though they like it cheap even if it fails once in a while :) |
Quote:
Quote:
|
Quote:
It's precisely the same in the sense that both methods are completly wrong. If you program in C, then you know that strpos is not a boolean function. It MAY return a boolean value but it will also return an interger which is 0 , which is confused as boolean zero. But, in this fuction, zero is not a boolean value yet you tried to evaluate it at as such. You have to tell php that you want to perform an incongruent comparison by using the "===" operator. http://en.wikipedia.org/wiki/Congruent See zero and FALSE are not EQUAL but the are congruent! The "===" says "ignore congruence" and find exact equivalency to FALSE. See you can read all the stuff you want on the internet but it obvioulsy can't replace my education that a boolean function returns either zero or one. If it returns anything else then don't do a boolean test on it. I didn't know php had "===" but I still would have gotten it right because the code you did is just wrong wrong wrong wrong wrong and I would have never written that, because I know what a boolean value is. I never wrote even one line of php code and I saw that right away in your example. But yet you still can't see that. http://us2.php.net/strpos Quote:
The manual tells you that. I told you that. I never read the manual until 5 mins ago and already knew that. But you don't want to hear that. Which proves one thing. Progammers may not be incompetent, but they sure are Fucking Hard Headed :1orglaugh So I back down on my "self taught programmer can write good code" statement. Go to fucking college like I did. |
All times are GMT -7. The time now is 10:42 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc123