Programming thread

Ok awesome. I've already established multi-CPU consensus and my software is capable of queueing up tasks so I guess I'm halfway there. I just need to implement the single interface that's capable of easily distributing tasks.
I plan on writing an interface that can execute Python, Java, C, C++ and an hMail interface. I've noted that down so thank you for the tips.
I recommend giving a watch to Rich Hicky's Language of the System talk. If you're doing distributed computing, watch some Joe Armstrong talks, too.
 
I recommend giving a watch to Rich Hicky's Language of the System talk. If you're doing distributed computing, watch some Joe Armstrong talks, too.
Ok I will. I've got a couple of textbooks online for free of doing this in Java, which I've been using extensively. But cheers I'll watch some of their stuff.
 
Ok I will. I've got a couple of textbooks online for free of doing this in Java, which I've been using extensively. But cheers I'll watch some of their stuff.
Their stuff gave me food for thought for years.
Another couple of things to keep in mind - don't get tempted by performance at all. I'd prioritize correctness, flexibility and scalable design. By which I mean, design the system to support 10 billion instances first, then scale it down, not 10 then scale up. That way lies breakage.
 
C:
int
#line 507 "./tex4ht-c.tex"

#ifdef CDECL
CDECL
#endif

main
#ifdef ANSI
#define SEP ,
(
 int  argc SEP
 U_CHAR **argv
 )
#undef SEP
#else
#define SEP ;
  (argc, argv)
  int  argc SEP
  U_CHAR **argv
  ;
#undef SEP
#endif
{
#line 1385 "./tex4ht-c.tex"

  register INTEGER  i;
  int  ch;
KILL ME!!!!
Anyone still supporting those old non-ANSI function definitions needs a tarring and feathering. This occasionally causes actual problems in modern compilers, because they don't seem to be able to reason correctly about the (non-)type of those "non-arguments".
I just want to know why "SEP" needed its own definition/undefinition if the whole thing is already inside an ifdef anyway :lol:
 
Anyone still supporting those old non-ANSI function definitions needs a tarring and feathering. This occasionally causes actual problems in modern compilers, because they don't seem to be able to reason correctly about the (non-)type of those "non-arguments".
I just want to know why "SEP" needed its own definition/undefinition if the whole thing is already inside an ifdef anyway :lol:
C2X Is actually going to forbid that shit lol. Good riddance!
 
how do you guys deal with burnout? (:_(
It's a big question, and not everybody's answer will be the same, I suspect. At least in my experience, it's not really solved by continuing to do whatever you're burned out on under the same circumstances that have burned you out.. Take a break. If that's not an option, try going to your boss/manager and asking to be reassigned for a while - maybe doing what you have to do but in a different place or on a different project will be enough to liven things up.
 
how do you guys deal with burnout? (:_(
Presumably you're asking about burnout caused by long hours? I was in this situation - weightlifting and meditation helped of course but the main thing that worked was discussing with management about proper processes and actually talking to software developers before committing to timescales. Explaining the concept of technical debt can help but remember that financial types see debt as a tool as opposed to a serious liability. It's important to point out that this is debt that compounds but unpredictably and one day there will be a serious problem with no quick solution.

I'm now in management myself (but still code every so often) so I have a measure of control over the workload so I can push back on unreasonable requests from the rest of the business ("I want this done before I go on holiday" lol). If something highly important isn't properly specified, I'll work with them to figure it out before a developer sees it. Hiring specific people, i.e. SRE types to deal with outages etc also helps keep developers away from the sharp end of the business's demands.

It's my responsibility to manage my staff's stress levels but also it's their responsibility to talk to me about the situation.

On the other hand, some businesses however just have a culture of high stress, fast pace etc and some people love that kind of work environment.

So: Is it a process problem or is it a culture problem? If process and you like the company, work to fix the process. Otherwise, GTFO.
 
Thanks for the replies.

Part of it is that my job is not progressing in the way I want it to (it's a small business and I don't really approve of the direction the staff are taking it, and that's about all I can say).

But the other thing is that just in programming in general I'm just getting burned out on the daily grind, I guess. I don't like 'writing code' as much as I used to and I just really want to get things done. As much as I try to improve my workflow, I keep hitting hitches and I eventually determine it's just easier to write stuff on my own. I'm just sick of going through that cycle again and again and again.

Part of it I blame on google going to shit. It used to be so easy to find external solutions and libraries that you could drag in to significantly lighten your workload, but these days you have to scan through curated community lists desperately looking for anything remotely related to what you need. Even those lists can be hard to find. Often I have to spend big chunks of weekends just randomly searching github because I can't depend on search engines anymore.
 
But the other thing is that just in programming in general I'm just getting burned out on the daily grind, I guess.
From what you've written I'm guessing your company does contract software development for other companies or you are in a business with an internal software development team.

If I'm correct then you should perhaps consider a company that develops products sold to customers as opposed to services provided to clients, internal or external.

I find product development to involve a lot less burn out because the company is in control of the backlog but most importantly for me: once you've solved a problem you don't have to solve it again.

Alternatively consider another type of programming - i.e. if you are doing web stuff then look at SRE type work* or perhaps consider embedded, which has a considerable learning curve but going back to the basics can be really fun (at least for me).

* I define SRE as a team which is about 50/50 reactive/proactive development and not just the company's bug bitch as tends to happen
 
helicopter.png


The 2021 Stack Overflow survey has launched. Ancient memes aside I'd encourage everyone to fill it out seriously since I think the information about what languages and libraries people are using and how much money they are making is useful (if not depressing).
 
View attachment 2203627

The 2021 Stack Overflow survey has launched. Ancient memes aside I'd encourage everyone to fill it out seriously since I think the information about what languages and libraries people are using and how much money they are making is useful (if not depressing).

Seems like they asked less questions this year, but maybe I’m imagining it.

Is this the first year they’ve specifically asked if one is a troon?
 
  • Informative
Reactions: GreeneCoDeputy
how do you guys deal with burnout? (:_(
Depends on what kind of burnout. Burnout from long hours/death march? Burnout from writing the same type of program a 100x (oh god those contract days were hell, "great, another MVC app")? Burnout of constantly trying to learn the latest, trendiest javascript lib?

What i've found in my career is shifting focus to newer and exciting technologies: I've gone from systems programming, to mobile/ios, to cloud, to big data, to machine learning.
 
  • Agree
Reactions: glow
I just want to know why "SEP" needed its own definition/undefinition if the whole thing is already inside an ifdef anyway :lol:
Your guess is as good as mine. This is actually being thrown out because it's illegible and archaic. The project is to replace it with a new C++ implementation. It took me 30 minutes to find int main because I couldn't isearch-forward for it. Who ever wrote this originally must have had nuclear autism.
 
  • Feels
Reactions: moocow
Back