Chaining has its own benefits. But I think this doesn't fit the definition of "Pythonic". Again, "Pythonic" is highly debatable. But, You can always break down big chain of operations, into smaller chain using good variable naming in-between.
Many operations are implemented as iterator in python on list, like filter, groupby.
Looking at your code, its looks like you're not doing lazy computation. (Correct me if I wrong). This could be huge performance impact, depending upon use case of list.
Remote: Yes
Willing to relocate: Probably yes
Technologies: Python, Flask, PyTorch, Spacy, C
Areas: NLP, CV, Optimization
Résumé/CV: https://read.cv/dipkumar/
Email: [email protected]
Why hire Dip: - Worked as machine learning engineer + research engineer + backend engineer.
- single handedly deployed multiple ML system in production
- I believe creating baseline first and improving from it instead of going with biggest weapon.
- fast learner (worked on various project ranging from stitching photos to speech intent detection to solving NP-hard problems)
Why not to hire Dip:
- Need Research Scientist instead of MLE or Research Engineer
- Need senior (experienced) backend engineer