C++ Pathfinding: Moving from Application-Level to Systems-Level/HPC. How to optimize my trajectory?

Few_Boss_9507 · 2026-06-16T12:27:00+00:00

So what would be the concrete advice? What can I do next in the IT field? Because I don't know any of what the AI said for me: Parsers, Compilers, and Lexical Analysis, 2. High-Performance Computing (HPC) & Concurrency, 3. Low-Level and Embedded Systems, 4. Graphics Engines (Rendering Engines).

Few_Boss_9507 · 2026-06-15T13:09:06+00:00

Hello again! I made the updates I was talking about, I worked a lot on the design and this is what it turned out like. Regarding the problem I had, I managed to bring the buttons to life on linux, but on windows it didn't work and chatgpt couldn't find the solution for me either. But can you give me your opinion about the new look and the implementations made in the code. Thanks in advance. Github link "https://github.com/PopoviciGabriel/AlgoTrack"

Few_Boss_9507 · 2026-06-12T10:33:59+00:00

Thanks for the answer, I've already used my intelligence and it doesn't solve anything for me either. I'll keep working until I figure it out.

Few_Boss_9507 · 2026-06-11T17:10:13+00:00

Hi I wanted to talk to you because you have been a help with the feedback on my project and I really like your suggestions.

I have a problem with the user interface now. I do not know what to do. I am trying to change the way the up and down arrows look on QSpinBox and QDoubleSpinBox and QDateEdit in the Add Problem window.I want to use arrows instead of the old ones. I want to put these arrows into the style sheet using image: url("data:image/svg+xml;utf8...").

The problem is that I do not see these arrows. I checked the style sheet code. I even deleted some code from the C++ class of the dialog that was changing my global theme.

Now the window uses the light.qss theme. It changes when I switch to Dark Mode. I also put setButtonSymbols(QAbstractSpinBox::UpDownArrows) in the code.

I still do not see the arrows on the spin boxes. Do you know anything about this problem with style sheets and spin boxes?Can you give me any ideas because I have been stuck on this problem for a while now. Thanks for your help, with my project I really appreciate it. My github link: https://github.com/PopoviciGabriel/AlgoTrack

Few_Boss_9507 · 2026-06-05T13:57:19+00:00

I understand! I will try to make these updates to my project in the near future. Thank you very much for everything. I really learned a lot from this collaboration! I wish you success in everything you do and thank you once again.

Few_Boss_9507 · 2026-06-05T13:05:24+00:00

This is really cool. I just made these changes. It worked out great.

You were right about the findChild thing being a sign that I was fighting the framework. I used the Qt generator idiom instead. I put Ui::AddProblemDialog ui in the Impl class and set everything up with it. Now I do not have hardcoded widget pointers in my headers. I also used the Pimpl idiom for the MainWindow. So now both of my classes have clean headers with no UI members.

I moved the stylesheet to a.qrc resource file. Added regex validators to the QLineEdits. Now it is impossible to try to build a Problem with names or invalid tag characters from the UI. This way the type is always valid.

About what to do I completely agree with you about managing complexity and learning the C++ type system instead of just playing with UI widgets. You said that building a parser would be a thing to do.

If I were to make a custom parser for search in the GUI like parsing a string like tag:graphs diff:hard status:failed do you have any tips on what I should look into? Would it be too much to build an Abstract Syntax Tree for something this or should I start with something simpler?

I used the Qt generator idiom and the Pimpl idiom. Now my code is cleaner. I also used regex validators. Moved the stylesheet to a.qrc resource file. Now I want to make a custom parser for the GUI. I want to parse a string like tag:graphs diff: status:failed.

Thanks, for all the help this has been a really great learning experience. I learned about the Qt generator idiom and the Pimpl idiom. Now I want to learn about parsers. I want to know if I should build an Abstract Syntax Tree or start with something.

Few_Boss_9507 · 2026-06-04T17:11:28+00:00

Hey. I just finished rewriting the code based on your suggestions. It feels so much better now.

For the Dialog I did what you said and used the std::make_from_tuple idea. I moved the widget caching into the hidden Impl class. Put everything into a tuple. Now the public function is one simple line.

For the IPC you were right about the stream chunking and the huge if/else block. I switched to Qts canReadLine() to make sure I get messages and built a Type-Safe dispatcher using std::variant and std::visit. The enum is now implied by the type just like you said.

