Just to echo the sentiment, I've had struggles trying to figure out how to use LLMs in my daily work.
I've landed on using it as part of my code review process before asking someone to review my PR. I get a lot of the nice things that LLMs can give me (a second set of eyes, a somewhat consistent reviewer) but without the downsides (no waiting on the agent to finish writing code that may not work, costs me personally nothing in time and effort as my Org pays for the LLM, when it hallucinates I can easily ignore it).
I wouldn't say it's doomed. For projects in large organizations that have a large amount of java already, it provides better ergonomics while allowing interop with the existing company ecosystem.
R&D was already a massive thing before trickle down economics came on the scene. In fact I would argue that since stock buy backs and trickle down economics became the operating model R&D went down. Mainly due to the fact that stock buy backs guaranteed stock growth where as R&D could be hit or miss.
This looks like it's a website without an app, so a few questions for you:
1. How does the site perform on mobile? If it doesn't that's a non starter for a large audience segment.
2. What's the pricing? There are several free options out there for managing your book collection, so unless there's a fremium tier (which there's no concrete language about pricing on the pricing page around subscription cost or subscription tiers) less people will want to try this out.
3. Why should someone use a web based library management tool over one that's hosted locally (either as a phone app, or as a site local to your network)?
4. What problems does this solve that others have missed? I would love for that to be front and center on the landing page.
Thank you for your questions. The actual app can be used/seen only after signing in. Regarding your questions:
1. This was initially planned as a web-based application, and it still is. However, when it comes to mobile responsiveness, it's not great — something I've pointed out and am currently working on. I'll finish this work during the weekend. Creating native apps will probably make sense in future, too.
2. Yeah, as it's only the beta version at the moment, the pricing doesn't mention anything specific. I believe there will be three different pricing tiers. There will definitely be a freemium version with some limitations, e.g. a limit of one library and 100–200 books in library, and access to basic statistics only. I need to think more about the pricing in more detail, as I've only concentrated on building the product so far. However, in general, I imagine it to be as I've already described above.
3. This is a very good question, to be honest, and one that I haven't thought much about either. I would probably use a locally hosted application if it offered all the features that librari.io offers. However, I can think of some reasons why a user might want to use a web-based solution. Firstly, I assume that syncing across devices would be difficult when the application is hosted on only one device, unless it offers export/import functionality. Backup and reliability are other reasons why a user would opt for a web-based solution. I believe that the ability to share your library with other people or family members using a link, which gives them access from anywhere at any time, is a good reason to opt for a web-based solution.
4. I can outline the three most significant issues I encountered, which eventually led to the development of this app. The first is the outdated UI that most of them suggest (but of course, I'm not saying that librari.io's UI is the best). The second is the lack of library statistics and analytics (e.g. distribution tables of books, authors, etc. or content-wise and reading activity related statistics). The third is the lack of customisation. For example, the ability to add custom book, author and publisher data fields with different types, such as text, date and number, and then attach actual information to those fields when editing those entities.
The problem with moving states is that there's a devil to pay when you loose your support network (family, friends, local coworkers). And the cost of moving isn't realistic for some.
I totally understand. Everyone has to weigh the cost for themself. Someone whose family is in danger just has to pay the price and move. Some might judge they can do more good by staying and fighting against the local bad actors.
> microservices are essential at any large company
There in lies the rub, the majority of engineers don't work at companies that need the kind of scale that Facebook has.
The majority of us work at smaller shops that can get by fine without all the overhead that microservices introduce. The problem that I see is that there are to many folks not weighing the pros and cons of the architectural decisions they are making, and are just joining the cargo cult.
reply