Timeline for How to prevent making silly errors while programming on a fast faced project and also maintain the project structure,
Current License: CC BY-SA 4.0
28 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Aug 27, 2021 at 20:01 | history | edited | Glorfindel | CC BY-SA 4.0 |
Improved formatting
|
| S Aug 27, 2021 at 20:01 | history | suggested | Chait | CC BY-SA 4.0 |
Improved formatting
|
| Aug 27, 2021 at 17:52 | review | Suggested edits | |||
| S Aug 27, 2021 at 20:01 | |||||
| Aug 27, 2021 at 15:32 | answer | added | Rad80 | timeline score: 0 | |
| Aug 27, 2021 at 15:07 | history | protected | gnat | ||
| Aug 27, 2021 at 14:43 | answer | added | Flater | timeline score: 0 | |
| Aug 27, 2021 at 13:52 | history | edited | candied_orange | CC BY-SA 4.0 |
I also make mistakes.
|
| Aug 27, 2021 at 13:46 | answer | added | John Peters | timeline score: 0 | |
| Aug 27, 2021 at 4:46 | answer | added | T.kowshik Yedida | timeline score: 0 | |
| Aug 26, 2021 at 22:23 | comment | added | gnasher729 | You should definitely turn on all reasonable warnings that your compiler has, together with a “no warnings” policy. And pick a programming language that helps. | |
| Aug 26, 2021 at 22:21 | comment | added | gnasher729 | On a project where I was the sole developer I did code reviews. Nothing got committed unless it was reviewed (by me) and tested (by me). You just have to focus. Some formal tools would help. And you have to get used to the fact that this will seem to slow you done since you do more work before something is committed. On the other hand you save a lot of time fixing stupid bugs. | |
| Aug 26, 2021 at 20:06 | answer | added | Joop Eggen | timeline score: 1 | |
| Aug 26, 2021 at 19:27 | comment | added | Rik D | The best way to look more professional is to actually behave more professional. Often this means going slower to finish faster. Write automated tests but don’t forget to run your own code and look at the results, both locally and in the test environment. | |
| Aug 26, 2021 at 18:49 | comment | added | cloudCharm | Yes, I have contract with the company , some fixed weekly hours .By "easily seen", i mean when we do a demo ,or they run the code on their local | |
| Aug 26, 2021 at 18:48 | review | Close votes | |||
| Aug 31, 2021 at 3:09 | |||||
| Aug 26, 2021 at 18:29 | history | edited | candied_orange | CC BY-SA 4.0 |
added 1 character in body
|
| Aug 26, 2021 at 18:19 | comment | added | Filip Milovanović | BTW, can you clarify (might be relevant to how you approach this): you say you are a contractor - so you're not officially an employee of this company, but more like self-employed, and there's a contract between two independent parties (you and the startup)? Or that's not what you meant? | |
| Aug 26, 2021 at 18:19 | comment | added | Filip Milovanović | Perhaps you are being mismanaged? What do you mean by these bugs are "easily seen" by your manager - are they doing code reviews? If so, then how are you wasting their time? If they want to put the pressure of such a fast-paced environment on a single developer, then they can't complain that you are stressed and are creating bugs. If they don't want that, then why are they indulging users so much? Maybe they should hire more people. Maybe they should also manage these change requests? They must be able say "no" to users, or at least postpone requests. Don't assume it's all on your shoulders. | |
| Aug 26, 2021 at 17:18 | answer | added | Jon Raynor | timeline score: 5 | |
| Aug 26, 2021 at 16:55 | answer | added | candied_orange | timeline score: 5 | |
| Aug 26, 2021 at 16:32 | history | edited | candied_orange | CC BY-SA 4.0 |
edited body
|
| Aug 26, 2021 at 16:25 | history | edited | candied_orange | CC BY-SA 4.0 |
I've fixed the errors I can spot. See if you can fix any I missed.
|
| Aug 26, 2021 at 15:33 | comment | added | cloudCharm | i know my manager is right , but i m trying my best and seeking for help | |
| Aug 26, 2021 at 15:20 | history | edited | cloudCharm | CC BY-SA 4.0 |
added 24 characters in body
|
| Aug 26, 2021 at 15:14 | comment | added | amon | Slow is steady, steady is smooth, smooth is fast. Stop trying to do more stuff faster. Take the time to finish one thing properly before starting the next. For example, writing a few tests for the code you touch would detect most null pointer errors. This seemingly takes more time, but might actually allow you to deliver faster and with more confidence. If your team lead can review your code and spot errors that is not wasted time, that helps delivering working software to the end user faster. Make sure to get enough rest. | |
| Aug 26, 2021 at 15:12 | comment | added | Philip Kendall | "and have no attention to detail" <- with all due respect, if you put as much attention to detail in your code as you have done to this badly formatted wall of text, I think your manager has a point. | |
| S Aug 26, 2021 at 15:05 | review | First questions | |||
| Aug 26, 2021 at 18:12 | |||||
| S Aug 26, 2021 at 15:05 | history | asked | cloudCharm | CC BY-SA 4.0 |