Kaoru
Kohashigawa

Taste of Awesome


culture

![Trees after a fire](https://images.unsplash.com/photo-1442473483905-95eb436675f1?crop=entropy&fit=crop&fm=jpg&ixjsv=2.1.0&ixlib=rb-0.3.5&q=80&w=900) [Photo by Dikaseva](http://dikaseva.com/?utm_medium=referral&utm_source=unsplash) On Monday I re-entered the job market. Turns out international / domestic adoption is a lot more difficult than any of us thought. The founders, instead of pretending things would be alright and fake it, decided to go back into research mode. **Great call**, even if I got the short end of the stick. I don't regret joining the team. In my 1.5 months of being there I got to experience a great culture. ### Culture of Criticism One of the things that attracted me to Binti was the _culture of criticism_. I would meet with my team members weekly or bi-weekly and discuss things that we could improve upon. There was a real desire to improve. It was just about improving technical skills but also soft skills. Things that make you a better team member, a better person. Our industry, I believe, needs more of that. ### Impact It was awesome having a bigger goal than myself. I felt like I was making a real difference in the world. I wasn't fixing a minor inconvenience for the privilege ( although I admit I enjoy those benefits ), I was helping [create families](https://binti.com/about/). ### Open It felt really nice to be able to share my opinions and thoughts without repercussion. There were real discussions weighing pros and cons on certain issues. There was no top down marching orders, without argument. There were orders, but it was well discussed, allowing all parties to share their input. Even if we did not agree. I'm still in awe of the aspiration of Felicia and Julia. To take on the beast that is adoption. I hope they do not fail. I got a taste of what it's like to be part of a company that _seriously_ invests in the development of their employees. I want to continue to work for companies of the same caliber.

Breaking the Mold


culture

![Tv in the grass](https://images.unsplash.com/photo-1438109519352-a52c41243c1a?crop=entropy&fit=crop&fm=jpg&h=600&ixjsv=2.1.0&ixlib=rb-0.3.5&q=80&w=900) [Photo by Pablo GarciaSaldaƱa](http://www.proyectohansbach.com/?utm_source=Unsplash&utm_medium=website&utm_campaign=unsplash) **TLDR:** Any time you join a new team, you have to let go some of your old habits and pick up some new ones. Yesterday I noticed something at my new job. I'm so used to moving fast and getting something to work that I was more willing to rip out a gem than to work through the problem. Let's add some context. I'm currently working on implementing a messaging system at [Binti](https://binti.com). To gain the most ground we decided to try out a gem called [mailboxer](https://github.com/mailboxer/mailboxer). To be honest their data model is a bit overly complex for what we needed. It's a mini app within itself ( technically it's a Rails engine ). Some simple questions forced me to write some long awful, buggy queries. For example, is there an existing conversation between these two users? At my last job, I care more about speed than maintainability. Ideas came in left and right and I needed to ship them yesterday. What I have to watch out for is taking the habits of what worked in my last job into my new job. That's part of the on-boarding process I suppose. Figuring out how to develop in the same rhythm as the rest of the team. I need to realize, I have the luxury of taking my time now. A good problem to have.