It seems like every other day I run into some post/tweet/article about people whining about having the imposter syndrome. It seems like no other profession (except maybe acting) is filled with people like this.

Well lemme answer that question for you lot.

YES YOU ARE A BLOODY IMPOSTER.

There. I said it. BUT.

Know that you're already a step up from those clowns that talk a lot but say nothing of substance.

You're better than the rockstar dev that "understands" the entire codebase because s/he is the freaking moron that created that convoluted nonsensical pile of shit in the first place.

You're better than that person who thinks knowing nothing is fine. It's just a job and a pay cheque.

The main question is, what the flying fuck are you going to do about being an imposter? Whine about it on twtr/fb/medium? HOW ABOUT YOU GO LEARN SOMETHING BEYOND FRAMEWORKS OR MAKING DUMB CRUD WEBSITES WITH COLOR CHANGING BUTTONS.

Computers are hard. Did you expect to spend 1 year studying random things and waltz into the field as a fucking expert? FUCK YOU. How about you let a "doctor" who taught himself medicine for 1 year do your open heart surgery?

Learn how a godamn computer actually works. Do you expect your doctors and surgeons to be ignorant of how the body works? If you aspire to be a professional WHY THE FUCK DO YOU STAY AT THE SURFACE.

Go learn about Compilers, complete projects with low level languages like C / Rust (protip: stay away from C++, Java doesn't count), read up on CPU architecture, to name a few topics.

Then, after learning how your computers work, you can start learning functional programming and appreciate the tradeoffs it makes. Or go learn AI/ML/DS. But preferably not before.

Basically, it's fine if you were never formally taught. Get yourself schooled, quit bitching, and be patient. It's ok to be stupid, but it's not ok to stay stupid forever.

/rant

I had to open the desktop app to write this because I could never write a rant this long on the app.

This will be a well-informed rebuttal to the "arrays start at 1 in Lua" complaint. If you have ever said or thought that, I guarantee you will learn a lot from this rant and probably enjoy it quite a bit as well.

Just a tiny bit of background information on me: I have a very intimate understanding of Lua and its c API. I have used this language for years and love it dearly.

[START RANT]

"arrays start at 1 in Lua" is factually incorrect because Lua does not have arrays. From their documentation, section 11.1 ("Arrays"), "We implement arrays in Lua simply by indexing tables with integers."

From chapter 2 of the Lua docs, we know there are only 8 types of data in Lua: nil, boolean, number, string, userdata, function, thread, and table

The only unfamiliar thing here might be userdata. "A userdatum offers a raw memory area with no predefined operations in Lua" (section 26.1). Essentially, it's for the API to interact with Lua scripts. The point is, this isn't a fancy term for array.

The misinformation comes from the table type. Let's first explore, at a low level, what an array is. An array, in programming, is a collection of data items all in a line in memory (The OS may not actually put them in a line, but they act as if they are). In most syntaxes, you access an array element similar to:

array[index]

Let's look at c, so we have some solid reference. "array" would be the name of the array, but what it really does is keep track of the starting location in memory of the array. Memory in computers acts like a number. In a very basic sense, the first sector of your RAM is memory location (referred to as an address) 0. "array" would be, for example, address 543745. This is where your data starts. Arrays can only be made up of one type, this is so that each element in that array is EXACTLY the same size. So, this is how indexing an array works. If you know where your array starts, and you know how large each element is, you can find the 6th element by starting at the start of they array and adding 6 times the size of the data in that array.

Tables are incredibly different. The elements of a table are NOT in a line in memory; they're all over the place depending on when you created them (and a lot of other things). Therefore, an array-style index is useless, because you cannot apply the above formula. In the case of a table, you need to perform a lookup: search through all of the elements in the table to find the right one. In Lua, you can do:

a = {1, 5, 9};
a["hello_world"] = "whatever";

a is a table with the length of 4 (the 4th element is "hello_world" with value "whatever"), but a[4] is nil because even though there are 4 items in the table, it looks for something "named" 4, not the 4th element of the table.

This is the difference between indexing and lookups. But you may say,

"Algo! If I do this:

a = {"first", "second", "third"};
print(a[1]);

...then "first" appears in my console!"

Yes, that's correct, in terms of computer science. Lua, because it is a nice language, makes keys in tables optional by automatically giving them an integer value key. This starts at 1. Why? Lets look at that formula for arrays again:

Given array "arr", size of data type "sz", and index "i", find the desired element ("el"):

el = arr + (sz * i)

This NEEDS to start at 0 and not 1 because otherwise, "sz" would always be added to the start address of the array and the first element would ALWAYS be skipped. But in tables, this is not the case, because tables do not have a defined data type size, and this formula is never used. This is why actual arrays are incredibly performant no matter the size, and the larger a table gets, the slower it is.

That felt good to get off my chest. Yes, Lua could start the auto-key at 0, but that might confuse people into thinking tables are arrays... well, I guess there's no avoiding that either way.

Sometimes.....

When I want to escape how dull/repetitive/boring the world of web development is. I crack open a nice lil terminal, dust off my gcc/g++ compilers and fuck around in C or C++ till my eyes start to bleed.

I have been fucking around with systems development. Mainly with Linux programming. I have also started to get deeper on game engine design and compiler design....because low level development is where its at.

A man can only fuck around rest apis, css and html and the endless sea of Javascript and other dynamic languages for so long before going crazy.

Eventually.....I would want to code something impressive enough to give me a spot somewhere as a C or C++ developer. I just can't work with web development any longer man. It really is not what I want to do, the fact that I do it(and that I am good at it) is circumstantial more than because I really enjoy it. I really don't

>be me
>I hate front-end dev, but I can do it. I hate switching between markup, styling, and logic.
>I like back-end and low level programming
>stay unemployed for a year and a half, because all offers are for React and Angular
>find backend job, yay
>they actually make me work on front-end shit
>mfw pic related

I had been a "hobby" programmer for well over a decade, with my primary career being in repair or a "technician". I had taught myself dozens of languages because it was fun, but never really accomplished much.

I was laid off from my job as a technician and I found myself listless and without purpose. I started doing development again on random things to pass the time and I ended up volunteering as a developer for a game I had played for years.

At the same time I had an uncle who encouraged me to consider software as a career. These two things gave me the confidence to apply for a local software job I saw on Indeed.

They called me pretty quickly, and I was brutally honest. "No, I don't have a degree. I'm self-taught. I have no professional experience really."

I got a proficiency exam anyway and I took it - apparently doing well enough on it that the CTO called me a week later. We had a long talk and I finally asked him why he called me.

He told me that while a degree means something, the passion to learn this job means more to him. It was a month before I was offered the position, and I graciously accepted it.

We had a call about my compensation before starting. It was rather low, but we both agreed that my skill level was quite an unknown.

A year later and my pay was bumped up a sizable amount. My skills are defined now and growing rapidly as new challenges are sent my way. I went from a naive hobbyist to a professional in a short period of time.

I realized that I was always a professional. I had a desire to learn and a desire to do things the right way. I may not have known what to call things. I didn't know some of the design patterns I had used over the years were standards that had names and meaning.

I basically work two jobs now. My full-time job and also on the game that helped propel my career forward and gave me the confidence to reach for it.

As for my hobby? I turned to electronics and the maker community. It's a nice marriage with my programming skill set, and I never knew how rewarding a blinking LED would be. :)

I learnt programming by making cheats for games and reverse engineering them. It was a fun experience as it wasn't always easy to start with C++ and assembly but it was definitely worth it. Though when you come from a low level language such as C++, looking at highly abstract languages such as Javascript makes everything feel wrong in Javascript, especially when it comes to types and how you can just switch types in the middle of the code :D. But it also gives you an understanding of how Javascript could be implemented, what the engine is doing in the background when you create an object etc..

How to profesionally say: you fucking illiterate and incompetent piece of shit, I am tired of spoonfeeding you because you dont use your fucking brain. I am fucking tired of explaining same concept over and over again for the past 2-3 months. Open fucking google for once and lookup latest practices, and learn what functional programming is and learn how to use operators instead of fucking inventing wheel again and again with your 100 lines boilerplate of code functions. Open your fucking mind for once and lookup stuff for yourself, instead of asking me to explain everything for the 100th time you lazy fuck. Oh and stop asking me "to be nice", this is gaslightling. I am being professional and I am the only person in this company who actually tolerates u on some level, others are just avoiding you you useless piece of shit. If I need to explain something for 5th time and I make you feel bad, it means you should feel bad. So maybe grow some balls and start putting in some effort, instead of playing the victim when you are the supposed 6 year senior and I am the 3 year junior, who has to do your fucking job half of the time. You are incapable of even using the standard architecture, what you use is fucking 6-7 years old. Fucking code monkey with broken english who doesnt understand what hes doing. You dont like my methods? I dare you to schedule an appointment between me and manager or your useless techlead, but I know you wont do that because I know you are afraid of everyone finding out how incompetent you are. You low fruit hanging task licking incompetent shit.

My family is pretty clueless about what I do, but they are genuinely curious. My mom especially. She always asks questions about stuff I'm learning and tries her best to understand.

I might do a little course in programming for anyone in my family who wants to learn. Helps a lot in how people solve problems, and would help reinforce my knowledge.

Question is, do I teach them a low level language like C, or something that's a bit easier to understand, like Python?

Hey hackers! It's me again 😀

If I wanna be an awesome pentester / bug hunter , what should be my main focus?
Network?
Data sciense?
Algorythm?
Low level programming?

I've already passed network + and basics of ccna and I already know pentesting using kali and I know c and python as well.
Just not sure where to go next and keep using kali packages makes me feel like a script kiddie (which is aweful 😬)

Dreaming to be able to write my own exploits and have my own 0day bugs👑

Thanks for any recommandation you would

I kinda hate my life right now.

I hate my job: I've been working as a flutter developer for a month and a half (even though I was hired to do backend) and I discovered I don't like frontend, it doesn't give me enough challenges. Every once in a while I have to do something complicated and have fun working, but most of the time it's just boring layout shit.

I can't do any side-projects, everything bores me. I want to get into really low level programming so bad but the steep learning curve makes me lazy.

I don't feel like I'm doing enough. I'm learning quite a bit about flutter, but I don't want to work with that, I hate it, so I feel like I'm just wasting my time. I'd like to work on something complicated and meaningful, like developing flight systems for rockets or whatever, but there's sooo much road ahead of me I just feel like I'm never gonna make it, plus I have to be very smart to do that and I'm starting to think I'm not as smart as I thought I was. I've been programming for almost 10 years now, but I can already see my college friends getting practically on my level in 2-3 years. I can't let that happen and this thought is making me stressed and burning me out. Programming is literally the only thing I'm good at (or at least I think I am), if I don't have that I don't have anything, because I suck at everything else (I'm not exaggerating, I wish I was though).

