Creează un cont pentru a te abona la acest blog și a-i urmări articolele pe pagina Lectură.
-
Short vs. long-term gain, incremental vs. disruptive innovation, and resume-driven development.
-
I wish I started sooner.
-
Pointers to think through your methodology and implementation, and the review process.
-
Three documents I write (one-pager, design doc, after-action review) and how I structure them.
-
Access, serving, integrity, convenience, autopilot; use what you need.
-
What the top teams did to win the 36-hour data hackathon.
-
Design and architecture, tech stack, methodology, results, and lessons learned.
-
What I learned about hiring and training, and fostering innovation, discipline, and camaraderie.
-
Stop procrastinating, go off the happy path, learn just-in-time, and get your hands dirty.
-
Why did I start writing?
-
How to increase the chances of getting called up by recruiters?
-
Why real-time?
-
A public roadmap to track and share my progress; nothing mission or work-related.
-
Wrapping up 2020 with writing and site statistics, graphs, and a word cloud.
-
A short story on flying daggers and life's challenges.
-
Time to clear the cache, evaluate existing processes, and start new threads.
-
How he switched from engineering to data science, what "senior" means, and how writing helps.
-
How did you set up your site and what's an easy way to replicate it?
-
Data cleaning, transfer learning, overfitting, ensembling, and more.
-
Interview questions you should ask and how to evolve your job scope.
-
A personal take on their deliverables and skills, and what it means for the industry and your team.
-
Setbacks she faced, overcoming them, and how writing changed her life.
-
What questions do they answer?
-
DNS server snafus led to email & security issues.
-
Not 'How to build a data science portfolio', but 'Whys' and 'Whats'.
-
Step-by-step walkthrough on the environment, compilers, and installation for ScaNN.
-
Building prototypes helped get buy-in when roadmaps & design docs failed.
-
As careers grow, how does the balance between writing & coding change?
-
Emphasis on bias, more sequential models & bandits, robust offline evaluation, and recsys in the wild.
-
What if the alternative was nothingness?
-
What's an average day like?
-
For years I've refined my routines and found tools to manage my time.
-
My tools for organization and creation, autopilot routines, and Maker's schedule
-
A step-by-step of how to migrate from json comments to Utterances.
-
Checking for correct implementation, expected learned behaviour, and satisfactory performance.
-
Should I switch from a regex-based to ML-based solution on my application?
-
My chat with James Le about my experience, leadership, agile, ML in production, writing, and more.
-
Why read papers, what papers to read, and how to read them.
-
Becoming a senior after three years and dealing with imposter syndrome.
-
How not to become an expert beginner and to progress through beginner, intermediate, and so on.
-
Examining the broad strokes of NLP progress and comparing between models
-
Why (and why not) be more end-to-end, how to, and Stitch Fix and Netflix's experience
-
Updating our FastAPI app to let users select options and download results.
-
Surprising lessons I picked up from the best books, essays, and videos on writing non-fiction.
-
Why OMSCS?
-
I couldn't find any guides on serving HTML with FastAPI, thus I wrote this to plug the hole on the internet.
-
Ever revisit a project & replicate the results the first time round?
-
It's not enough to have a good strategy and plan.
-
I wanted to add my recent writing to my GitHub Profile README but was too lazy to do manual updates.
-
I thought giving it my all led to maximum outcomes; then I learnt about the 85% rule.