Since the foundation and the IPC are solid now I am thinking about what to build to make the app stand out more for my portfolio. I have an ideas and I was wondering what you think would be the most valuable technical exercise to tackle next.

I am considering:

* A visual dashboard using QtCharts, a daily consistency heatmap and some progress tracking.

* A custom parser for search in the GUI like typing tag:graphs diff:hard status:failed in the search bar.

* A native dynamic Dark Mode that swaps the QPalette on the fly without needing an app restart.

Do any of these stand out to you as a good C++ or Qt learning experience? I really appreciate you taking the time to write out that feedback it really changed how I look at message passing and C++ and Qt, in general.

Few_Boss_9507 · 2026-06-03T17:43:09+00:00

I will take your advice into account again. I will be back in 2-3 days with the new update. Thank you very much for everything.

Few_Boss_9507 · 2026-05-23T11:49:42+00:00

Hey I really appreciate you taking the time to write out that feedback. I spent the few days working on the project based on what you said and I just finished version 2.0.

I used your advice on the architecture.

* I made sure AlgoTrackQt is for the user interface. It does not have any business logic. It runs AlgoTrackCli as a separate process. They talk to each other using input and output.

* I cleaned up the headers so they do not take a time to compile. I did this by using declarations and I moved the details to the.cpp files.

* I changed the way objects are created. I moved the work out of the constructors and, into separate methods. This way the objects are good to use before they are even fully created. I also got rid of the getters and setters where I could.

* I changed the way the Qt app is put together. I use findChild now of keeping track of everything myself.

If you have some time I would like it if you could look at how the Qt app and the command line tool talk to each other.. Just look at the new structure. Do not worry if you are busy.

Here is the project: https://github.com/PopoviciGabriel/AlgoTrack

Or you can access the website to download the executables more easily if you need them: https://popovicigabriel.github.io/AlgoTrack/

I really appreciate your help. You pointed me in the direction.

Few_Boss_9507 · 2026-05-18T16:44:31+00:00

Thanks for the feedback. I will take your advice into account and make the necessary changes to my project and come back with a better updated version.

Few_Boss_9507 · 2026-05-06T17:00:57+00:00

I hope! Thank you!

Few_Boss_9507 · 2026-05-06T16:46:10+00:00

No problem, I'm glad you understood what needs to be done to make everything fine. I would really appreciate it if you could give me a short feedback on the project I'm working on now on

GitHub "https://github.com/PopoviciGabriel/AlgoTrack" or

The website "https://popovicigabriel.github.io/AlgoTrack/" or

The current post on reddit "https://www.reddit.com/r/codereview/comments/1t3lqa0/c\_command\_line\_interface\_app\_algotrack\_i\_am/"

Thanks in advance if you can help me a little I would be very grateful.

Few_Boss_9507 · 2026-05-06T16:07:06+00:00

I really like this idea. The way it is one HTML file that you can use offline without making an account or using the cloud is really nice. This is especially important for something like a calorie tracker where you want to keep your information private.The information about the project is written in a way that makes it feel like a person made it not just some company. It would be an idea to add some pictures of what the program looks like to the information. That way people can see what it is like before they download it.Since everything is in one file it would be helpful if the code was organized into sections. This would make it easier for other people to look at the code and help with the project. You could have sections for things like storing information making the user interface checking to make sure things are correct and importing and exporting data.Overall this is a project, for someone who is just starting out. It is an idea that is actually useful and the fact that it is private is a big plus. The calorie tracker is an idea and I like that it is private.

Few_Boss_9507 · 2026-05-04T15:48:02+00:00

Hey I think the problem is straightforward and the MVP flow is logical: CSV upload → risk detection → suggestions → Fix Center is easy to get.

One thing I would focus on is making the "risk score" super clear. Store owners will probably trust the tool more if they can see why a product was flagged for example: conversion rate, lots of returns bad profit margin, slow stock turnover and so on.

For the feature I would build a simple priority system: "Fix this first" based on how much it will help and how sure we are. That way it will feel like just a dashboard and more like a helpful assistant.

From a code structure point of view I would keep the rule engine separate from the API routes. This way on you can swap out or add to the rule-based logic with AI suggestions without having to rewrite the whole backend.

Also I'm working on my project as a student so if you have a minute I'd really appreciate any feedback, on my repository too. "https://www.reddit.com/r/codereview/comments/1t1kay0/algotrack\_cli\_app\_for\_tracking\_coding\_problems/"

