F
Flexport Engineering
flexport.engineering · Company blog · on HN since 2017
Flexport's engineering team writes about React, linting, code formatting, security findings, and typing a Rails monolith at a freight logistics company.
What HN saysHN mostly sees it in Flexport's hiring posts and in discussions of code formatting tools such as Prettier.
29HN people shared it
3linked it in comments
34stories submitted
655story points
4 years agolast shared
2017people per year2026
Most-shared posts
- 1Flexport is brutally disrupting global trade and international shipping3 people · 5 points · first shared 2017 · 1 comments on HN
- 2Optimizing React Rendering2 people · 131 points · first shared 2017 · 77 comments on HN
- 3Six security vulnerabilities from a year of HackerOne2 people · 53 points · first shared 2017 · 2 comments on HN
- 4Writing custom ESLint rules for your picky developers2 people · 15 points · first shared 2017 · 5 comments on HN
- 5Ending the debate on inline functions in React2 people · 6 points · first shared 2017 · discussion on HN
- 6Upgrading Prettier on a Large Codebase2 people · 5 points · first shared 2018 · discussion on HN
- 7Approximating “Prettier for Ruby” with RuboCop2 people · 4 points · first shared 2019 · discussion on HN
- 8Adding Sorbet to a Rails Monolith2 people · 4 points · first shared 2020 · discussion on HN
- 9Kent Beck's TCR: A pulverizer for coding tasks2 people · 4 points · first shared 2019 · 1 comments on HN
- 10Using mixed integer programming to assign air cargo to flights1 people · 199 points · first shared 2020 · 56 comments on HN
- 11Building Accurate Shipment Timelines – A Sorted Affair1 people · 100 points · first shared 2017 · 18 comments on HN
- 12Isolating Rails Engines with RuboCop1 people · 88 points · first shared 2019 · 1 comments on HN
- 13Flexport relocates trucking headquarters to Chicago1 people · 12 points · first shared 2019 · discussion on HN
- 14How to serve web clients in China: an experiment with Cloudflare's China service1 people · 4 points · first shared 2017 · discussion on HN
- 15Optimizing React Rendering (Part 2) – Mutation Sentinel1 people · 4 points · first shared 2017 · discussion on HN
What HN people wrote when they linked it
moiramreilly · 2017-12-01
Flexport | Software Engineers, Staff Engineers, Data Scientists, Product Managers and Product Designers | San Francisco | flexport.com / flexport.engineering
Flexport's mission is to fix the user experience in global trade and bring the world free trade through technology. Here at Flexport, we share a vision where any two businesses can trade with each other without regard for geographic distance, logistical complexity, or regulatory challenges.
Our services put clients back in control of their logistics and supply chain needs. We offer faster freight quotes, lower prices, improved visibility and notifications, and advanced analytics. Our lean team of ~35 engineers are building products flexible, maintainable products that are reshaping this fragmented industry.
Started in 2013, we've raised $204M from investors that include Peter Thiel’s Founders Fund, Google Ventures, First Round Capital, Bloomberg Beta, Y Combinator, & more.
Check us out if you:
-Want to be part of a close-knit engineering team that releases new code every day
-Take a product-first approach to building software
-Care about the real world functionality of your programming
-Desire to build scalable programs that standardize information flow and increase operational capacity
-Have amazing coding skills and CS fundamentals; and
-Know modern javascript frameworks.
Our stack
We deploy every 20 minutes with our Buildkite CI setup. Our frontend is built with Flow-typed ES2017. We have around 1500 React…
dmnd · 2017-09-22
Flexport is also hiring engineering interns! Contact me via my profile here, or apply directly: https://www.flexport.com/careers/job/221999
You can learn more about what's involved on our engineering blog at https://flexport.engineering.
bjterry · 2020-12-08
The semantic formatting seems better to me, but I feel like I'll get used to almost any reasonable formatting. If you spend enough time with a consistently formatted codebase, your eye will be drawn to the important parts when you review code. In a tiny way, you develop "expertise" with the formatting, and when you look at other code there is an ever-so-subtle friction to understanding it. Manually reindenting code after editing or refactoring it is also pretty annoying, though of course that's the instinct that "code is meant to be read" is intended to argue against.
It's interesting that the creator of Rubocop isn't that bullish on Prettier, because my company literally uses Rubocop to replicate a Prettier-like experience [1]. Rubocop makes a totally decent Prettier replacement, with the right rules. Another advantage of using a separate opinionated formatting tool is that you avoid issues with a diversity of editors which never quite have the same auto-indentation to mess up code diffs.
1: https://flexport.engineering/approximating-prettier-for-ruby-with-rubo…