Timeline for Refactoring Java class for a cleaner design
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 8, 2023 at 18:01 | comment | added | user949300 | Whatever "improvement" you decide upon, make baz and fuz final, so that it is clear that one can't add or change one later. | |
| Dec 7, 2023 at 10:00 | answer | added | Robert Bräutigam | timeline score: 3 | |
| Dec 6, 2023 at 16:26 | answer | added | Doc Brown | timeline score: 2 | |
| Dec 5, 2023 at 19:03 | answer | added | JimmyJames | timeline score: 4 | |
| Dec 5, 2023 at 17:24 | answer | added | user949300 | timeline score: 0 | |
| Dec 4, 2023 at 13:24 | answer | added | user437602 | timeline score: 4 | |
| Dec 4, 2023 at 8:05 | history | edited | Philip Kendall | CC BY-SA 4.0 |
No need to shout
|
| Dec 4, 2023 at 7:48 | review | Close votes | |||
| Dec 10, 2023 at 3:07 | |||||
| Dec 4, 2023 at 5:06 | comment | added | Flater | What's notably missing from this explanation is how you intend to use this object. You can't judge an implementation if you don't know what it's supposed to do. | |
| S Dec 4, 2023 at 3:21 | review | First questions | |||
| Dec 4, 2023 at 7:28 | |||||
| S Dec 4, 2023 at 3:21 | history | asked | user1154644 | CC BY-SA 4.0 |