Readit NewsAs somebody who have been in and out mental hospitals, this is very familiar.
At one point in my early twenties, I was literally thinking about killing myself every single waking second.
Finally I decided to throw in the towel, and got around to planning my end.
Sat there, ran through various scenarios in my head. All the way up to putting the gun in my mouth and pulling the trigger.
My imagination always terminated in blackness. Nothingness.
Then I realized I didn’t want to die, but didn’t want to live this way. And promised myself that I would do everything in my power to heal.
It took me about 15 years to get where I am now. Stable and mostly at peace with myself, but it was an arduous and painful journey - with many terrifying moments where I couldn’t see a way out.
I’m incredibly grateful that I managed to figure it out and I wouldn’t wish that agony on anybody.
I'm really glad to hear you made it through such a challenging time in your life. Your strength and determination are incredibly inspiring. I'm curious to know more about your healing process. Did you work on identifying and addressing the root causes of your pain, perhaps through therapy or counseling? Sometimes, personal issues can stem from our familial relationships. Did you find that to be the case in your journey? I'm interested to learn more about how you managed to overcome your struggles and achieve the peace you have today.
JacKTrocinskI commented on CTEs as lookup tables misfra.me/2023/ctes-as-lo... · Posted by u/preetamjinka
CTEs are just a nicer, more readable way of writing a subquery. Also, CTEs can be recursive. In Postgres, CTEs can be useful when used with the RETURNING clause. If you're using the same CTE in multiple different queries, then consider creating a view instead. I wouldn’t use a CTE for lookup values, create a lookup table instead.
JacKTrocinskI commented on Ask HN: Strategies for working with engineers that are too smart? · Posted by u/throwitawaaay
I am one of those people - an academic type that likes to over-engineer, and at least partially work on embedded systems. What I've learned after two decades of experience is that it's best to apply most of that sophistication to tooling and supporting software - test suites, fuzzing, benchmarking, quality evalution, code and data generation, prototyping environments, automated reports, etc etc. All while keeping the actual shipped software as simple as possible.
K.I.S.S. - Keep It Simple Stupid
JacKTrocinskI commented on Ask HN: Strategies for working with engineers that are too smart? · Posted by u/throwitawaaay
It sounds like there might be a larger project management issue within your team, though it’s hard to tell from a single example. Features should solve business problems and should come from your clients and/or users and not from engineers. Are your users complaining about your static solution? If not, then why change it? Engineers should work on things that will add value to the business. Arbitrary performance improvements and code rewrites that don’t solve any business issues should be rejected by your project manager.
My suggestion would be to bring this to the attention of your PM. If that fails, then focus on picking up tasks of high value and visibility. Let the “smart” engineers do code rewrites or performance improvements. You’ll have a lot more to show on your resume, feel a greater sense of accomplishment in your work, and will have a greater chance of getting noticed as a star on your team.
JacKTrocinskI commented on Project Management: Time Estimations jtrocinski.com/posts/Proj... · Posted by u/JacKTrocinskI
To quote:
Time estimates matter not only to the business but they’re a reflection of your level of expertise as a software developer. An experienced software developer can keep tasks on schedule and communicate delays in advance.
I have 51 years as a software developer. Time estimates are worthless.
That's not really a great counter argument, can you explain why you think time estimates are worthless? Do you prefer story points instead? How do you schedule a project with your clients?
Obviously whatever trading bot you're running separate from the actual trading engine itself is somewhat proprietary, but it would be great for the community to get more of this type of software in the hands of other hackers.
Quantopian / Robinhood tried and failed, and the numerous clones since then have been somewhat sub par.