I can't see friends because of the corona. I've met with friends about 7 times in a year and I havent been with a girl god knows since when. Meanwhile, practically everyone I know is partying, having fun, going to the beach and I'm here, at home, typing this fucking rant and feeling sorry for myself.

I also wanto to get fit but every time I try to do so something happens and I have to wait 2 months in order to start again.

There isn't anyone I can trust enough to share some feelings and thoughts I have and this is eating me up.

I am unhappy and have been like this for a while now. Every once in a while I smile, yes, but most of my day is endless boredom either because of work or the lack of it. I just want to go back to normal, I don't want to think about my future, I want someone to talk to, I want to be able to cry.

I hate this.

Forgot to post a book yesterday, so maybe I’ll post two books today...

Anyway, this book, I found it recently never seen it before. But boy is it great.

It’s similar to the programming pearls book as far as what it’s about. Think of the refactoring book, clean code, programming pearls, and the mythical man month books, thrown in a blender, added some new spice and some new things, and filtered down into 100 or so page book, simple quick and enjoyable actually.

This book the references staple books by Sedgwick, knuth, Brooks, Myers, and so many others. It’s funny how things come full circle.

My favorite quote from the book. I’ve been essentially saying this for years, but to see it on a book, it’s lovely... more people need to realize it too.

“Understanding how things work at a low level becomes a base for making good decisions at the high level”

