Hi !
Featured games (90)
games approved by the League of Dukes
Games in Showcase (748)
Games in Android Showcase (226)
games submitted by our members
Games in WIP (834)
games currently in development
News: Read the Java Gaming Resources, or peek at the official Java tutorials
    Home     Help   Search   Login   Register   
Pages: 1 ... 3 4 [5] 6 7 ... 10
 on: 2018-02-17 07:13:07 
Started by ORmorni - Last post by mrexiled
I am loving your creativity man, this is a great idea no doubt.
I have a proposition for you add me on skype @ CodyzOrrz or PM me.

but to stay on-topic:

here is an idea i have for your game.

1.Single player minigames (if you dont want a campaign of some sort)
    A. Would increase the amount of total players (considering it really is kinda hard for some to find partners).
    B. Increase the amount of faults/bugs found within the cores of the engine. (because of more players)

 on: 2018-02-17 06:26:58 
Started by mrexiled - Last post by mrexiled

Hey guys, i'm fairly new to this forum. (surprising considering how many years i've been making games)

I'm here today in search for Java Developers to create a 2D Java Game Engine with a Real-Time Editor.

So if your Looking to put something on your resume, gain some positive reputation, or some cool revenue then this project could be a good fit for you.


1. At least 2 years experience in 'core' java. (working on private game servers does not count to me)
2. At least 1-2 hour/s free time during the weekdays.
3. Great understanding on efficient Rendering techniques provided by java and its communities.
4. Great understanding when it comes to heap/ram/overall performance in 2D games.
5. Must be efficient in a Java IDE and Git. as these will be used during the project.

that's it guys, i don't require too much, i'm just looking for CREATIVE and FLEXIBLE java developers that are wanting to have some fun and possibly make a name of their selves, not too mention the possible amount of revenue that can come from this is super amazing. (but lets just focus on the simplification of 2D java games)

thanks for reading everyone if you are interested or have any questions please dont hesitate to PM me or Message me on SKYPE (Skype:  CodyzOrrz)

 on: 2018-02-17 00:59:23 
Started by A-Bomb - Last post by philfrei
Code reading is hard. Very few are going to attempt it. I can easily imagine a situation where a company is hiring to fill a need and they don't have the internal expertise to evaluate code that might pertain.

Recruiters are kind of pesky and rarely coders. If they could actually code, they'd probably be doing that rather than recruiting.

The code you write and present on GitHub is still important, though. And it can lead to work opportunities if the library is one that people actually download and use.

 on: 2018-02-16 17:06:33 
Started by A-Bomb - Last post by FabulousFellini
@princec thanks for that, that was super informative I'm sure for everyone.

 on: 2018-02-16 14:27:33 
Started by A-Bomb - Last post by A-Bomb
Ok so, a lot of useful info here. I've taken away that the Github repo is a pretty big one (which I'm working on with a colleague), portfolio should be designed for a moron, and that there are WAY more small details than I had initially thought people ACTUALLY cared about...

That last one actually makes me a little sad, I won't lie. It just feels like I'm in a world where I can't let my code speak for itself, like at all; not even a little. I feel as though I've included some of my most clever, efficient solutions in this portfolio and it's just going to waste because of some idiot not knowing what he's looking at (despite thorough comments) or being overly concerned about how wide my margins are or something...

These last couple weeks of putting myself out there have been so unfulfilling and tiring... at this point I just feel as though it's not worth my effort. Perhaps it's just a smarter move at this point to just continue my job at the warehouse and simply work on my passion projects on the side.

Thanks to everyone for your input!

 on: 2018-02-16 13:53:37 
Started by A-Bomb - Last post by princec
Or "pimps", as we like to call them. Yes, they genuinely are pretty useless f**ktards 90% of the time. They'll only find your CV because they did a keyword search on their huge database - so make sure you do and don't have the keywords you want in the document or you'll get hassled for all sorts of crap you don't want to do. Then when they read your CV almost 95% of it is totally over their heads anyway unless you're lucky enough to find a recruiter who was once in the industry as an actual professional in a previous life.

Other cruft like "team player", "self-learner", "highly motivated" you can also leave out of your CV. You are automatically all of these things already. Don't waste space on empty guff.

Cas Smiley

 on: 2018-02-16 12:39:03 
Started by A-Bomb - Last post by nsigma
TL;DR recruiters are idiots; design for idiots!  Grin

 on: 2018-02-16 11:48:00 
Started by A-Bomb - Last post by princec
As a recruiter (and contractor for some 20 years) here is some general advice about CVs:

1. At the top put all the basic information: your name, availability, notice period, location (and/or willingness to relocate), mobile number, email address, and any languages you speak fluently. Don't put your age or gender in here. Don't mention any social media contact handles.
2. Under that I'd advise a single paragraph describing the type of work you're looking for. Tailor this bit every time to the job you are applying for, so that it looks like you are exactly looking for the role described by the job ad!

That's page 1. This page is the most important page in the whole CV. Make it look neat-as. Use serif fonts as it'll likely be printed.

3. Page 2 of the CV could be a simple trio of tables detailing the years experience you have with: Languages & APIs, Tools and Environments, and Roles. For languages etc. you'd have Java 5 years, C++ 3 years, SQL 4 years, HTML 1 year, Javascript 1 year, Angular/JS 1 year, Swing 1 year, J2EE 3 years. For Tools and Environments you'd have Linux 4 years, Windows 1 year, Eclipse 5 years, etc. and for Roles you'd have Team Leader 1 year, Analyst/Programmer 5 years.

