HN user

ARolek

306 karma

Technology generalist currently working on Scoutred.com.

Posts11
Comments25
View on HN

GloveBox | Product System Engineering | Denver CO | Fully remote (US only) | $150k + benefits.

GloveBox is an InsurTech with an innovative platform that’s changing how insurance works for everyone involved. We believe the industry has long needed a transformation, and we're here to build it—bridging the gaps between policyholders, agents, and carriers through seamless, powerful connections. Backed by industry-leading InsurTech VCs, influential agencies, and top insurance experts, GloveBox is breaking down outdated barriers with a clear mission: to make insurance transparent, empowering, and accessible for millions.

As a Product System Engineer at GloveBox, you’ll be instrumental in developing core web services and APIs. You will be heavily involved with the design and implementation of system level enhancements, from the database all the way through public facing APIs. This role will have an emphasis on building out CRM and user notification / communication capabilities.

GloveBox is primarily developed using open source software. We also believe in giving back to the community, and support contributing back to projects that we use. Our back end system tech stack includes the following: Go, Postgres, Clickhouse, Docker, Git, Linux (Ubuntu), AWS (ECS, Lambda, SQS, API Gateway, S3, Cloudfront, etc.)

If you're interested in this position, you may apply here: https://wellfound.com/l/2AKRks

I just wrapped up a Go based SAML integration and I was initially using your package. I encounter a bunch of issues with namespaces, and eventually ended up using xmlsec1 directly against a formed up XML template. I agree with you, SAML should go away. This was my first experience with it, and the nuanced complexities were so exhausting. I’m glad the integration is done...

Killer work Alex! It's crazy you just rolled this out. We have been in development on something very similar but have yet to make a public push on the product. The main difference is we host the vector source file and build rasters from it. This helps maintain top quality at any size, and allows us to output to additional formats (i.e. PDF).

The product is still in alpha, but it's amazing how many similarities we came to with the URL scheme design. For example, image embedding:

https://img.ogol.io/<domain.com> example: https://img.ogol.io/ogol.io

we also support downloading

https://dl.ogol.io/<domain.com> example: https://dl.ogol.io/ogol.io

Each logo also has it's own page to make working with the asset outside of an API easy.

https://ogol.io/ogol.io/nn0ymd

Our approach requires companies to confirm their domains and associate a vector logo with the domain. Your strategy obviously provides a lot of logos right out of the gates. Logos are such a pain to deal with, it's great to see the problem being attacked from a few different angles.

Four years of Go 13 years ago

I spend about 30% of my time system side in Go, and the rest in Node.js. I'm working to migrate almost all of my time to Go. The language is fun to work in and, personally, the overall experience is much improved over Node.js. It's exciting to see the momentum behind the language and the great people who are attracted to it.

I use to think this was true too, but it was clarified for me on at https://en.bitcoin.it/wiki/FAQ#Where_does_the_value_of_Bitco...:

"It's a common misconception that Bitcoins gain their value from the cost of electricity required to generate them. Cost doesn't equal value – hiring 1,000 men to shovel a big hole in the ground may be costly, but not valuable. Also, even though scarcity is a critical requirement for a useful currency, it alone doesn't make anything valuable. For example, your fingerprints are scarce, but that doesn't mean they have any exchange value."

I use Sencha Touch on a daily basis, and have used it since version 1.0 (v2.0rc is now out). Clients love it because it comes close enough to native performance for data presentation apps. I also enjoy writing apps entirely in JS. I have also learned a lot about JS reviewing the source code.

The biggest downsides of Sencha Touch I see are: 1. Initial load. The framework is pretty large, even compressed, but CDN, gzip, and cache.manifest files help

2. Device support. Right now they they only support Android and iOS, but this fits the majority of my target.

3. Learning curve. Coming from a jQuery background it took awhile to understand their approach.

I love jQuery for desktop dev. When I tried a previous version of jQuery mobile the experience was not as good overall as Sencha Touch. Looking at the release notes for JQM 1.1, I will be giving it another try.

Really cool idea. We could use this everyday. Have you thought about what the price is going to be? Will it be per doc, or per GB of storage used?

This is a great idea. Often when I do projects through Elance I bring in team members to supplement different parts of the project. It would probably be beneficial to have a point of contact for each project as communicating with clients takes a ton of time. Otherwise one person turns into project coordinator and misses out on the fun stuff ;-).

Overall I love this idea and wish you great success! Keep it up.

I have had great success with Elance.com. At first I had to bid the projects on the lower end to get some ratings. After I had a few happy clients and a few 5 star ratings I started receiving 3-4 proposal requests a week. I also tried oDesk, but did not see the same results.

Thanks everyone for the solid feedback! The feature requests and critiques are invaluable. This was an alpha version we put together to see what type of response we got before we started to develop additional features.

@Adrianwaj - I dig your favorites video idea. I'm going play with some interface designs and see what I can come up with. You have a lot of great suggestions here. I think we can incorporate most of them over time, but I want to avoid having too many features and making the app too complicated for the user. I do appreciate all the great ideas. Thanks!

@iwr - I was debating between wrapping the YouTube chromeless player in Flash or JavaScript. To achieve a full screen button, I would need to wrap the player in Flash, but overall I much prefer working in JS, especially with the push towards HTML5 and CSS3. You bring up a great point about dual screens. I think as HTML5 develops, so will a solution. As browsers continue to trend towards being more minimalistic maybe a they will soon offer a JS full screen mode.

@makuro - We have not developed the seek scrubber or volume control quite yet. I wanted to see the overall response to the core application before I started working on those additional features. I have designs for them though, so keep an eye on us. ;-)

@iworkforthem - Thanks for the positive feedback! I would love to use this interface to build out content channels for others. You bring up a really good utility here. Using the Data API we could easily grab all the videos from a certain user, and booya you have a custom channel. Ping me if you know anyone who could use this. vidi@vici.tv

@Vantra - Someone else mention that thumbs up \ thumbs down idea too. We are essentially doing that with the next button. We figured if you hit the next button the video was not engaging enough for you to watch all the way through. We capture that data and consider it when choosing videos for everyone. Our back end crowdsources what videos are the most entertaining using the next button and a few other pieces of critical data pumped through a some cool ratio analysis and comparison algorithms. With this AI, VICI.tv will filter though YouTube and deliver better and better content over time.

Again, thanks for all the comments and keep them coming. We will put in more features based on what people suggest the most. Any questions, feel free to find us on twitter (@VICItv) or drop us a line: vidi@vici.tv.

Lastly, what channels are everyone's favorites? I saw so many awesome ones pop up yesterday. A couple of my new favorites are Parkour and Chris Farley.

Alexander