beybol

A problem often arises when a paid plan competes with a free one within the same product. Clockify limited basic functions (data export, billable rates) in April to convert users from free to a paid plan. Google has now moved free competitive models behind paid plan as well. It happens all the time - nothing unexpected. Clockify, Gemini are just examples.

In my projects WHY always goes to ADR because every decision should be well documented, not only as a comment but with arguments. Moreover a decision may change and the change should be documented too. A published commit message is unchangeable. In one of my projects I have 170 commits and 85 ADRs where one is accepted temporary and one superseded by another.

By structured data, I mean a JSON-LD section in the source code that describes my project. I've included: WebApplication, offers.price: 0 , sameAs, FAQPage. Bing read it but still I don't have a proof how effectively it influences LLM-s.

So far directories didn't bring me registrations but my scale is too small to determine whether being listed in directories helps with user acquisition or SEO/GEO while I observe registration with LLMs refer. How do I measure that? I correlate server logs with application log (mainly registrations). I observe for example GPT scans as a result of conversation with user and seconds/minutes after that entry and registration in the system. It supprts my observation about traffic source quite accurately. Can you provide more data here and let us know whether LLMs regularly scan directories and how it looks on your end?

For me, social media and directories (like SaaSHub, Capterra etc.) are not working. Of course, you should try them and track the results — measure the traffic generated by each source. Be aware that logs may rotate, so make sure to check them frequently, save and analyse.

In my case, the only source of traffic and registrations is recommendations from AI assistants, so I focus on GEO - structured data in the source, proper indexing in Bing and Google.

I am running a small-scale project without a marketing budget, so this is more of an observation than a conclusion based on proven, repeatable statistics.

t depends on the system. Keeping a time zone alongside a UTC timestamp may be useful in some cases.

For example, if your system is supposed to remind a user to do something, such as take a pill, and the user changes time zones while travelling, you may want the reminder to occur at 9:00 local time wherever they currently are. In that case, storing the original time zone together with the event may not be necessary, because the relevant time zone is the user's current one.

Everything depends on the context. For me, however, there is no doubt about one thing: I store timestamps in UTC. Whether I also store a time zone, and where I store it, depends on the system and its business requirements.

I don't know the exact use case, but it sounds weird. If UTC is the single source of truth, then when you display the data and want to change some business assumptions, you only need to change the application logic. The underlying data remains unchanged.

One scenario I can imagine is when you want to store the results of business calculations in the database. In that case, once the algorithm changes, you may also need to update the stored data. This may be necessary for performance reasons.

In all other cases, calculating the result on the fly solves the problem and does not require a database update when the business rules change.

I read raw data (UTC timestamps) from the db and timezone for user profile and calculate it on the fly.

I don't rely on time calculations at the database level. I handle them in the application based on UTC time stored in the database and the user's time zone. This shifts the problem to the application code, where I can control it precisely and make conscious decisions about how to handle specific business requirements, such as when a day ends or how to deal with events across different time zones. It also makes it possible to properly test all cases with unit tests.

For me the best way to get new customers is: referrals and transparency. Ask your current customers for referrals. Moreover I can deliver faster and cheaper than many bigger companies. Especially while leveraging my work by AI in a transparent and honest way so I am very competitive.

I've stopped reading all lines but I read very carefully specification and read/create proper ADR-s - this is crucial for me. In addition I plan strict automated tests (unit and functional) + I run mutation tests to check tests quality and find gaps. Moreover after every stage of development (not task, but several ones) I perform security review.

It will require more attention to settings.local.json :)

you may be exceptional :) I am not claiming that noone wants to read but the main stream is focused on shorts not text.

People don't like reading news these days. It is sad. Nevertheless Google is not supporting this product as they could.

Does anyone use this kind of editor on a daily basis development process?

I think most people wouldn't appreciate it these days :(

Looks like everything is working anyways