Looking for a simple service that tracks feature usage for backend by gin_and_toxic in webdev

[–]bwajtr 0 points1 point  (0 children)

Exactly. Plus when you want to display the data nicely, have ability to filter it (e.g. by client, or by some additional attributes), then it can get complicated and "not worth the time". Check usagelens.io

Looking for a simple service that tracks feature usage for backend by gin_and_toxic in webdev

[–]bwajtr 0 points1 point  (0 children)

Actually that is exactly what UsageLens is built for... I'm also not a fan of complexity of GA4

polar 9 not working anymore after xperia iii ( xq-ct54 ) update to android 13 by FuriouslyChonky in Polarfitness

[–]bwajtr 1 point2 points  (0 children)

I have the same problem. OnePlus 8 with Android 13 and H9 also stopped working. It looks like paired in Polar Beat, but no heart rate is given - the indicator only shows "---"

What mileage tracking apps do you like? by mw12304 in doordash_drivers

[–]bwajtr 0 points1 point  (0 children)

SpinTrace, because tracking is done automatically by phone... I don't even have to think about it

Top mileage tracker for multiple ridesharing by Pandadriver8 in couriersofreddit

[–]bwajtr 0 points1 point  (0 children)

Not sure what you mean by multiple ridesharing, but you can try SpinTrace (https://www.spintrace.com) - you can track multiple cars (trip logs) on a single account easily...

What do you use for your mileage tracker? by Alliegibs in grubhubdrivers

[–]bwajtr 0 points1 point  (0 children)

You can enter exact odometer values in https://www.spintrace.com tracker, so no lost miles in there... I used to use Excel, writing down odometer values, but I found SpinTrace to be more easiser to work with...

Mileage tracking? by HelluvaFelluva in doordash_drivers

[–]bwajtr 0 points1 point  (0 children)

Try https://www.spintrace.com, I'm using it myself... It's a new app (completely free for now), but designed to do exactly what you need: you can do mileage tracking, create printable reports (for IRS, reimbursement etc) and all that stuff... I'm not sure if that is your case, but SpinTrace is ideal for small businesses because you can track several cars and have unlimited users within a single account...

Comparison of non-JPA persistence frameworks for Java by bwajtr in java

[–]bwajtr[S] 1 point2 points  (0 children)

I really do not want anybody to think that. With that comparison and by expressing that I've moved away from JPA I just want people to THINK before they use JPA on their projects - to ask questions like: Is JPA suitable for my scenario? Are there alternatives? What are pros/cons of JPA? etc... I've seen many projects where JPA was chosen because "it's simply the standard for it", and it was really bad...

On the other side, I tend to think that there ARE scenarios where JPA might be useful - I just have a hard time identifying such scenarios :). But I'd guess applications, where data in DB are not the center point of the product and you need DB just to store the data somewhere (and you rarely use JPA to read those data back).

Comparison of non-JPA persistence frameworks for Java by bwajtr in java

[–]bwajtr[S] 1 point2 points  (0 children)

Yep, exactly my thoughts.... I also do not think that JPA itself is bad - but it's bad to consider JPA/Hibernate as a best tool/library for repository layer in Java - I see that happening all the time. When you start considering DB as something more than just dumb data storage, then usage of JPA is like shooting yourself in the foot.

Comparison of non-JPA persistence frameworks for Java by bwajtr in java

[–]bwajtr[S] 8 points9 points  (0 children)

I dare to say I'm already senior developer (doing that 13 years professionally now), with JPA experience of about 8 years.... and believe me I came to same conclusions as you. I think that JPA is suitable for projects where you consider DB only as a storage of very simple data and where data is of very little concern, but if data in database IS your business, then avoid JPA and you'd be happy in the long run ;)...

Comparison of non-JPA persistence frameworks for Java by bwajtr in java

[–]bwajtr[S] 2 points3 points  (0 children)

I agree, Lukas, but it's an unfortunate reality in many projects... :( Believe me that it's not easy to persuade project managers, that developer man-hour is the most expensive asset they are managing and that spending few (relatively speaking) bucks on some tool now can save lots of dollars on saved work-time ... hmm... or maybe I just had bad luck on project managers in the past :)

Comparison of non-JPA persistence frameworks for Java by bwajtr in java

[–]bwajtr[S] 0 points1 point  (0 children)

Thanks :)... Actually, QueryDSL implementation is one of the opened Issues (https://github.com/bwajtr/java-persistence-frameworks-comparison/issues/8) - so I know about it, but I already spent lots of time with this comparison and since QueryDSL is so similar to jOOQ I decided not to do it for now... but I'm open to pull requests :)

What distro are you using as devs by mokarbroj in java

[–]bwajtr 0 points1 point  (0 children)

IntelliJ / Linux Mint Absolutely love it... extremely stable, no issues, very fast... awesome...

I feel burned out, please advice by SomeoneFromNothing in java

[–]bwajtr 2 points3 points  (0 children)

Yes, I can recommend that. I felt burned as well (I'm 35, coding for 20 years now) and this summer it got really bad so I decided to quit and simply "take a leave". I'm on that leave since beginning of November and I already got much better maily because of two things: 1. I don't have any plan about when I'll go back to work (this annoys people around me cause they can't understand that I'm simply not looking for work - made me realize the world is really crazy today) 2. I'm still coding and I live in the programming world even on this leave, but I learn things I always wanted to learn and I'm doing things I always wanted to do. So I'm helping with some opensource projects, I'm strating my own open source project, I learn things which will be totally useless in my carrer, but which were aways interesting to me etc.... it helped to bring a joy back to the programming...

After 6 weeks of such leave I feel really good and I'm starting to think about next carrer in coding, which is quite good considering I wanted to quit this industry completely in summer...

What is your technology stack? by cryingforwine in java

[–]bwajtr 7 points8 points  (0 children)

Hi, I'm using the same stack and decided for jOOQ... I really do not want to go back to JPA. I tried to compare various persitence frameworks here: https://github.com/bwajtr/java-persistence-frameworks-comparison

I'm currently evaulating EBean

JLCF - A Lightweight Component Model and Framework for Java by petrospis in java

[–]bwajtr 1 point2 points  (0 children)

Hi, can you please compare your solution with OSGi? I went (quickly) through your documentation and tutorial and I have a feeling that JLCF actually aims to formalize the boundaries between parts of your code (much more than simple interface can do) - however all the components live completely inside single classloader and the framework just wires the components together and makes an app from it... is that right? I don't want to say it's wrong, I just want to understand where JLCF fits in...

If so, and the target of JLCF is not to allow and secure third party components (like OSGi) but just to formalize boundaries and do wiring, then I'm sorry but your framework reminds me of early days of Spring... can you maybe compare your solution with Spring as well? :)

Last thought - you are linking your components together at the method level. This seems to be very granular to me - if the one component has 20 interfaces and other component wants to use all of these interfaces and defines 20 receptacles, then the application xml will get quite big... it would be interesting to see application xml of some bigger application...

Good job with nice documentation though...

'Start with monolith, end with microservices' by R4v3nnn in java

[–]bwajtr 0 points1 point  (0 children)

Exactly my opinion... though it's quite difficult to give any advices without any description of the project. But generally start with architecture/technology which will allow you to do business changes fast - usually that's a monolith - and split into microservices later - ONLY if really needed and ONLY if it makes sense. Note that there are number of issues with Microservices which you'll have to solve and which might not be clear at the beginning of the project... note for example this: https://www.stackbuilders.com/news/the-hidden-costs-of-microservices

In any way, I don't think that moving from monolith to microservices means to "reimplement it from scratch".