130 reputation
4
bio website
location Sweden
age 29
visits member for 3 years, 2 months
seen 2 days ago

Software Engineer from Lund


May
23
comment Working on someone else's code
+1 and +1 to 5arx's comment. I've done integration work at REALLY large companies where the version control system consists of writing the date, your name and a comment in the file. After being used with working with git, this seems frighteningly inefficient and bug-prone.
May
22
comment Should we avoid object creation in Java?
+1: Unnecessary object creation (or rather cleaning up after removal) can definitely sometimes be costly. 3D Graphics/OpenGL code in java is one place where I have seen optimizations done to minimize the number of objects created since GC can otherwise wreak havoc with your framerate.
May
2
comment Teaching programming by solving puzzles?
+1, was going to suggest SpaceChem myself.
Apr
19
awarded  Teacher
Apr
19
answered Are there guidelines on how many parameters a function should accept?
Apr
11
comment Is the phrase “never reinvent the wheel” suitable for students?
It can be ok to reinvent wheels when you are creating extremely optimized code. Standard libraries are very useful, but it is often possible to create something that is less general but faster.
Apr
9
comment Techniques for getting off the ground in any language
+1, I agree with AndyBursh. Sounds like a really good task that tests control logic, map/reduce-functionality, string handling and IO. The only thing missing would be some kind of graphics, but that might not always be possible in all languages or systems.
Apr
5
comment How do you maintain focus when a particular aspect of programming takes 10+ seconds to complete?
Ubuntu has a nice alert alias setup in .bashrc. It depends on libnotify, but if it is installed, you can do command; alert and it will give you a desktop alert when finished specifying which command it was that finished. Really useful for lengthy compilations or tests.
Mar
12
comment How do I review my own code?
Getting into the right mindset is really important. I find that it helps if I actually print out the code and go through it on paper with a marker pen. Then I cannot change anything when reviewing (which prevents me from going into coding mode) and can easily scribble comments and movement arrows on the paper.
Mar
12
awarded  Supporter
Mar
12
comment How do I review my own code?
+1 for short term review suggestion. Using git to view all changes between different points in time can really help cleaning up the code.