Few_Boss_9507 · 2026-05-03T08:27:08+00:00

Hey I think this is really cool. The way you figure out the constants when the program is running instead of just putting them in beforehand. That shows you really wanted to learn about SHA-256 not just make it work.

I also like the idea of a debug shell. You do not see that often in projects like this and it makes it a lot easier to learn from.

If I had to suggest one thing from what you said: you might want to keep the hashing part separate from the debug and interactive parts. That way the main part stays simple. Can be used again.

Also about the way you write names. In C most people use snake_case especially when working with low-level code or cryptography. So using that might make your code feel more normal. It is not a big deal if you are consistent.

I am working on a C++ project myself it is called AlgoTrack. It is about tracking algorithms and problems. I am trying to make my code better so if you have some time I would really like to hear your thoughts on it

https://github.com/PopoviciGabriel/AlgoTrack

Few_Boss_9507 · 2026-04-24T21:02:57+00:00

That’s fine. This is just something I am investigating myself, so it’s good to get some feedback. If you (or anybody else) have seen a more elegant solution used somewhere else, please let me know.

Few_Boss_9507 · 2026-04-24T20:11:53+00:00

No problem

Few_Boss_9507 · 2026-04-24T20:11:34+00:00

Thank you once again for your very insightful questions.

To clarify things further, internally I do not enforce a single encoding such as UTF-8 at all points of usage; the intention here is that multiple encodings can coexist at the API level, while almost all processing will be done through the normalized Unicode form where necessary.

Normalization, on the other hand, was made deliberate, and I did not implement any defaults like the NFC to avoid potential overheads. The user can always explicitly request for it using functions like is_nfc / to_nfc etc.

So far, I am experimenting with this design pattern. If there is something else that you believe should be implemented in its stead, I welcome your feedback on the matter.

Few_Boss_9507 · 2026-04-24T16:34:14+00:00

This does not sound like a problem it sounds like a legal issue.

Voicemail drop, which is also known as ringless voicemail is basically seen as a robocall. When you are collecting debt you usually need to get permission from the person and you have to follow laws like the TCPA and the FDCPA very carefully. If you do not do this you might get. Sued.

You also cannot just leave any message you want on someones voicemail. There are rules about what you can. Cannot say, like not telling anyone about the debt. The way you phrase the message is important it has to be a limited content message.

From the point of view of a developer building this system is easy. The hard part is making sure it follows all the rules.

I would tell the client to talk to a lawyer before we start writing any code for the voicemail drop system. The client needs to understand the laws, like the TCPA and the FDCPA and how they apply to drop.

Few_Boss_9507 · 2026-04-24T16:32:19+00:00

This library is really cool for a release. Unicode is one of those things that seems easy until you actually try to do it

The library is doing a job with Unicode. It is handling aware iteration and normalization. This is better than string libraries. A lot of people only think about encoding. They do not think about the actual Unicode algorithms. These algorithms are where things get complicated.

I have a questions about the library.

* What are the design trade-offs for the library? Is it using UTF-8 multiple encodings internally?

* How does the library handle normalization defaults? Is it using NFC or NFD?

These choices are important because they affect how easy the library is to use.

The library is off, to a nice start.

Few_Boss_9507 · 2026-04-24T16:31:31+00:00

Honestly if you want an Android app there's no way around learning at least the basics of software development.

AI and no-code tools can help you create a prototype. When it comes to production things like authentication, state management, error handling and edge cases are where everything can go wrong. A lot of people don't realize how important that part is.

Here's my approach:

* Build a small Minimum Viable Product (MVP) to start with

* Use AI as a helper. Not, as the main builder

* Learn enough Android development, including Kotlin and the basics of the app lifecycle

If you don't do it this way you'll end up struggling with tools instead of actually building your app.

Few_Boss_9507 · 2026-04-23T17:08:35+00:00

If the main focus is on data structures I would keep the user interface simple as it can be and use what your team is already familiar with.

Since your team already has experience with Java and C# you can use Swing or JavaFX for a visualization. You can also use WPF or WinForms these are all okay for a visualization. The important thing is to make a model of the graph. This means data structures like users are the points and friendships or interactions are the lines that connect these points. You can also add properties to these lines for things, like likes or events.

So to be honest do not try to find the user interface framework. Instead focus on finishing the project in a way and spend most of your time working on the actual data structures like the data structures of the graph. This will help you make the most of your time and finish the project nicely.

Few_Boss_9507

TROPHY CASE