Followed up with if you’ve never built a computer from scratch your missing out... get yourself a breadboard and some TTL logic.. and build a 4 bit CPU, once you know how to program in assembly the next step is building your own computer ... if your university didn’t teach a class that did this they ripped you off....

Don’t bitch at me.. the book said that.. and I agree! 100% because it’s true, you can’t debate that.

Oh and btw this is another book written by a female developer.. kudos to her for nailing so many topics in such a short book!

I just learned that linux shouldn't be called linux but GNU (or GNU/Linux)

I am a student and currently learning programming but also I looked into history and saw this interesting fact.

Basically, there was a guy who wanted to make operating system similar to unix but free to use and distribute. He called it GNU. After few years, it was getting finished but it was missing few parts. One of those parts was kernel. So people glued together this low level kernel called Linux, mid level GNU and some other stuff on top of it. It was first known as GNU/Linux and slowly GNU was kicked out of the name even though 'Linux' - the whole OS constisted more of GNU than Linux kernel.

Doesn't this seem like injustice? Am I wrong somewhere?

Did I ever say I love my PM? He's fucking awesome.

In the summer I got an internship at this company and the PM had plans to turn me into a permanent employee, junior position I assume. I told him I'd need a month after school started to see how things went with school and the job at the same time. In the end I decided I couldn't work full-time because I don't have time for it. Also, I want to explore a bit the CS field and see if there's anything else I like (quantum computing and low level programming are at the top of my list), so I decided I won't be renewing my contract as an intern either.

