Last active
August 19, 2022 18:32
-
-
Save maltebucksch/d43ffc0af1170ef230b94c0bf0fe5630 to your computer and use it in GitHub Desktop.
Evaluating a great developer team
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fun testTeamIsAwesome() { | |
val quickBirdTeamMembers = fetchTeamMembers() | |
val awesomeTeamMembers = quickBirdTeamMembers.filter { teamMember -> | |
teamMember.isPassionate && | |
teamMember.isFriendly && | |
teamMember.isConstantlyImproving | |
} | |
assertEquals(quickBirdTeamMembers.size, awesomeTeamMembers.size) | |
} |
Hi! fetchTeamMembers()
should be a suspend
function, and you are not in a coroutine scope 🤔 . So I think that test will not work 🙂
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Nice implementation of all of the surroundings! :-D makes sense from a coding point of view. But it seems a bit too complicated for conveying the message in a simple way inside the job posting. But I guess that wasn't your goal, so --> nice input 👍.
Makes sense! Might put too much pressure on the team because they have to be awesome every single minute. Everybody has a bad unproductive morning from time to time, and that's ok. So let's implement that pipeline but run it only once per week maybe? :)
Valid point. Leads to a philosophical discussion. Is a non-existent team awesome? 🤔 Hard to say. I'd also be inclined to think that a non-existent team doesn't add any value to the world, and is therefore not awesome. Might be a reason to adapt the test.