For all those non-NEET anons who work in some tech-related field:
>What does your average work day (when you actually need to do something) look like?
>What sorts of things do you need to do?
>Does it require a lot of creative thinking, or is it a paint-by-numbers sort of thing?
It doesn't matter if you're the lowest-of-the-low codemonkey, or a project lead for some safety-critical system of a large buisness.
I ask because I'm a second year Comp. Sci. student with almost no direction, no personal projects to my name, and a steadily growing lack of confidence.
>>57919239
i spend all day funposting
>>57919329
This is a fun post!!
>>57919239
I work as an IT technician. Most of my work involves basically dealing with Windows 7's shit (it breaks frequently, yet predictably), the rest of the time I'm in the warehouse repairing broken hardware. Fixing screens is the most difficult because my work uses all-in-one Lenovos, and the only way to the screen is through the chassis and motherboard.
>>57919239
>I'm a second year Comp. Sci. student with almost no direction, no personal projects to my name, and a steadily growing lack of confidence.
just watch more anime
>>57919239
>What does your average work day (when you actually need to do something) look like?
It's very varied. Usually starts by me checking my issue tracker and figuring out what to continue working on.
In terms of work, it's a mix of responding to notifications/alerts, upgrading hardware, updating configuration, and making incremental improvements to existing subsystems. I don't really have a set work pattern since it mostly depends on what pops up that needs to be done.
>Does it require a lot of creative thinking, or is it a paint-by-numbers sort of thing?
I'd say it's a mixture. Some of it is just reading documentation and other menial tasks, some of it is creative thinking, some of it is just straight up planning and organization (e.g. planning out the specs and deployment strategy for a new cluster)