First year programming in the late 90s … segmentation fault? I put printfs everywhere. Heh. You’d still get faults before the prints happened, such a pain to debug while learning. Though we weren’t really taught your point of the comment at the time.
Least that was my experience on an AIX system not sure if that was general or not, the crash before a print I mean.
Software devs and designers usually fall under IT is my understanding but I can see why many people/places would make the distinction. Especially for companies that only write software, their IT would more be the infrastructure, but if they’re only writing software for in house use that’s more on the IT side. I could be completely wrong about this too, just how I saw them grouped.
I’ve only dabbled in Linux, I can figure out things for the most part but never used it beyond some fiddling, but I didn’t realize that desktop environments had that many specific applications. I always thought beyond some default apps most apps wouldn’t depend on the desktop environment but after some reading seems like they use similar dependencies.
So if this gets seen, can most/many/any general kde apps work under a different environment if you install the dependencies or do you absolutely need the environment for them to work? Does that also follow for other desktop environments? Been reading up on DEs to get a dual boot or virtual install going in the future and this was something I hadn’t realized may make one DE stand out.
The problem with stuff like flow charts is that when you do a new feature that changes the chart then there’s another chunk of time to update that document. If you’re really interested in that all you can really do is make your own as you go through software and you’ll see usual patterns how different code areas interact. it’s not as useful as figuring it out on your own or studying design paradigms.
That’s cause they always have money in the lobbying budget to fix things.
Not if the place doesn’t do daylight savings time, and not all places in a timezone will do that (least in North America) so you need extra code if they do or do not. It becomes a pain after awhile when you do it in multiple projects. Technically one extra setting but it’s still a pain to make sure it’s handle properly in all cases, especially when the previous programmer decided to handle it for each case individually, but that’s a different issue.
Also when you deal with the times, say in .Net you gotta make sure it’s the proper kind of date otherwise it decides it’s a local system date and will change it to system local when run. Sure it’s all handled but there are many easy mistakes to make when working with time.
I probably didn’t even get to the real reason, I sort of picked this up on my own.