Last week I went into a call with my PM to tell him about all of this and I did not expect the response I got. He actually thinks I'm doing right and supported me in my decision to learn other things. I didn't expect this kind of response at all and it made me feel much, much better (I was pretty nervous to tell him). He also told me that if I want to work on something else in order to learn I just have to ask (I currently do web dev).

But that's not all. He gives us, developers, space to work and doesn't micromanage us. He has technical understanding, doesn't force deadlines on us and understands that sometimes things take longer than expected. He is just great and I'm kind of sad I'll be leaving this job because he's awesome and (from what I read here on devrant) that seems to be pretty rare.

Anyways, that's it, no anger or anything today, I just wanted to say I like my PM very much.

FFUUUuucccckkk me sideways. So I decided to look into USB type-c's power delivery and alt modes. Cause I kinda want to make an adapter card to run my displays over a single cable. TLDR of the rest: USB-C has some huge capabilities which noone is interested in using since its way to complex to handle for what its worth in the end.
Now PD alone is kinda ok to deal with since a lot of powerbanks use it and some hobby guys documented how to work with it. I find it really odd thou that you NEED to use a dedicated IC for using the configuration chanel to negotiate how much power you can draw. Why the USB standard didnt use some simple 5V low speed signalling? Also the standard says that you only have to implement 5v 0.6A with every other power level being optional. (This is also true for cables. Most manufacturers use only the USB 2.0 standard for them and brag about how fast type-C is. ლ(ಠ益ಠლ) )
Now to the alt modes. These motherfuckers are a real shitshow to deal with. First you need a Mux to deal with USB-C's two way insertion, so your signals wont get flipped. Next thing is that you have four lanes at your disposal in alt mode. Which you can either use for four Display Port Lanes or two DP lanes and two USB 3.0 lanes. (You always get USB 2.0) Now you may think that there would be one simple chip to do it all? Nope you need atleast two at the price of 6$ each. One for PD and one for Alt modes. Both are very hard to solder (QFN, 0.5 mm pitch 40+ pins) TI ended up being the only one with a decent offering of IC's that do what I need. As for working with them, you would think that you just slap a simple MCU on there that communicates over I2C or SPI to configure the chips? Nope! You program the chips memory from which it configures itsself. And the programming is done with some TI tool which gives me no idea as to how you can handle everything whith no control logic behind it.
Looking into alternative IC's leaves me with cypress semi. And their documentation is basically a total mess. I wanna know what that chip is good for and what I need to do to make it work. I dont care about technical details mixed with marketing jargon nobody understands. And I really despise that I have to register just to download a datasheet. Especially since there is no info about it on the main page.
And this whole rant hasnt even touched the topic that USB-C only uses DP and nothing else. So you better hope that you have DP++ so you can use a passive conversion.
This was my Ted Talk about USB-C. Some info in it may be subject to my stupidity and errors as it currently is 02:15 in the morning and I need some sleep.

First year: intro to programming, basic data structures and algos, parallel programming, databases and a project to finish it. Homework should be kept track of via some version control. Should also be some calculus and linear algebra.

Second year:
Introduce more complex subjects such as programming paradigms, compilers and language theory, low level programming + logic design + basic processor design, logic for system verification, statistics and graph theory. Should also be a project with a company.

Year three:
Advanced algos, datastructures and algorithm analysis. Intro to Computer and data security. Optional courses in graphics programming, machine learning, compilers and automata, embedded systems etc. ends with a big project that goes in depth into a CS subject, not a regular software project in java basically.

I really like this book on the basis of the philosophy overall, no this doesn’t solve all problems but it’s a good baseline of “guidelines/rules” to program by. Good metrics or goals to architect and design software projects high and low level projects.

Fight Software Rot
Avoid duplicate code
Write Flexible, dynamic, adaptable code
Not cargo cult programming and programming by coincidence.
Make robust code, contracts/asserts/exceptions
Test, Test, and TEST again and Continue testing.. this is a big one.. not so much meaning TDD.. but just testing in general never stop trying to break your software.. FIND the bugs.. you should want to find your bugs. Even after releasing code the field continue testing.

20 years later us high level language developers we will be considered low level language developers,programming GOd's and Goddess

Ye, so after studying for an eternity and doing some odd jobs here and there, all I can show for are following traits:

* Super knowledgeable in arm/Intel assembly language
* C-Veteran with knowledge of some sick and nasty C-hacks/tricks which would even sour the mood of your grandma
* Acquired disdain of any and all scripting languages (how dare you write something in one line for which I need a whole library for!)
* All-in-all low-level programmer type of guy (gimme those juicy registers to write into!)

