>0 hifikuno @ 2022/03/03 03:04
I am a data engineer. I've only been doing it about a year, but I love it. When I first started doing uni, I hated my databases course. It was boring, dull, and I couldn't think of anything worse than doing SQL full time. Now, over a decade later here I am working almost exclusively in SQL. There are challenges that I just didn't see when I was learning the basics. Do you have a similar story? Is your job better than you hoped? Worse?
>1 jdtron @ 2022/03/09 18:07
I work as a software engineer and I love my job. Working in an agile environment feels like a very nice way to get things done. But what I don't like is the massive amount of meetings every day. It's probbably fine, if someone works in just one team. But for me, being involved in sometimes 4 to 6 projects at a time, means the overhead mentioned above multipied by the number of projects I participate in. But I'd say this is the only thing that don't like. Aside from that, working in a software company is pretty much like I expected it to be.
>2 jacksonbenete @ 2022/03/19 01:10
Well, I was just hired to work with functional programming for a fintech. Amazingly, boss was asking me two write while loops with if conditions and asking me not to use functions like map, filter... and discouraging pattern matching. I guess it's like they say, "The determined FORTRAN Programmer can write FORTRAN programs in any language." So yeah, right now my job is quite different than what I thought I would be doing.
>3 dozens @ 2022/04/06 19:23
Well I'm not an astronaut or a fireman or a chef. So there's that. Real answer is the same for every job I've ever had across 3 careers now: Planned: doing the job Actual: managing people and helping them do the job
>4 schwartz @ 2022/05/16 22:08
I'm a front-end developer. I thought I'd be solving interesting problems and building cool UIs that push what the browser is capable of. Instead, it's just all buttons and inputs and API endpoints.
>5 anonymous @ 2022/05/22 18:54
Currently unemployed and looking for work again. I was working as a sysadmin, and have worked as webdev for a little bit. I took time off to join the infosec bandwagon. Like a lot of people, I find that I was interested in hacking for a long time. Had been involved in what feels like "the old way"; reading phrack articles, doing vulnhubs now and again. Polluting [parameters here and there, y'know, just being a skid and having fun. I think I've always liked computers and "been good at them", but didn't really have a friend circle that was into them, and that worked out fine. But in studying and looking into infosec, its a little disheartening to see how much its changed in the last few years. The DEFCON experiences I had nearly a decade ago are so different to the current "former military" groups of people coming into infosec. I feel like "hacking" has changed so much from the days of "cypherpunks" and people that enjoyed stuff because it was fun. Popping shells, crashing apps, etc was just ...fun. Now it seems like the former .mil folks bring with them a certain bullying behavior -- that they seem to be unaware of. To be fair to them, I finally have made a push into infosec likely for the same reasons. The money is good, supposedly. But I dunno, I just like hacking; learning stuff about systems. I guess I'm the type that really likes compsci stuff but kinda don't take it so horrendously serious? The "new" sterness around it all has mostly turned me off to the general or bigger parts of the industry. But I think FANNG and Fortune 500 folks have always been like that. lol. I dunno, I think some of this is just gettin' older.
>6 anonymous @ 2022/05/22 20:19
>>2 From what I imagine, someone had to check some corporate boxes and decided that the best way is by pretending. If that person is from a non-technical background, I don't understand why they would meddle in your work with such requests. If that person is technical, and FP indeed fits the purpose, I would try to explain to them in which cases you would indeed use FP constructs. I've worked in weird corporate environments. I've seen Python 2.7 still used in production, and FP code written as if it's (bad) Python (i.e: disabling type errors, coercing the return type of a function called "getConnection", to either a List of raw JSON string, or a plain unparsed String, etc). So there are many wonders out there. :D Best I can do is amuse myself.
>7 jacksonbenete @ 2022/05/23 17:39
>>5 I used to enjoy computers (and tech as a whole) and security in the 90's and early 00's. As a kid and later as a teenager, all the tricks like calling a number for free from a public telephone/payphone by forcing pulses through the wire, or by faking a coin, was fun. Then, exploiting Windows OS, hacking apps... was a lot of fun back then. Nowadays internet stuff and even computers bored me a lot. I don't like what things turned to be in the modern age. I mean, I'm only 30yo, it's not like I was hacking in the 70's... But I liked things like they were in the 90's. That's it. >>6 It's a fintech, which is the latest trendy bubble industry, and FP is the latests trendy paradigm (again), so... Yeah, they're both checking corporate boxes while it's also quite ok to take advantage of the nice scalability and fault tolerant system that Erlang has to offer. But people gonna write bad code in any language or paradigmn. The system is so messy to deal with, without documentation and without contracts and type annotations that I'm right now looking at F# to learn and to hopefully get a job in it. I mean, I love FP, but again, people gonna write bad code if you let them. Let pick a strongly typed language then, so people will be forced to define types and write things in an auto-documented way. I understand, the MVP have grow too fast, so the creator had no time to document and write better tests... But if you didn't back then, you should do it right now instead of keep writing even more features without documentation and good tests... I like programming, but I guess I'm easily frustrated. I quit the career once, let's see if I'll endure it this time or if I'll quit software engineering again.