* various political machinations behind the scenes
* the gutting of the team I'm on
* the sunsetting of the project I'm on
* my contract coming to an end
The temptation to just browse reddit, twitter and youtube is one I'm struggling to resist.
271–280 of 316 posts
* various political machinations behind the scenes
* the gutting of the team I'm on
* the sunsetting of the project I'm on
* my contract coming to an end
The temptation to just browse reddit, twitter and youtube is one I'm struggling to resist.
Java websphere stack is such a waiting game. Besides I don't love code.
If you're running Websphere locally, exclude WS folders from anti-virus scanning. It will considerably speed up WS start up.
Lack of sleep, have a young child at home ... can't really focus on anything else but documenting own older code or watching lectures right now.
Instead of sitting down and writing a draft code version, then reworking it, then reworking it again, then realizing there's a better way to do/structure the same, discarding it and making a clean version I was forced (by the baby-centric lifestyle) to think it all through in the head first. I would then sit down and emit the final version on the first try. The best part is that it also took noticeably less time than the iterative "hands-on" approach.
Earlier quoted context omitted.
Good point, happened to me today. The UI requirements to my ticket didn't make sense. The changes the other dev wanted would have took us possible days. I was hesitant to start, so I asked another dev... He said something totally different, he kept referring to something the designer wanted, but it didn't make sense to me, either. I called the designer and she told me she never said that and we agreed on something el…
Just in case you aren't aware, but this is what agile is actually about. Big part of it is communicating with the team. Not having a fixed plan and adjusting when having new insights is also part of it, but I think the communication part is often overlooked. In the classic methodologies, you had some document, that told you what to do. In agile you should talk about things and just use a few notes to summarize what s…
Earlier quoted context omitted.
> I'm sure a lot of people have this problem: naming things. Can't code until you figure out what that variable should be called. i, j, k, foo, bar, baz, and don't waste a moment thinking about it till your solution is finished and warrants a once-over (or till it has grown sufficiently complicated that a real name is finally necessary even if temporary -- try to work in small enough units that this never happens).
I generally think that if I can't find a good name for a thing, I don't actually know what it does yet, so Im not ready to code it. I, j, and k have clear definitions as basis vectors, so they can be used, but I don't think I'd ever call a variable foo or bar
https://geekhack.org/index.php?topic=95872.0
I do think we need a modern hacking keyboard though.
Because Coding is not Working. Coding is not Planning. Coding is not Being Efficient. Coding is not Accomplishing Goals. Coding is not Saving Money. Coding is not Gaining Customers. I am getting paid to get things done in a good manner. If I wanted to have a house built for me, I would not expect to pay somebody and immediately have them start laying bricks without them looking at the land, taking soil samples, sketc…
Coding is a means, not an ends.
Working hard is easy. Working smart is hard.
Earlier quoted context omitted.
Good point, happened to me today. The UI requirements to my ticket didn't make sense. The changes the other dev wanted would have took us possible days. I was hesitant to start, so I asked another dev... He said something totally different, he kept referring to something the designer wanted, but it didn't make sense to me, either. I called the designer and she told me she never said that and we agreed on something el…
Just in case you aren't aware, but this is what agile is actually about. Big part of it is communicating with the team. Not having a fixed plan and adjusting when having new insights is also part of it, but I think the communication part is often overlooked. In the classic methodologies, you had some document, that told you what to do. In agile you should talk about things and just use a few notes to summarize what s…