5 ms·

You must be godly. I have a couple of problems I have been thinking about for years that I could use some help with! But my problems in are the real time render

You must be godly. I have a couple of problems I have been thinking about for years that I could use some help with! But my problems in are the real time rendering realm. For me personally I have found that when I find initial solutions to problems, they are usually just a shadow of the actual problem. The true complexity is not revealed until I start stress testing it, or making it interact with other systems, trying to expand it to handle more functionality. Maybe this can be attributed to the fact that my first step is to just make things work. And it not until I make them work do I really see the patterns. Then I usually manage to remove half the code as the patterns and abstractions resolve themselves. So for me, coding is essential to truly solving the problems.

JeanMarcS 9y ago
I might have mistranslated what I usually work on. I essentially do web apps for professionals. Intranet is a better word ? Usually CRUD apps with no need to top of the art designs, just working and adapted to what the client wants. The most interesting part is sort out the best solution to translate a need they often have difficulties to explain, as it generally is concept they use on a daily base and is adapted to the way they work for years (in companies and projects as diverse as, for example, CRM for multiple AC companies regrouped in a joint society, gas truck following, with deliveries validated on tablet, backoffice for an editor for managing authors, stock, and stuff like that, etc...). Once I figure it out, menus, shortcuts, the different screens, etc, and validate with the client, 80% of the job is done. And then the coding part starts. I don’t say it’s useless and sometimes you’re right you bump on some problem you didn’t thought of in the beginning. But most of the time, it’s boring, for me. As I said, I work alone and most often for small companies, so there is rarely a lot of people using the systems at the same time. It might simplify it a lot for me.

JeanMarcS 9y ago

I might have mistranslated what I usually work on. I essentially do web apps for professionals. Intranet is a better word ? Usually CRUD apps with no need to top of the art designs, just working and adapted to what the client wants. The most interesting part is sort out the best solution to translate a need they often have difficulties to explain, as it generally is concept they use on a daily base and is adapted to the way they work for years (in companies and projects as diverse as, for example, CRM for multiple AC companies regrouped in a joint society, gas truck following, with deliveries validated on tablet, backoffice for an editor for managing authors, stock, and stuff like that, etc...). Once I figure it out, menus, shortcuts, the different screens, etc, and validate with the client, 80% of the job is done. And then the coding part starts. I don’t say it’s useless and sometimes you’re right you bump on some problem you didn’t thought of in the beginning. But most of the time, it’s boring, for me. As I said, I work alone and most often for small companies, so there is rarely a lot of people using the systems at the same time. It might simplify it a lot for me.