Timeline for Tetris logic for interview
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 2 at 2:21 | comment | added | STerliakov | Since it's a quick interview question, I'd completely get rid of rotation implementation and just hardcode four positions per element. It's difficult to get rotation correct without tests and running code, as you might have noticed, and there are only few pieces in tetris - no harm from just hardcoding them. | |
| Oct 1 at 11:30 | answer | added | toolic | timeline score: 3 | |
| Oct 1 at 11:30 | history | edited | toolic | CC BY-SA 4.0 |
deleted 1 character in body; edited tags
|
| Sep 30 at 20:19 | vote | accept | charlielao | ||
| Sep 30 at 20:15 | comment | added | charlielao | it's an interview question implementing some aspects of the Tetris game, including rotate, move left/right and clear rows; I meant to get some feedback on my interview performance so the codes are not really complete with test cases and runnable examples etc. Apologies for the confusion. | |
| Sep 30 at 14:19 | comment | added | ggorlen | What is the specification/purpose of this? In other words, can you elaborate on what exact "tetris logic" is to be implemented here? Are there tests, or how are these classes used? | |
| Sep 30 at 12:26 | answer | added | konijn | timeline score: 3 | |
| Sep 30 at 8:14 | history | edited | Toby Speight | CC BY-SA 4.0 |
Summarise the purpose, not the concerns, in the title; fix code fence
|
| S Sep 30 at 6:42 | review | First questions | |||
| Sep 30 at 6:47 | |||||
| S Sep 30 at 6:42 | history | asked | charlielao | CC BY-SA 4.0 |