New answers tagged junior-programmer
0
It is legitimate to worry about whether your skillset will be valuable in the future. Working with an obscure language, or with "obsolete" technologies, can in certain circumstances be harmful for a career.
I can say without hesitation that you are not in such a situation. Swing is a wildely used GUI toolkit. It is still maintained, and it is ...
2
I wouldn't focus on the fact that you are learning Swing; focus on the fact that you are gaining experience with Java and all associated technologies and techniques.
Being a Swing application, there are probably all number of different techniques to learn, including good design patterns, good multi-threaded design and if it is a three-tier system, there may ...
4
Of course you have no idea how to write a "generic error mechanism". No one knows how to write a "generic error mechanism" until some requirements are defined. It sounds like all you have is someone's notion that a "generic error mechanism" is somehow required to start this project.
Personally, I would push back on this notion. Writing "generic" anything ...
2
Rejoice in that you aren't doing something you've done a hundred times before. You've found the joy of software development (for me, anyway, YMMV) - learning how to drive while you hurtle down the freeway at extraordinary speeds. This is the kind of thing a great developer lives for and excels at.
My personal process is something like this:
Research. Find ...
8
I think you're suffering more from anxiety than a skill deficit. At some point, wasn't everything new? Have you ever been given a task and not been ablt to solve it to some extent? You're paid to figure things out.
Utilize Your Team - If you're on a good team, you should be able to ask for help. There are things you'll know that even the most senior won't ...
32
I think that everyone will have a different answer but I think the following things are the general answers.
Think about the problem, draw some diagrams, make sure that you know what the problem is that you are trying to solve.
Do research on what you are trying to do. The internet is a valuable source of information. I am not saying ask Stack overflow ...
16
No perfect solution but some things that might help:
break things down into the smallest possible units until you have things you can do
restate the immediate task or problem that are at hand to make sure you really understand them well enough. Then do some analysis yourself and then repeat.
pick the simplest task first, even if it seems too simple.
ask ...
5
It's very hard to find a perfect job. Assuming you find a new one -- what makes you think you can predict the quality of the code base over there before you have been really working on it? Code base is very often a mess.
My experience is that if the people and the pay are appealing then this is something few people can claim and which is worth working for, ...
-1
I am Mainframe Programmer from India with 10 years' of experience in COBOL, Assembler, DB2 ,CICS and JCL. Once intriguing, but now appearing boresome and meet-the-dead-end I want to move out of Mainframe. The problem with mainframe can be squarely atributed to IBM's conservative attitude. IBM captivating z/OS in z/Architecture and not unlocking its potential ...
7
It's largely just par for the course for experience programming, and is one of the key reasons why programmers need quiet space and uninterrupted time to work. Simply put, you need to learn to keep quite a few different things in "working memory" in your mind.
There are aids you can use, though.
Task comments. Any editor or IDE can parse (or has a plugin ...
1
Do you have decent working conditions?
If you're working in open space, with a person nearby who constantly talks on the phone, people are walking all around, you receive new e-mails every five minutes and you can't ignore them, because they come from your boss, you're working on a slow PC where the compile time is about two minutes, etc., I'm not surprised ...
Top 50 recent answers are included
