
source{d}
@sourcedtech
Followers
3K
Following
1K
Media
770
Statuses
2K
Data Platform for the Software Development Life Cycle. #EngineeringEffectiveness #MLonCode⠀| GitHub: https://t.co/4XuUmDJURU⠀| website: https://t.co/Gvetg0CBGy
Remote-first. Offices: San Francisco, Seattle, Madrid.
Joined November 2015
In case you missed today exciting news from @sourcedtech 🎉📢🗞️. - Private beta of @sourcedtech Community Edition is now open - more info in this blog - @sourcedtech Enterprise Edition is now GA. #CodeAsData #EngineeringOps #SDLC.
0
2
21
source{d} analysis of the @cloudfoundry codebase: The results show a mature and complex architecture yet extraordinarily active and agile. #MLonCode
1
2
5
Data Retrieval pipeline at source{d}."Data collection and processing might be less sexy than #MachineLearning but nevertheless is crucial for any progress" #MLonCode
1
0
1
How do you know if your software is good enough? @rich_archbold, VP of #Engineering @intercom shares his engineering standards that will help protect you from easily avoidable mistakes #DevOps
0
3
8
We analyzed all the @TensorFlow git repositories with source{d} EE to extract interesting insights for the Tensorflow community. Check out our summary here: View the dashboard of the entire analysis here: #MLonCode
0
0
1
RT @p_e_fraisse: 👏 Not only for architects but for a whole organization This is what I am used to call #CodeAsData from a few years. Hope t….
0
2
0
💥 ". Vendors such as source{d} are enabling developers to build increasingly complex software faster, with high quality, and better user experience.” 💥@marksdriver , @Gartner_inc #MLonCode #GartnerCoolVendor
0
1
1
Yesterday we shared Part 1. Here is Part 2 of "Clean code. Why bother?" by @pauxdsantamaria, co-founder of @uppernauts. 1. Clean code leads to better practices.2. Reviewing PRs is hard work.3. Reusability.4. Faster bug fixing
0
2
5
Check out source{d} Lead #MachineLearning Engineer, @vadimlearning's article on @kdnuggets "What is #MLonCode?" 🤖🎓 💻 📄
0
0
3
@sourcedtech CEO, @Eisokant had his article, "How #MLonCode Could Disrupt #SoftwareDevelopment," published on @EnterpriseAI_
0
0
0
"Clean Code. Why bother?" via @pauxdsantamaria, Co-Founder of @uppernauts .1. Your teammates will thank you .2. Think about your future self .3. Messy code tends to get messier .4. Faster decision making .5. Reduce repeated code .6. It feels great!
0
4
7
Paper Review: "Import2vec - Learning Embeddings for Software Libraries" by Hugo Mougard, Senior Machine Learning Engineer at source{d}.#MLonCode
0
0
5
Learn how to "get the product feeling great, the #Engineering team feeling productive and proud of delivering a high-quality product, pumping out features while keeping the bugs down" by former @facebook and @YouTube, @radoshi 💻 💡 🎓🐜
0
0
1
We analyzed all the @TensorFlow git repositories with source{d} EE to extract interesting insights for the Tensorflow community. Check out our summary here: View the dashboard of the entire analysis here: #MLonCode
0
0
1
Paper review: "code2seq - generating sequences from structured representations of code" by source{d} Engineer, @seoul_engineer #MLonCode
0
0
5
Multi-GPU #DeepLearning at source{d}.Learn how we solved several problems in order to train neural networks with @Tensorflow 2.0 on several local GPUs in our ML cluster. #MLonCode
0
0
1
Top 4 metrics to measure your #Software Delivery Performance.1. Change Lead Time.2. Deployment Frequency.3. Change Failure Rate.4. Mean Time to Restore (MTTR).#EngineeringObservability
0
2
9
🎓 #DeepLearning on #Dataframes with @PyTorch . "The goal of this post is to lay out a framework that could get you up and running with deep learning predictions on any dataframe using PyTorch and Pandas." via Mike Chaykowsky
0
0
4