http://www.actionscript.org/employment/view_position.php?id=544

[Taff]

Must have 2 years experience Flash 2004 MX Professional.

Couldn't that be a bit tough to find a candidate?

:confused:

[Timmee_3Styler]

hahhaha good catch :)

[hangalot]

unless you were on the beta.... but then again you would not be able to say without violating your NDA so...

[Xeef]

Hmmm

i sit 16 hours in front of the computer wich shoud make up 2 working days
and this 7 days a week since 10 months
i think i coud call it 2 years experience (working years whit hollidays and week ends)

[snapple]

I wouldn't classify 'experience' as sitting infront of a computer. I call it "tooling around and not being bothered to get on with real work". People always want to 'big-up' their experience.. result? Everyone has loads of experience, just not good experience.

[hangalot]

Xeef also not to be mean, but the fact that you spend this much time on the forum, would make me extremely reluctant to hire you as it seems you don't do any work.

[Xeef]

:p :D

you coud have 10 years experience and still by worser then one whit 1 months

or say it more possitive

1 whit 1 moths experience coud by better the one whit 10 years

was more a joke then a application for the job

[mmm..pi..3.14..]

I'd hire Xeef...the fact that he spends so much time on the forums does not make me not want to hire him, some of his posts contain some really amazing code, sometimes I even need to look at it a few times to understand what he's done, lol :p

Eric

[snapple]

Amazing code should require exactly the opposite of that. Functions should only ever do 1 thing, and do it well, avoid use of 'god-classes' and avoid coupling and keep your code cohesive. Any code that takes a few looks to work out, generally means that it's not good for other programmers to use or that easy to implement.

[hangalot]

hear hear. best practises page 1

[tg]

Any code that takes a few looks to work out, generally means that it's not good for other programmers to use or that easy to implement.

not only for other programmers... if you do long term projects, you don't want to go back and maintain something you wrote 1-2 years ago. if you did a poor job with your programming, even if your the original programmer, trying to figure out what you were thinking can be a real problem.

so... i've got to agree with snapple... and add document everything!

[jjbilly]

hey, poor xeef :o Mind you, when he throws in the Hungarian...

[CyanBlue]

Me don't likie comments... I think I am too lazy... :(

[Xeef]

yeh thats true commenting is important

i just not like to write 1 line of code and 10 line to comment it :p
and i also program for fun and not as a job
if i use 20% of the time to program and the rest to comment then it's no fun anylonger :(

[hangalot]

you get software that autogenerates java doc style comments for you, and then you get software that auto generate documentation from java doc comments for you. so the amount of comments you must actually write is very little to get max effect. also using a proper editor with templating features makes this process even more standarised. using well developed frameworks like ARP, or the itteration::2 with a unit testing framewrok (like asunit)is also part and parcel of a best practises enterprise. so the minute you actually write code for a living (which it seems most of us here do) keep this in mind.

[snapple]

Generating your own java docs is great, i recently ended up with quite large documentation for a project and it's so nice to just be able to comment here and there and end up with full documentation. I was saying to senocular the other day - javaDocs is just what Flash needs (no not that poor excuse for documentation they call "liveDocs").

One thing that irritates me beyond belief (and for some reason it is rife in Actionscript) is unnecessary commenting, part of good standards is to only comment when it is necessary. On the flash forums, i swear many people seem more preoccupied with drawing pretty pictures with forward slashes than actually writing clean, proper, reusable code.

hangalot, i have never performed unit testing via any kind of framework. Unit testing always happens (by definition) on a small scale, so i just write a few scripts, if it comes out with the right result - i leave it, i have to confess that i never ever do this to the extent that you are suppose to (or how much we are told to).

[hangalot]

we had a extreme programming consultant hovering over our shoulders for 6 months while we worked on a project for a client (who themselves enforced the XP method on us), so that meant writing unit tests before coding, short itterations, peer programming. all in all i think its a really effective methodology. as they say either you do the whole of XP or its not worth your time doing any.

as a side note peer programming fcked me off no end in the begining, since they seemed to team stronger and weaker programmers together, and it effectively defeated the purpose of what peer programming should have been. this in time changed as everybody got more clued-up, and when they started loosing developers (contracters, including myself) the knowledge of what we did was still maintained in the company (which i consider an effective knowledge mangement model)

[senocular]

I'd hire Xeef...the fact that he spends so much time on the forums does not make me not want to hire him, some of his posts contain some really amazing code, sometimes I even need to look at it a few times to understand what he's done, lol :p

Eric

I've gotten jobs from spending excessive amounts of time on forums ;)

[hangalot]

small jobs or real jobs, on large projects? i got a contract though the employment section, does that count? :D

[senocular]

Contracted work, nothing TOO huge (though I honestly dont like large projects).

... I would think counting the employment section is cheating :D

[Timmee_3Styler]

"It HAS to be made with Microsoft ASP.NET Web Matrix as asp.net file are saved as “.aspx” format."

I found this the other day, and I want to ask about web matrix. Doesnt all ASP.NET code have the .aspx extension?

[freddycodes]

we had a extreme programming consultant hovering over our shoulders for 6 months while we worked on a project for a client (who themselves enforced the XP method on us), so that meant writing unit tests before coding, short itterations, peer programming. all in all i think its a really effective methodology. as they say either you do the whole of XP or its not worth your time doing any.

as a side note peer programming fcked me off no end in the begining, since they seemed to team stronger and weaker programmers together, and it effectively defeated the purpose of what peer programming should have been. this in time changed as everybody got more clued-up, and when they started loosing developers (contracters, including myself) the knowledge of what we did was still maintained in the company (which i consider an effective knowledge mangement model)


Don't you just love writing unit tests for frontends?

Assertion.Assert("moron clicked the button");

I work in a XP env as well. Its beneficial but has its shortcomings as well. You mentioned a couple of them.

[hangalot]

Don't you just love writing unit tests for frontends?

Assertion.Assert("moron clicked the button");

I work in a XP env as well. Its beneficial but has its shortcomings as well. You mentioned a couple of them.
we automated a fair bit of UI testing with winrunner. you still need to write unit tests for api level stuff, but for actual ui interaction winrunner is a wicked way.