Location: San Francisco, CA
Remote: No
Willing to relocate: No
Technologies: Java, Python, JavaScript, Rust, Elm, Flask, SQL, gRPC, Docker, Kubernetes, AWS, Google Cloud, Apache BEAM, Google Dataflow
Résumé/CV: http://alexshadley.com/resume.pdf
Email: shadleyalex@gmail.com
Software Engineer backend generalist with one year of industry experience, spent past year at rideOS developing software to solve the vehicle routing problem at scale. Excited about opportunities at small startups (less than 10 eng preferably) where I'd be able to own products end to end, move quickly, and grow fast.
Hey! As someone who isn't super familiar with this space, I'm a bit confused about who your target user is. At first I thought it was for people who have a mobile app and want to publish it on a bunch of stores, but the APIs are all about querying products and customers, so I guess it's for integrating with eCommerce platforms? A concrete example use case on your website would help explain this to me a lot!
Browsing a bit through the doc I believe this is targeted to developers that build "apps" that online merchants can (buy and) use on their e-commerce website.
I agree with alex: a sample app would probably make it more clear!
advice from someone ina similar area: STARTER app not SAMPLE app. The former gives your clients a starting point to build production applications; the later is usually some throw-away sample code that quickly goes stale and causes nothing but support headaches. By extension, you will need to dedicate ongoing resources to keep this up to date; that's what you expect of your clients, so I hope you enjoy dog food!
Likewise very surprised! I've found that Software Engineering as a field is great for knowledge transferring between jobs -- the ability to design and reason about systems transcends individual languages and tools.
I graduate this May with a CS degree, that about mirrors my experiences. The vast majority of competent and even semi-competent students have no problems getting good paying internships, and jobs out of college. I appreciate that unpaid internships are a really bad situation in some fields, but fortunately CS is pretty lucrative right now.
Yes, thank you! Going without ADTs and pattern matching after having them is unbearable. All I really want is Rust but easier to use, maybe I should just bite the bullet and dive into Rust?
From an ex Go-er (5 or 6 years professionally?), now in Rust for a bit over a year, I can say that Rust in the majority of the cases is "just as easy" as Go.
The thing with Rust is it gives you a lot more of the complexity rope if you desire to hang yourself with it. But, a realization I had early on, was that I didn't _have_ to. Not everything has to reuse perfect lifetimes or maximum possible generics. You don't have to chase every latest feature (Async, I'm looking at you). Without all of that, Rust is still an amazing language.
What I found most amazing after leaving Go was not something I expected: Iterators. Being able to easily mutate complex data structures, filtering in complex ways, zipping, chaining, etc. I could do the same exact thing in Go mind you, but in Go I found myself writing helper functions all over the place. In Go, my code felt so spread out, and was hard to just look at in one screen to understand. Rust (and Iterators) made so logic concise that you could view it in one screen and make sense of it.
Keeping code "locality" was oddly, by a large margin, my favorite thing about Rust.