After completing the mandatory part of my computer science studies, all I did was immerse myself into low-level stuff. Even started to hold lectures and all.

Now I'm at the cusp of being let free into the open market.
The thing is: I'm pretty sure that no company is really interested in my knowledge, as no one really writes assembly anymore.

Sure, embedded programming is still a thing, but even that is becoming increasingly more abstract, with God knows how many layers of software between the hardware and the dev, just to hide all the scary bits underneath.

So, are there people in here who're actually exposed to assembly or any hands-on hardware-programming?
Like, on a "which bit in which register/addr do I need to set" - kind of way.

And if so, what would you say someone like me should lookout for in a company to match my interest to theirs?
Or is it just a pipe dream, so I'd need to brace myself to a mundane software engineer career where I have to process a ticket at a time?

(Just to give a reference: even the most hardware-inclined companies I found "near" me are developing UIs with HTML5 to be used in some such environment ....)

I fucking hate this low level programming shit. The fucking buffer overflow attacks and the whole understanding of the system architecture just goes over my mind. Can anyone who has found relatively useful resources be kind enough to refer them to me so my stupid mind can understand that better?

Idk why I had the idea to research how sockets work in X86 Assembly. I’ve just been weirdly obsessed with low level stuff recently.

Edit: and obsessed with network programming.

!rant (all ranters should read)

Today I was at university, doing some C low-level stuff. Then I looked my Professor.

Holy fucking shit, this man (and obviously the others) learned programming without google, stackoverflow, youtube and online doc/forum/examples/explanation.
I also believe that some of them could not compile and run at home their software.

MASSIVE RESPECT FOR YOU ALL !

I think I need some "programming detox", a couple weeks away from any kind of software development. It's just not fun anymore, I have lost my drive, I'm lazy to learn new stuff, I never finish my projects, I don't even know if I enjoy web development anymore.

Actually, I'm kind of lost on what to do with my life.

I don't want to become a full time web developer because it's boring, it's always the same shit: write frontend with some sort of framework, design database, write backend, rinse and repeat. There's nothing new, all projects seem to have the same requirements.

I don't want to get into machine learning and whatnot because it's a lot of math and theory, I like math but idk if I would like doing that all day. Same goes for basically anything related to research.

Low level stuff: on paper I like it, it's interesting, but I'm too lazy to learn and whenever I come up with a robotics project I end up making a shopping list and forgetting about it because either 1) stuff is too expensive or 2) I can't make the parts I want without spending a lot of money on tools. Also from what I can see in school, VHDL is boring af.

I just don't know what I like anymore, nothing gets me excited, not even video games. I used to like csgo but I just suck at it and I only play it because there's nothing else to play and deep down I still have a little bit of hope of becoming a decent player, even though I know I never will.

I just don't know what I want out of life. Sometimes I just like having tons of school assignments (especially calculus ones) just to keep me busy.

As a junior dev from a sysadmin and security background, this is a list of software development concepts I never seemed to truly understand but hope to(rated from most intimidating to least):

1) Frontend web development and all the huge world of javascript frameworks and tools. - It's more overwhelming than the political geography of the Holy Roman Empire in the Middle Ages.

2) Machine Learning, Deep Learning and A.I- too much math that fucks with my brain.

3) low-level programming(kernel,drivers) - sounds extremely interesting but the code in assembly/C/C++ looks like Linear A Minoan hieroglyphics.

4) Rx(insert language here) - I never get why it is useful or why someone invented this. Seems interesting though.

5) Code Reflection - sounds like Thelemic magick.

6) Packaging, automation, build tools, devops, CI, Testing -seems too complicated. I just want to run an executable at the client or make a web app that does something. Why all this process?

am i the only one that finds ui stuff (angularjs+css+makeing it look the way you want-tml etc..) alot harder to master then backend and even low level programming?

is somthing wrong with me??

DOM manipulation using vanilla JS is now "Low-level web programming"? 💀

it would help if i had time to learn even a little more C, as I'm bumbling my way through the Linux kernel and GodMode9 (an amazingly powerful 3DS manip tool for everything from the SD card to the NAND to literally raw FIRM0/FIRM1 bootloader access) to try amd patch some code from GM9 into the kernel to handle the SD card *properly* so Linux 3DS doesn't constantly hang when reading/writing to the SD card, to enable Wi-Fi access (same bus location and similar bus structure as SD/NAND access, different processor,) enable NAND decryption and access (yes, really, NAND is encrypted via software, which is... ...fun...) and more.

tl;dr: the 3DS hardware, C, and others' code collectively make me wanna slit my fucking wrists. Hopefully my sacrifice allows higher-level programming languages to be visble for low-level jobs in the future.

