IgorPerikov ( Igor Perikov )

Igor Perikov IgorPerikov @yandex Russia, St. Petersburg https://medium.com/@perikov.igor interested in building resilient applications, chaos engineering

repos

gists

followers

following

IgorPerikov/mighty-watcher 41

Open source made easier

IgorPerikov/etcd-service-discovery 2

IgorPerikov/github-api-client-integration-testing 2

IgorPerikov/botd 1

IgorPerikov/hollow-maven-plugin 1

IgorPerikov/hollow-maven-plugin-examples 1

IgorPerikov/shopx 1

IgorPerikov/advent-of-code 0

IgorPerikov/archived-mighty-watcher 0

Helps find issues available for contributing

IgorPerikov/bank-processing-test 0

startedchaos-mesh/chaos-mesh

started time in a day

push eventIgorPerikov/botd-spotify-integration

IgorPerikov

commit sha 7e45a371e9d2eb8c8e250b3490fd9bf0fdd58b30

basic domain objects

view details

IgorPerikov

commit sha 7d7e036e54ad73bb9583b28ccdef729ec3d1cc88

parse data from google spreadsheet

view details

push time in 5 days

push eventIgorPerikov/botd-spotify-integration

Igor Perikov

commit sha 58de50efd24815950de850fa4f4a51477ece45a0

Create LICENSE

view details

push time in 5 days

push eventIgorPerikov/botd-spotify-integration

Igor Perikov

commit sha 219ab8ab06f1b21c4aadce52272885ba0a97d9e2

Create README.md

view details

push time in 5 days

create barnchIgorPerikov/botd-spotify-integration

branch : master

created branch time in 5 days

created repositoryIgorPerikov/botd-spotify-integration

created time in 5 days

issue openedLeetCode-Feedback/LeetCode-Feedback

322. Coin change question lacks details on inputs

Your LeetCode username

IgorPerikov

Category of the bug

[x] Question
[ ] Solution
[ ] Language

Description of the bug

https://leetcode.com/problems/coin-change/

Description has no details on inputs and it's impossible for a person to know what to expect, maybe amount can be so big, that making array of size amount wouldn't pass memory restrictions. Turns out system has a test case which will check for int32 overflow edge case, but it's kinda irrational to try to predict all possible limitations, when none are stated

My suggestion is to add input restrictions to the description to clarify this

created time in a month

push eventIgorPerikov/botd

Konstantin Perikov

commit sha 9cdf4a64c512ee490a04ba0f8938b90ead63d197

make code more pythonic way (#1) * make code more pythonic way * delete unittest * add requirements installation in readme

view details

push time in 2 months

PR merged IgorPerikov/botd

make code more pythonic way

+43 -25

3 commit in MysterionRise/botd/tree/master IgorPerikov/botd/tree/master