I built a home-grown scanner like this one (not with ZBar though) for my asset tracking web app (www.assetbots.com) and agree that for 1D barcodes a cheap bluetooth or USB scanner is hard to beat.
We support both (camera and external), but surprisingly a lot of our customers find the camera good enough. Code 128 is our second-most scanned symbology behind QR.
I launched Assetbots (https://www.assetbots.com/) last year and went through a lot of ups and downs transitioning into the "people give me money" phase of the SaaS journey.
This year I plan to go all-in on scaling customer acquisition and getting the business out of infancy and into the next level of growth.
I never realized just how bad this can be until I started selling/marketing my startup. I was so confused by the reaction to my participation on a few subreddits where my target customers hang out - I had never experienced anything like it before.
I started to see patterns (not only against my posts personally, although I quickly stopped trying to participate) because I began to understand the market players. It's unreal how inauthentic most of the content actually is and how much of it is straight up shill marketing. I suspect this is true for a large number of niche forums where specific products or services become "blessed" by the community.
The only way to accomplish this is with either a large network of puppet accounts or with the support of the moderators. Probably both.
I've been a Replicache user since v7 when it was distributed as wasm - it's now v10 for General Availability. My use case is quite a bit different than this demo - I'm making a bog-standard back office SaaS with it [0]. It's been great though. Very productive and the end result feels very fast.
I'm also working on a similar product, but targeted toward small businesses (https://assetbots.com/). I agree that the simplicity is nice here. I've done a lot of customer interviews and demos at this point, so here's my free advice:
- Custom fields are a must.
- An IRL link (an "asset tag") is nice, but honestly not critical, even for most small businesses. This changes as users become more accustomed to having an inventory.
- Users say they want hierarchies but they almost never do in practice (e.g., nested folders or containers).
I'd love to chat inventory product design any time. Feel free to email me (my email is in my profile). Good luck!
This is really cool! I'm working on an asset tracking application right now (https://www.assetbots.com/), and generating labels are a big part of the workflow. My roadmap calls for simply generating Avery sheets.
But it would be AWESOME if I could let a user click a button and send them to a labellive:// URL and have it just work. I'll explore a little and see if there's a mom-tested way to make this usable.
I just launched the marketing site on Monday. I'm 38 with a spouse and two small children. I've been a CTO of two SMBs over the last few years and needed to build something of my own. It's the craziest thing I've ever done.
The industry is end-of-life IT assets. It's a big industry with a lot of steak dinners that you can make a decent living at by grinding. I was introduced by a buddy of mine who's managed to build a good no-tech business in the niche.
My thesis is that there's opportunity around "platforming" the service with integrations and automation. Compliance and convenience are big drivers for customers, so traditional marketplaces have failed to take off.
Shotzoom is an app development company that creates market leading mobile and web experiences in sports and fitness. We pride ourselves on creating the highest quality products in our industry, and have received numerous accolades such as the Apple Design Award. Our newest app, Golfshot: Golf GPS, has been featured multiple times on both the App Store and Google Play.
We’d really like you to:
• Be a great Android developer, with one or more fully-developed apps under your belt.
• Have 2+ years of experience developing mobile applications.
• Be action- and detail-oriented.
• Be comfortable working without much organizational hierarchy or direct oversight.
Ideally, you should:
• Be an expert in object-orientation, eventing and delegation, and other modern programming styles.
• Be excited to develop on all of Android’s myriad form factors, from tablets and TVs all the way down to watches and Android Wear.
• Have familiarity with or an interest to learn other mobile platforms such as iOS with Objective-C, or even Windows Phone with C#.
• Have some technical presence on the web, such as a GitHub profile, StackOverflow profile, or a personal website.
If you're interested, please feel free to contact me personally: [email protected].
We're actually unsure of market size, except for anecdotally because we are the market. We're hoping to better understand the market and our place in it doing this sort of phase-in, rather than writing all of our code first and hoping for the best.
The social proof is a great idea, and something I completely forgot. We've gotten a number of sign ups so far, some with some very good comments. So I'm not planning on investigating that immediately.
I've never dealt with an ultra-long trip like the one he's talking about in the article. However, for "normal-"length vacations you might take as a software engineer (i.e., 2 weeks or so), I've found that my body actually benefits from the time off.
I've done two two-week trips this year (Peru and Spain). In both cases, I was in excellent shape before the trip (155-160lbs at 5'11" with low body fat and good muscle definition). I work out three to four times per week, plus box twice per week.
I lost about 10lbs during each trip. When I got home from Peru (the first trip), I was mortified. I tried to bulk up like crazy by eating a ton of good fat and protein, and I lifted almost exclusively heavy weights. I was bigger and stronger than before the trip in three weeks.
After the second trip I was less scared, because of the previous experience. I was just as strong as before the trip in about three weeks again, but I didn't gorge myself as much, so I stayed a bit leaner.
I guess what I took away from the experiences was that you're bound to loose body fat while traveling, simply because you do so much walking. If you're in good shape beforehand, though, your muscles will "remember" and come back to you remarkably fast. You may even be able to improve your overall fitness level and put on leaner muscle afterwards.
I suppose it depends on the definition of "success". Learning about the state of the art and writing some enlightening code, no matter its ultimate usefulness, would be plenty successful for me.
I'm mostly surprised at the lack of papers I'm able to find that have been published after the mid '90s.
I will give major kudos to you though, sir. I've spent the last hour or so reading through the wiki. Please, keep up the great work.
I assumed you did, I was honestly just trying to formulate my point. That, and I was talking about C++ macros, which is what Joel was referring to as well.
Given the overall theme of this rant, I would assume that it's about keeping code close together and easy to understand.
Obviously, macros have almost nothing in common with functions. Macros are simply shorthand for code that will be literally placed at the spot they are called.
So rather than calling functions, with all argument expressions evaluated, and a call stack, and blah blah blah, you are just copy-pasting code without it actually ending up on the screen for a developer to see.
My Google interview a few years ago was very similar. No matter how confident you are, it's amazing how nerves can cause you to stand there at the whiteboard babbling like a newborn.
Google actually had me do two on-site interviews (one in my hometown and one in Mountain View). The first one went very well. I had a great rapport with the (single) interviewer, and had fun solving the (single) problem he gave me.
The Mountain View interview went more or less like the one described in the article. Marathon style. Had good rapport with some of the interviewers, less so with others. Once you start stumbling your confidence starts to fall apart, and it can really hurt you for the rest of the day (the interview lasted all day).
I also didn't exactly end up with the job. They offered me a testing position with "fast-track" promotion to engineering. I passed on that.
Good advice in the article though: practice problems on a whiteboard at home or with friends. Especially fundamental problems that you learned in your first algorithms class and the like.
We support both (camera and external), but surprisingly a lot of our customers find the camera good enough. Code 128 is our second-most scanned symbology behind QR.