A "portal" built on Drupal 7. Started by someone who cannot do anything outside Drupal, and overseen by someone who believes JS to be "low level programming" (he literally said that).

What normally would be a table with 7 columns is instead 7 tables joined together. That goes for each data structure.

Each page, built in a separate module, either manually includes the same css files, or simply copy/pastes them.

Old, legacy modules have been hacked, and now depend on newer modules... Which, in turn, depend on the same old ones.

The theme contains huge, hardcoded parts of logic, so it can never be updated.

Worst part of it? It's only 3 years old. And there are people buying it as SaS. Already hitting bottlenecks at 2k users.

Developing a compiler is the only thing in programming that is as difficult as building an Operating System.

Anyone here worked a whole lot with low level programming?

I have always worked with high level languages like Python and C++, but I’ve also had an interest in working with embedded systems, real close to the metal.

Any directions on where I should go to start learning low level programming? Sites, languages, etc?

Appreciated devRant fam!😊

I've been trying to diversify programming languages I know.

It's been rough; I just don't like a lot of the high level programming languages and low level ones are often tough to learn to for someone without formal CS background.

Then I tried Go, and you should too!

Don't you guys think we need live programming?

Like a development runtime, instead of doing this whole file based development thing? We edit files, and then run them, why aren't we just running a program constantly and editing it as it runs? It would let us inherently take advantage of concepts like objects and lists instead of having to build plugins that analyse and modify our files to sort of act like complex programming data structures.

If we just programmed using these complex data structures to begin with.

Like do you realise how antiquated the idea of a file is, and folder, that's literally a paper based analogy.

Imagine if we just had objects, with pointers and property names, the best we have is ln -s file1 file2 but that's not a real pointer.

Anyway, hope someone understands me!

I'm writing a medium article called a world beyond files but I'm stuck at how low level to go and who the audience of the article should be.

I went really in depth into what this idea of an "object" is, and how it can be expressed in a file but once a program picks it up it becomes much more and almost alive.

I feel like saying "I know C#" (or Java or other similar languages) to mean that you know it as a language as opposed to more of a framework is ridiculous. We should say what programming language level we know (high, mid, low...) since the difference between say C# and Java is pretty much the same as the difference between say WinForms and WPF. Depending on which two languages and which two frameworks you choose it can be a much bigger difference between the frameworks than the languages.
In a CV I'd like to say "I know x-level languages with experience in [actual programming language + frameworks]" instead of saying I know C# and then recruiters and HR people and such assume I don't know Java at all, but know MVC, WebForms and whatever else even though I might specialise in something else and would take me pretty much the same to get proficient in Java as it would take me to get proficient in that framework or something that's technically C#.
It just makes so much more sense to me. As a dev you're supposed to know the principles, the syntax should be secondary. A pointer is a pointer regardless of it's marked with a * or IntPtr or just a value in a register with no special marking that it's a pointer...
Can we, as devs, come up with something like this?

While teaching theory is actually good, it doesn't mean that there is no room for any practical education either. Students needs to be exposed to modern programming languages like Python, Ruby while at the same time be trained in the pioneers of programming like C, C++, Java. It is only then would they be able to make informed decisions on who they really want to be. If you had one practical lab session on C and Java and then the rest of the semester about HTML, students would end up moving away from programming.

Concepts like programming and networking concepts should be included whereas ancient technologies like programming micro-processors (x386, x486, etc) should be excluded. Who programs x386 and x486 micro-processors anymore? While the understanding of how micro-processors and other low-level components in the computer systems work is very essential, doing practicals on them isn't really a good use of students' time, energy or effort.

That feeling when your friends' college life kind of depends on you helping them out in this assignment using a low level programming language (low level means it was meant to operate on the machinery level) that you were really good in at the first semester. Then you realize that you have forgotten a lot of things just because the logic and approach ist totally different from the high level programming language and you forget how a programming language works once you stop using it and it takes time to dive back in and you really like being friends with them. Now all you're left with is with the fear of letting them down.

I am fed up of developing websites backends and do not like working on frontend. What areas should I work in, where I can get to learn low level programming and build something to be proud of rather than shitty shiny websites with CRUD operations mostly dictated by frameworks and libraries.

Nothing's gonna make you hate life more than low level graphics programming

What would be the easiest starting point on low level languages?

I started with java, learned to hate it.
I continued with web development, learned to hate it.
Continued with PHP, learned to hate it.
Continued with scripting languages like Python, NodeJS, etc.., hated it from the beginning but it was easy.

But everytime i touch something like c/c++/rust/etc i immeadiatly give up, because the syntax is so different than all these other high level languages and so much null/type safety and so on.

