And then they demand "equal pay"

It takes about three, spaced apart. If you're clicking rapidly it takes more.

It only takes two or three clicks.

Calling Linus an amateur: priceless

Isn't it undefined and importable?

Dude, you need to get out of there.

So you're responsible for their work but don't have the authority to fire them?

It sounds like you don't know how to navigate the politics of the situation. Whether it's a dudette or a dude some pissant will always try to take credit for your work. The solution is to make an utterly impossible steaming pile of shit of an idea that sounds good, let them take all the credit for the idea, and then watch them fail.

it takes tonnes of hardwork, cutting through competition, persistent dealing with sexism

This is true, but most of the sexism is anti-male

and lot of patience to make place for yourself in this male-dominant

lolno. "There are mostly guys" does not equal "the guys only help other guys"

coveted industry.

lololololololololol

The first problem I see is that it tests an undefined number for a value. test1 is declared, not given a value, and then a while loop is run based on its value.

I think you can get it patented if no one else has already done so, but it will be very difficult to defend if it ever actually goes to court. The advantage in the patent would be to make sure it never goes to court. That said you'll probably get more value in publishing it as open source and getting as many people as possible to use it.

Even today a good supervisor can get a lot more out of a team of programmers. That doesn't make his spec lists code.

This is difficult, therefore a computer will never be able to do it.

The author is being deliberately obtuse. The claim is that only the work that happens above the programmer's level will be needed. Someone tells programmers what to write today, in a much higher level language called English. The claim is those instructions will suffice. And those instructions certainly are not code.

Before you move along you should leave a snarky one liner so we all know how cool you are.

Oh bullshit. Any sufficiently large list of popular sites would suffice for this purpose.

yes! I've seen this so many times. Sometimes they jump right into the bizarre, unexplained shit, sometimes they make it a whole chapter first.

Obviously it's somehow misinterpreting the extra opening curly bracket. __asm is an intrinsic function call, so it has to have been turned into an infinite recursion.

I learned early to comment profusely. I've learned a lot about program design and algorithmic complexity, but thanks to my comments I don't have any trouble.

I felt like a supernerd just reading this.

I have about 50 years of life left. Ten years is a long time.

I don't have a problem with that until it reaches a certain point in the ecosystem. If users are being forced to download your snapshot because it's the only way to support Company Z's API and they're using it on a production system, things have gone way too far. In my opinion the right thing to do in that case is to rush a separate module to release-ready status.

NASA made some of the most reliable software ever written. They did it working from 9 to 5 with no overtime. They did it by first freezing scope, then by making extremely simple, clear code that fit the scope, in small testable units. If the rest of the industry wrote code like that we could finally call it software engineering without insulting real engineers.

While we're ranting the eternal beta needs to go away. It has become a transparent excuse to push bad code. Beta should be for a per-program SMALL user test set for almost-ready software that was feature frozen before this. Beta should have a planned and published beginning and end. When the beta is over the program needs to be shitcanned or patched and published in a clearly demarcated release format.

And the fact that people are stupid enough to pay for beta software does not excuse this.

Javascript may be shit but jquery is one of the most beautiful pieces of code I've ever seen.

https://www.youtube.com/watch?v=60P1xG32Feo

Any consultant right now who can come up with a different buzzword to mean "80 hour workweeks" will make a killing.

This is awesome.

If it works don't fix it.

If all you want to do is write software for web browsers, then JS may be your ticket, but it’s hardly the path to a rich IT career.

Who thought it is? Javascript fills its niche well. What more could be asked of it?