benmanbs
At the end of the experience they bring you into a room with lights, and you get to delve into what you learned and any assumptions you made about the other people in the group or the guide themself. It was an amazing experience.
[0] - https://www.childrensmuseum.org.il/eng/pages/childrens_activ...
> Go back too much? Use ls to see what’s in the directory you’re in, and then use cd to head back to where you want to go:
In my experience, if I get lost with `cd`, the best way for me to figure out where I am is not to execute an `ls` (because I might be in a folder with no contents, or somewhere with ambiguous content), I would recommend `pwd` ("print working directory").
• Why: Marketing is a 3 trillion dollar industry. We want to enable marketers to put customers first, and ditch their ads.
• Traction: Just acquired by WeWork (https://www.wsj.com/articles/wework-wades-into-enterprise-so...)
• Stack: Java, React.js, Kafka, MySQL, Kubernetes, AWS
• Tech Challenges: Lots of data with strict publish guidelines. Migrating to a microservice architecture.
• Values: People first
- Contact -
I'm Benjamin, a Technical Team Lead at Conductor. I found Conductor 4 years ago through a HR Hiring thread.
Email: [email protected]
• Product: The best-in-class content marketing platform.
• Why: Marketing is a 3 trillion dollar industry. We want to enable marketers to put customers first, and ditch their ads.
• Traction: Just acquired by WeWork (https://www.wsj.com/articles/wework-wades-into-enterprise-so...)
• Stack: Java, React.js, Kafka, MySQL, Kubernetes, AWS
• Tech Challenges: Lots of data with strict publish guidelines. Migrating to a microservice architecture.
• Values: People first
- Contact -
I'm Benjamin, a Technical Team Lead at Conductor. I found Conductor 4 years ago through a HR Hiring thread.
Email: [email protected]
There were some things I intentionally left out (how to write good code, documentation) because I figured those were out of scope of this post (I did try to reference them subtly with the line "the code is in a place where it’s ready to publish"). I also left out some of the things you mentioned (versioning documentation, changelog, channels of communication, SO tag) because I figured those might fall into a Part 2 type of post, where I'd say "Now that you have a first version of your library published, let's discuss how to maintain it."
I'll be honest with you, I had a little issue with the length of this post, so I was trying to balance how much to include or omit.
I really appreciate the feedback, and I'll keep those points in mind for a Part 2 post!