Timeline for What do you do if you're not a good programmer?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot |
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
|
|
| May 21, 2016 at 17:40 | comment | added | user42272 | @Arwen17 bcstools.com does this work? Just googled "sqr ide" | |
| May 21, 2016 at 16:53 | comment | added | Arwen17 | I love IDEs when they're available. I loved programming in Java in college because the IDE would help out. But SQR and lot of less popular languages dont come with IDEs and no one at my last company was using one. They just used vi, and their own brains, nothing else. | |
| May 21, 2016 at 16:51 | comment | added | user42272 | @Kilisi I added an edit that makes this answer a bit more honest, which might interest you. | |
| May 21, 2016 at 16:51 | history | edited | user42272 | CC BY-SA 3.0 |
added 711 characters in body
|
| May 21, 2016 at 16:39 | comment | added | reirab | Another upvote for "this is what programming is." I think one of the most extreme examples I can recall was a coworker spending 3 or 4 months evaluating a codebase trying to figured out some bizarre behavior. The eventual solution was moving one line of code down a few lines. It happens. Even when developing new code, though, I tend to spend far more time thinking, drawing diagrams, taking notes, etc. on how the system should be designed than actually typing code. There are many days where I don't write any code at all. Welcome to engineering. | |
| May 21, 2016 at 15:25 | comment | added | Kilisi | @Paparazzi So would I, just the timeframe to come up with the plan I was moaning about (unfairly) I often forget how complex some problems can be :-) The guys doing my stuff have 20 or 30% years solid experience, so they make things look very easy. | |
| May 21, 2016 at 15:23 | comment | added | paparazzo | @Kilisi And I would can anyone that started coding for the sake of coding before they had a clear understanding of the problem and a clear game plan. | |
| May 21, 2016 at 15:22 | comment | added | Kilisi | Yep, I thought something similar, so I deleted my comment. Upvoting for saying it's a normal part of programming (which it is) | |
| May 21, 2016 at 15:09 | history | answered | user42272 | CC BY-SA 3.0 |