spreiti
This is the official Java channel.
I described my workflow that has been a game changer for me, hoping it might be useful to another person because I have struggled to use LLMs for more than a Google replacement.
As an example, one task of the feature was to add metrics for observability when the new action was executed. Another when it failed.
My prompt: Create a new metric "foo.bar" in MyMetrics when MyService.action was successful and "foo.bar.failed" when it failed.
I review the plan and let it implement it.
As you can see it's a small task and after it is done I review the changes and commit them. Rinse and repeat.
I think the biggest issue is that people try to one shot big features or applications. But it is much more efficient to me to treat Copilot as a smart pair programming partner. There you also think about and implement one task after the other.
I see it as a competent software developer but one that doesn't know the code base.
I will break down the tasks to the same size as if I was implementing it. But instead of doing it myself, I roughly describe the task on a technical level (and add relevant classes to the context) and it will ask me clarifying questions. After 2-3 rounds the plan usually looks good and I let it implement the task.
This method works exceptionally well and usually I don't have to change anything.
For me this method allows me to focus on the architecture and overall structure and delegate the plumbing to Copilot.
It is usually faster than if I had to implement it and the code is of good quality.
The game changer for me was plan mode. Before it, with agent mode it was hit or miss because it forced me to one shot the prompt or get inaccurate results.
Also, buy a Nintendo console. It solves 99% of all problems. I haven't seen these dark patterns in any Nintendo title and personally I think it's the best gaming environment for kids.
[0] https://www.jetbrains.com/help/idea/using-breakpoints.html#s...
[1] https://www.jetbrains.com/help/idea/using-breakpoints.html#l...
Relevant JEPs:
- 441: Pattern Matching for switch
- 440: Record Patterns
- 409: Sealed Classes
- 395: Records
It is kind of similar to Scalas version of pattern matching with case classes.
But from my experience most people don't know these tools even exist so the only thing they do is restarting and guessing where the problem might be if it persists.
But every now and then I discover something new and this is when I get excited again. This is what keep the little coder flame burning that is still left within me.
So I try to find something new every month or two that get's me excited again. Doesn't take much time and is very rewarding.
(I work as a Software Developer at SBB and work on the system that does the refund process)
The Breitling Navitimer 01 would tick many of your boxes (Chronograph, (Logscale)Bezel, Date) and is an iconic watch. However you can't swim with it.
Another iconic chronograph is the Zenith El Primero with the tri color dial. It is also WR to 100m.
Then there is the Omega Speedmaster "Man on the Moon" Chronograph.
Tudor also has a few nice watches: Black Bay Chrono, Black Bay Heritage, Black Bay 58, Black Bay GMT, Pelagos.
If you want a fine Quartz watch have a look at Grand Seiko and Citizen Chronomaster. These are High Accuracy Quartz (HAQ) watches which means +/- 5-10 seconds a year depending on the model.
For more classic looking watches have a look at Jaeger LeCoultre. I especially like their Masters collection.
There are E-Straps from Montblanc that can notify you among other things.
There are also the "HOROLOGICAL SMARTWATCH" and "HYBRID MANUFACTURE" from Frederique Constant that could be interesting to you.
What stops you from creating a module inside a monolith with an interface that provides a self-contained service that does one thing?
On a serious note, I still think Java has one if not the best ecosystem of any language. Fast JVM, lots of high quality Open Source libraries/frameworks, tooling (IDEs, monitoring, debugging) and if you have a problem you probably are not the first one and usually find an answer.
The weekend before they found them my wife told me that a monk who was praying for them at the cave said that a ghost[1] was hiding them from the eyes of the divers until Monday[2]. They shouldn't be worried about the children and their coach as the ghost would take care of them. To my surprise they found them on that Monday.
[1] https://www.nytimes.com/aponline/2018/06/27/world/asia/ap-as... [2] I don't have a source as my wife was just scrolling through her Facebook feed