Try to keep those three tables to a single page. Don't include stuff you don't want to be hassled about doing. This page serves as a simple filter for the recruitment agent. Meet enough buzzwords at the relevant length of experience and you're through to the next stage.

4. Page 3 of the CV is your recent experience. Each role you've been in, in reverse chronological order (most recent at the top), with job title, employer, month & year started and ended. One or two paragraphs describing the work you did, particularly any notable achievements or things you learned. Feel free to state that something is confidential and can't be discussed here if necessary. Try to keep this to one page. Nobody cares about what you did 15 years ago - finish it off with something like Before March 1998 - various Analyst/Programmer roles

5. Finally Page 4 of the CV is a couple of paragraphs "About Me". This is where you link to github. Nobody gives a crap if you read books btw. but they might be interested in whether you go snowboarding or have a motorcycle or play D&D, which occasionally are random connections with interviewers that can give you something non-work related to chat about. Big tip: if you are being interviewed it is because the rest of your CV already passes all the criteria for the job, so what the interviewer is looking for is someone they like to talk to. Some interviews have mind-bogglingly pointless technical tests in them. Grin and bear it. You still won't get the job if the interviewer thinks you're boring as f**k or can't talk to them.

Another tip... really really try to keep the whole damned thing to 4 pages or less. Nobody wants to read a tome. Remember they probably have another 20 tomes to read. Yours will stand out because it presents everything they need to know whether to bother interviewing you in a short snappy format, and plenty of hooks for them to initiate asking you questions.

Cas Smiley

 on: 2018-02-16 11:23:57 
Started by BurntPizza - Last post by Damocles
Testing out a workflow on how to model asteroids and smaller moons, (and getting that into an acceptable size for a game model)
Here a first iteration.
(The crater edges are still way too fuzzy...)

 on: 2018-02-16 08:27:48 
Started by A-Bomb - Last post by NuclearPixels
Well the recruiter cannot provide you much feedback because his job is about the initial screening of the candidates... Further, after getting N people into his list, he provides it to someone who actually understands something about game development. The developer or team lead (whoever) chooses a few which seemed interesting to him and asks the recruiter to dismiss the rest..

I agree with what some people say below. The way you are selling yourself is wrong (you might notice, that even if you walk in into the shop it is not guaranteed that you will buy something, so do not build illusions a beforehand).

A few things which I believe can increase your chances for getting noticed (not by recruiters, but by those people who actually make decisions):
1) A GitHub repo with a few small projects. Do your best in terms of coding style, code modularity, unit testing.. Use some patterns, but do not go too deep into that, project full of patterns looks suspicious Tongue.
2) Organize your CV better. I think you have too many subsections and the limits of actual sections are not clear (for example you have an Education section and right after you have a bold text with bigger letters and the eyes are automatically jumping there without noticing that it is an education section)
3) In the working experience, put only the things which are relevant for position (Amazon thing is not in this case). In your case, what I would have done is expanding that "Graphics Engine Programmer" into several projects you have been developing since 2012, with some very short bullet-style description (also use keywords, like Java, Spring, whatever) of the project. If there is a video to the game I would probably put it there. If you do not tell, I have no idea what you have been doing all those 6 years...
4) I would move skills and abilities before the education, split it into several sections and put keywords instead of phrases. Something like:
Advanced: Java, JSF,...
Itermediate: Python, WebGL, ...
Traits: self-learner, ambitious, ...
5) I would definitely add self-learning section at the end, meaning that after completing the education you still educate yourself, put some books there, which you actually read (questions can come about your opinion on the book, etc, so do not risk, lying is bad)

Thank about it the other way around, you are choosing the person among 100, you look into a CV which is messy and does not tell you much about the candidate expertise, would you spend your precious time interviewing that person that you knew nothing about before looking into CV and still know nothing about after looking into it? CV is the first thing the person who is making the decision will look into, is like an elevator pitch, make sure you use those 30 seconds well sqeeze the maximum of those 30 seconds..

Pages: 1 ... 3 4 [5] 6 7 ... 10
xxMrPHDxx (305 views)
2017-12-31 17:17:51

xxMrPHDxx (93 views)
2017-12-31 17:15:51

xxMrPHDxx (146 views)
2017-12-28 18:11:33

Ecumene (310 views)
2017-09-30 02:57:34

theagentd (492 views)
2017-09-26 18:23:31

cybrmynd (521 views)
2017-08-02 12:28:51

cybrmynd (463 views)
2017-08-02 12:19:43

cybrmynd (446 views)
2017-08-02 12:18:09

Sralse (405 views)
2017-07-25 17:13:48

Archive (1312 views)
2017-04-27 17:45:51
Java Gaming Resources
by philfrei
2017-12-05 19:38:37

Java Gaming Resources
by philfrei
2017-12-05 19:37:39

Java Gaming Resources
by philfrei
2017-12-05 19:36:10

Java Gaming Resources
by philfrei
2017-12-05 19:33:10

List of Learning Resources
by elect
2017-03-13 14:05:44

List of Learning Resources
by elect
2017-03-13 14:04:45

SF/X Libraries
by philfrei
2017-03-02 08:45:19

SF/X Libraries
by philfrei
2017-03-02 08:44:05 is not responsible for the content posted by its members, including references to external websites, and other references that may or may not have a relation with our primarily gaming and game production oriented community. inquiries and complaints can be sent via email to the info‑account of the company managing the website of java‑
Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines | Managed by Enhanced Four Valid XHTML 1.0! Valid CSS!