But i want to get into low level programming languages which compile to an executable and don't get executed on some "vm".

The near future is in IOT and device programming...
In ten years most of us will have some kind of central control and more and more stuff connected to IOT, security will be even a bigger problem with all the Firmware bugs and 0-day exploits, and In 10 years IOT programmers will be like today's plumbers... You need one to make a custom build and you must pay an excessive hour salary.
My country is already getting Ready, I'm starting next month a 1-year course on automation and electronics programming paid by the government.

On the other hand, most users will use fewer computers and more tablets and phones, meaning jobs in the backend and device apps programming and less in general computer programs for the general public.

Programmers jobs will increase as general jobs decrease, as many jobs will be replaced by machines, but such machines still need to be programmed, meaning trading 10 low-level jobs for 1 or 2 programming jobs.

Unlike most job areas, self-tough and Bootcamp programmers will have a chance for a job, as experience and knowledge will be more important than a "canudo" (Portuguese expression for the paper you get at the end of a university course). And we will see an increase of Programmer jobs class, with lower paid jobs for less experienced and more well-paid jobs for engineers.

In 10 years the market will be flooded with programmers and computer engineers, as many countries are investing in computer classes in the first years of the kids, So most kids will know at least one programming language at the end of their school and more about computers than most people these days.

I am a junior / new grad and I am working at my first job out of school. The software team is very small (around 5 people) and we maintain a very large project. Since the project is so large, each member of the team is responsible for a specific part of the project.

Other members on the team work on embedded and low level programming. I am responsible for only the web interface to the project.

I recently just figured a solution for a problem that I had been exclusively working on for almost 2 months.

I tried asking for help from other members of my team when I was working in this problem. However, most of them told me that they do not have the time to become familiar with the my codebase inorder to help.

As a junior, what am I supposed to do in this situation? I know I could’ve asked a question on stackoverflow but I thought that if members of my team helped me, it’d be a beneficial mentorship experience.

What are your thoughts?

I'm thinking about what language to dive into next.
I already have a pretty good knowledge of Go and mediocre knowledge of C and Java.

So far I thought about...
1. CPP, as I need it for school and it runs on literally anything.
2. Rust, as is seems to spread and the combination of low-level, memory-safety and abstraction seems pretty appealing to me.
3. Kotlin, specifically kotlin-native, is it combines java-like high-level programming with native speed.
4. Nim, as it combines high-level techniques with c-like freedom.

What do you people recommended, or something completely else?

Thinking really hard about starting my own retro pc collection starting with the NEC pc-98 ......hmmmmmm wondee how my wife would feel about me spending money in this shit

Recently I have taken to all things retro tech, always liked it really, specially since my mom showed me pics of me playing with an old commodore 64 when i was younger as well as another of a family friend showing me the sharp 68k this shit fuels my appetite for knowing more about the programming ways of the old school coders. Some pretty interesting stuff, I feel that the newer generations would benefit greatly by knowing the things we had to do in order to build efficient programs back in the day. Not to say that I was part of that at all. I was born in 1991, how I came to see these systems is unknown and forgotten by me, but something that none the less os part of my story in computing.

Because of the industry that surrounds me I have been dealing with working with web development, but shit is really not that much of a passion of mine, had I the skills more than the academic knowledge I would love to work with low level C code all day, I just feel that the things that developers do there are so much more interesting than handilg web development, web development is tedious and a current shitstorm, not to say that shit was not like that for the programmers that i am referencing, but i just want more.

Web development has made me a successful man, at 28 i am the head of my department, I might sound like a Disney princess but I want more, I want more knowledge and more experience in different areas of Computer Science. I want to know it all and it seems like time continuously goes against me.

Oh well, here is to a new year lads, see what i can do.

Good code is a lie imho.

When you see a project as code, there are 3 variables in most cases:

- time
- people / human resources
- rules

Every variable plays a certain role in how the code (project) evolves.

Time - two different forms: when certain parts of code are either changed in a high frequency or a very low frequency, it's a bad omen.

Too high - somehow this area seems to be relentless. Be it features, regressions or bugs - it takes usually in larger code bases 3 - 4 weeks till all code pathes were triggered.

Too low - it can be a good sign. But it should be on the radar imho. Code that never changes should be reviewed at an - depending on size of codebase - max. yearly audit. Git / VCS is very helpful here.
Why? Mostly because the chances are very high that the code was once written for a completely different requirement set. Hence the audit - check if this code still is doing the right job or if you have a ticking time bomb that needs to be defused.

People
If a project has only person working on it, it most certainly isn't verified by another person. Meaning that only one person worked on it - I'd say it's pretty bad to bad, as no discussion / review / verification was done. The author did the best he / she could do, but maybe another person would have had an better idea?

Too many people working on one thing is only bad when there are no rules ;)

Rules. There are two different kind of rules.

Styling / Organisation / Dokumentation - everything that has not much to do with coding itself. These should be enforced at a certain point, otherwise the code will become a hot glued mess noone wants to work on.

Coding itself. This is a very critical thing.

Do: Forbid things that are known to be problematic in the programming language itself. Eg. usage of variables in variables, reflection, deprecated features.

Do: Define a feature set for each language. Feature set not meaning every feature you want to use! Rather a fixed minimum version every developer must use and - in case of library / module / plugin support - which additional extras are supported.

Every extra costs. Most developers don't want to realize this... And a code base that evolves over time should have minimal dependencies. Every new version of an extra can have bugs, breakages, incompabilties and so on.

Don't: don't specify a way of coding. Most coding guidelines are horrific copy pastures from some books some smart people wrote who have no fucking clue what you're doing and why.

If you don't know how to operate on people, standing in an OR and doing what a book told you to do would end in dead person pretty sure. Same for code.

Learn from mistakes and experience, respect knowledge from other persons, but always reflect on wether this makes sense at this specific area of code.

There are very few things which are applicable to a large codebase on a global level. Even DRY / SOLID and what ever you can come up with can be at a certain point completely wrong.

Good code is a lie - because it can only exist at a certain point of time.

A codebase should be a living thing - when certain parts rot, other parts will be affected too.

The reason for the length of the comment was to give some hints on what my principles are that code stays in an "okayish" state, but good is a very rare state

Get a bachelors degree or higher from a decent uni or college. It's gives you a solid foundation teaching you stuff that you wouldn't otherwise spend time on because frankly it's shit boring. Like compiler technology and low-level programming languages. I believe this broader understanding which eventually allows you to become a better developer and architect.

Yes, the first year at a real job will teach you a ton more relevant stuff than 3 years at uni. But that's just not what it's about. Ignorant people just think it is.

I dunno if this is a rant or an anti-rant, but for some reason, Assembly and low-level development hardly ever tick me off. It absolutely dumbfounds me how what many regard as the most frustrating and difficult ways of programming a binary digital computers is just so enjoyable. I spend hours per day teaching myself C and GNU Assembly and how it works with little actually getting done. It just rarely gets frustrating enough to rant about. Ladies and gentlemen I think I have found my calling!

What programming books do you all recommend?

Language wise any books on C, GoLang, Python, Rust, and LUA are welcome

And topic wise I’m interested in books about computer science theory, network programming, low level programming, and backend programming are welcome.

I know it’s a wide variety of topics but some are stuff Im currently doing, I’ve already messed with and just really want to learn more or focus on, or plan to do it when I get around to it

The most productive way of development is going slow and don't make a lot mistakes. Lately, I'm doing the opposite. It's often not your skills or knowledge but just your patience / expectation to be managed. Since I switched from C to Python I got the mindset that everything should be possible to make in short time with low effort. Being used to do a lot of effort because of C development gave me a lot of patience and upgraded me to be a better dev at any language. But sadly, I notice it's a skill you can lose. How to retrain my patience. Doing a lot of C again. But I want to have the patience NOW (retoor said impatiently). What a paradoxale dilemma shit. You have to do patient stuff to be become patient whey really sucks and sucks if you became inpatient.

Very underrated skill that actually says a lot about you as programmer: patience.

With enough patience you can master anything. Without it, you're depending on tools that allow you to. That's OK, but there's always some price to be paid. Many time it's the ignorance not knowing how the tools work and thus how it actually works. Some people can live with that, others don't. Knowing how somethings works is relative anyway. Do you know how it works until the language level? Kernel level? Framework level? Everyone chooses themselves what the limit is I guess. My limit is the C api / kernel interface.

Random thoughts. I'm just bit frustrating performing low lately and speculating about what to do about it. I just don't have a different hobby than programming. Doing something else for a while to give brain a rest would be best but it should be something raising dopemine. TV / gaming doesn't do that for me.

Sigh, how to do absolutely nothing. I did it for a 1,5 year full time but that was because of medication. Now it's impossible.

I'm currently mostly learning web dev, but do you guys have any book recommendations for other fields of programming. Perhaps something low-level or something like distributed systems. Everything goes.

How do I get into low-level programming?

I already know Java Js and Python and I feel I want to take my skills to the next level and learn C or Go.

But what to start with in that area after I learn the language? I have no idea what to do with low level stuff.