TABLE BASED WEB DESIGN

I was surprised there were no rants about this topic before I realized it was more than a decade back 😳

We've never had it better! So to help add a little perspective for all those ranting about what is unarguably the golden age for web developers... let me fill you in on web dev in the late 90's;

JavaScript was a joke. No seriously! - I once got laughed out of the room for suggesting we try use it for more than disabling a button - (I wanted to check out the new XHR request thingy [read AJAX]).

HTML was simple and purely a markup language (with the exception of the marquee tag). The tags were basically just p,ul,ol,h*,form inputs,img and table and html took 10 minutes to learn. Any style was inline and equally crude - anything that wasn't crude could not be trusted and probably wouldn't render at all in most browsers (never mind render correctly).

There were rumors of a style TAG and something called a cascading style sheet which were received with much skepticism since it went against the old ways and any time saved would be lost writing multiple [IE version specific] style sheets for each browser just to get it to work - so we simply didn't.

No CSS meant the only tags you had to work with to create a structured layout were br, hr and table... so naturally EVERYTHING was in nested tables! JS callback hell can't touch this! - it was not uncommon to have 50+ nested tables all with inline style in a single page which would be edited without any dev tools or linting.

You would spend 30 minutes scanning td tags until your eyes bled to find something, make a change, ftp the file to the server, reload the web page and then spend 10 minutes staring at the devastation on your screen convinced you broke
the internet before spotting an un-closed td tag with your bloodshot eyes.

Tables were not just a silver bullet - they were the ONLY bullet and were in the wild west!

Q: Want an inline form or to align your inputs left?
A: Duh table!

Q: Want a border with round-corners, a shadow or blur?
A: That's easy! Your gonna want to put that table in the center cell of another table then crop a image of the border into 6 smaller images to put in the surrounding cells... oh and then spend 10 minutes fucking with mystical attributes like cell-padding and valign to get them flush.

...But hey at least on the bright-side vertically & horizontally centering stuff was a breeze!

So this other senior dev got seriously ill a couple of weeks ago and the project he was working on was assigned to me. His code was so aesthetic, loved his work, the structured code helped me a lot in meeting the deadlines. He returned a few days back and now the company has given him two weeks notice because "his pace is slow". I am frustrated, PM is frustrated. The guy is such a gem that he is still helping with all the new requirements client is throwing at us.

Having PHP as my most useful skill.

I know various other languages, but they're either too exotic for professional use, or my knowledge about them doesn't have the same depth as with PHP.

People joke about how awful PHP is, and it's not entirely true. The incongruous stuff such as confusing parameter ordering can be fixed with libraries. And PHP7 fixed a lot of the ugly stuff. A good dev can certainly write structured, readable, performant PHP code.

But there is a real hard limit. PHP is missing more complex type definitions present in other languages. A weak type system is like building stuff with popsicle sticks and bits of duct tape, it works fast and perfectly fine for small projects, but the lack of strictness is a problem when you have thousands of classes intertwined in all kinds of complex factory, service and repository patterns. And the simple type hints are still newish and fully optional, which means a lot of people don't use them.

So I regret getting stuck in this self reinforcing loop, where I learn more about a very imperfect language through employment, and keep rolling into jobs using that skill because it's what I'm most experienced with.

Roommate: I thought you aren't into social media...

Me: This is devRant, it's different.

Roommate: How so.

Me: It's for like minds, very well structured and has this fun feature which let's me create myself as a cartoon for my profile pic.

Next Day..........…......……

Me: (walks into the room) Why are you laughing and why are you using my phone.

Roommate: I THINK I LOVE THIS APP. I might actually download it.

Note: Roommate is a musician who studied CS in school.

So I missed the first 3 days of my programming class. Once I showed up to the 4th the professor was really cool about it. She informs me on the HW I missed and so after the test she handed me (which was overdue as well) I started on the HW. By the end of the class I show her the exercises I did and just by how I structured each function (Python btw) she could tell that I was advanced for the class... I was surprised when she said that I didn't have to show up to the class because it would be a waste of my time, and that I can use the time to focus on personal projects. She offered to help me out with database dev (which ironically I planned on reading head first sql after a design pattern book). The thing that hit home was when she said "I think you're going to be a great programmer."

Anyone else notice this trend:

1. Don't go to uni / drop out (who needs education).
2. Get a job in IT, it pays well (who cares you don't have a structured logic).
3. Learn need-to-know stuff only (I only need to know my code).
4. Tell others they should get into programming, it's not that hard.
5. Get asked about the workings of a computer, but that's not in your domain of work. "I only code".

Millennial much ?

Developers coding cycle:

Start of Project - "Right, I am going to make this code clean and structured."

Deadline looming - "F**k it, just throw the code in there and get it finished".

Olivia Wilde's jawline is better structured than my code :-/
*internal screaming*

Debugging somones hacked site now, you know some developer messed up when the heckers injected code is more readable and structured than the actual sites...

Four meetings today.

Legal was not involved in legal agreement changes until I refused to make them without Legal signing off. Legal changed several things, leading to:

Project scope changed size from large to minuscule to small to medium.

Details changed at every step.

Despite being incredibly structured and process-heavy, people at this company are so disorganized. 😕

WHY THE FUCK DOES IT HAVE TO END?

WHY THE FUCK DOES ANYTHING HAVE TO EVER END?

When I left my previous employer, I was so connected to people there. In fact my entire direct team was just few months old.

I ended up crying like a baby on my farewell call in front of everyone. I just couldn't stop.

Definitely not the brightest or smartest people, but surely great at heart. I did hate them at times and we had our ups and downs but they made the place tolerable.

The work culture is created by colleagues at any organisation and not the leadership/management. And work culture was one of the major reasons why I stayed back for 7.25 years even when a rat was earning more than me.

I joined new organisation with a big smile on my face that, I will learn and earn more. And as I was buckling up, my lead quit.

She was one of the smartest person I met. She inspired me so fucking much. Our entire team is geographically located in multiple time zones. Still she never hesitated to jump on calls as early as 07:00 AM or as late as 12:00 AM. Yet she pinged me every time on Slack to check on me and made sure I was doing well. Kept pushing me to get enough sleep, take care and not burnout myself. Always handling her daughter while on calls with us without impacting the discussions.

She taught me like her own child. So patient with a retard like me. Gave me good feedback and insights on how can I grow as a person and what all to look for in the organisation.

She bids her final goodbye early next week and with every meeting we have, I get more emotional. Doesn't feel like we are in different continents but just in same room, talking like we have known each other for years.

And you know what, after joining this org, I came to know that they hired me for a level below what I was in previous org (because how the job titles were structured here and I don't really care for titles). The product I am working on is highly ambitious and everyone is keen to make it live.

And now everything falls on me. Kickass opportunity to get a promotion, relocation, good hike, and all that I desire. And my employer is known to be quite employee friendly to actually fullfil all my wishes.

But that's not what I want. I want my people with me. It would have been so fucking awesome if she wouldn't have quit and together we would have built the product and have had so much fun doing so.

I am sure, the reason of my death will be empathy. I am next to tears while I type this.

I suck at goodbyes. Even though, with the help of technology, people are and will be connected, but still goodbyes are the shittiest things to ever exist.

I developed a simple scholarship management system for my school using Laravel, MySQL, jQuery and Bootstrap, I did it for free since college students from my country have to pay social service to get their degrees. Everyone in the scholarships department seemed to be really happy with my work and they evaluated my social service with 10/10, but yesterday they asked for one last favor: to go talk to the new social service guy who'll be supposed to maintain my project, a mid 30's dude who was really pissed off from the beginning because he wasn't even able to deploy the project, he wasn't even able to clone the project from Github. Ok, so I tried to explain to him the tools I used and how the project was structured, but everything I said seemed to piss him even more, so I stopped and had a chat like:

Me: "Look man, do you know or at least have basic concepts of PHP and MVC frameworks?"

Guy: "Yes, but I'm a project manager, not just –despectively– any programmer, and you didn't write proper documentation, it's impossible to deploy your project with the manual you wrote, I cannot work like this".

*We go to their computer and I clone and setup the project in 3 minutes.

Guy: "Yes, but I still don't know how the project works, I need everything documented. If I have to change something, I don't know where to look.

Me: "Man, that's why asked you about knowing PHP MVC frameworks".

Guy: "I cannot work like this, nothing is documented, I don't even know what's that software you're using *points at Sublime Text*. Or tell me, can you arrive at a place where they expect you to work with something you don't know and they have no documentation?"

*At this point he was really pissed

Me: "Well... Dealing with non-documented software is what I do for a living"

Guy: "I don't know what companies you've worked for, probably not big ones..."

Me: "Well, I actually work for *I mention one of the biggest music apps in the country*"

*Guy ironically laughs

When I gave my feedback to the lady in charge of the department, I told her that this guy was really pissed off at how things were done and that I wasn't so sure of him being capable of maintaining the system. She told me not to worry, that the guy became a well known asshole in the office only after a few days, and that she'll probably have to find something else for him to do. It'd be hilarious if this guy ends up capturing scholarships in the system I made.

Whoever implemented the data import in Numbers on Mac needs to be lined up against a wall and shot with needles until they wish they were dead.

Why on all of gods unholy green and shitty earth would i want data i import (EVEN IN CSV FOR FUCK SAKE) to be delimited by an arbitrary text width? WHAT THE ACTUAL FUCK

WHY WHY why would I EVER want to delimit my carefully structured data by fucking text width instead of new line or comma? AAAAARRRHHH

And what fucking big brain genius made this the DEFAULT SETTING for imported text AND CSV FILES. IT STANDS FOR COMMA SEPARATED FILE YOU FUCK BOI MAYBE JUST MAYBE I WANT IT SEPARATED BY FUCKING COMMMMMMMAAAAASSSSSS

No matter how much product owners claim "bugs have priority over anything else", "we value high quality structured code", and "we do test driven development"...

...Once a big client wants a feature to be developed before they sign up, dirty code will be written from napkin specs, and that code will always be refractored "soon".

I have to start my best moment last year with a confession: I moved from Dev to Test half a decade ago. Naturally I do a lot of automation. My Best moment was when Dev said my automation code is so well structured that he wants to work on that and not an the production code anymore. Gave me that warm "still got it" feeling 😊

Post my vaccination break, I login to work today and this is waiting there for me..

My designer just dropped this note in our channel where we have our entire team including directors (my manager),

"I wanted to specifically give kudos to Floyd for creating the Confluence page for XYZ feature requirement.

It's so elaborate and very well structured 👏🏻"

And my Tech director adds to it and appreciates my efforts.

My TPM kept praising various new initiatives that I started and how it made him happy to see the progress + how everything was organised.

My skip level manager kept appreciating the work entire previous week and even in a meeting we had just before I started typing this post.

I feel like I have settled really well in this new org + started gaining trust of teams and leadership.

I need to continue the momentum before I start leading the product independently (a few more weeks should be good).

Now two things I am expecting in return, is good amount of international travel + good timely hikes.

And what's interesting is that my employer is known for these exact two things.

So fingers crossed.. 🤞🏻

Why are we still having degree vs autodidact arguments/debates?

It's fucking 2018, who gives a flying fuck how you learn?

Stop giving a shit about how people learn and give a shit about their abilities and skills.

I'm tired of people from both sides (people with degrees and autodidacts) acting like they're better than the other. Stop being arrogant cunts.

Some people have the self control and motivation to teach themselves.

Congratulations! That's fucking awesome.

Others don't and could use a structured environment like University to motivate and encourage them.

Hey it happens. At least you're trying.

My god. Just stop with this shit already. It's annoying and unnecessary.

If you made it this far, how's your week been going?

Some companies are structured and work as cults.

Went to company party several days ago and felt as if I was 🧠 🧼. The way they talk about the company, people, “mission”, social structure of employees etc. I literally felt as the only one who’s seeing through it.

Note to self: If I were to start my own company, I have to read a bunch of books about cults.

Anyone else worked at cult-like startups?

Not sure if I should be happy of I should cry.
...

I woke early today so I could directly start working on my little project to make some progress.
I was coding for ~10 hours.. The code worked fine for all testcases, except for one. I debugged for hours and I couldnt figure out what was wrong. I tried changing stuff in my code and it got more and more messy to the point where I couldn't even understand my own code anymore. I was so frustrated ...
> Deleted everything I made today.
> Rewrote the entire thing in one hour with a different, more structured approach.
> Worked perfectly for all cases, even the very complex ones.

1 day wasted....

Should I be happy that I came up with something decent in the end? I am still mad cause I wasted the entire day.. Why did I not directly went for the thing I did in the end ..? ._.

I suddenly realized all the technical debt shit I told my boss would happen years ago given the way things were done/heading then... Just occurred pretty much all at once last week in the form of critical production issues...

The teams like:
-we need real time server process monitoring
-structured logging for apps
-containerization so one app didn't affect others

Me thinking: yes.... I told you so like 3/4 years ago when I first joined the team and kept repeating so much I got tired of saying at every annual review...

This is exactly what happens when you let technical debt grow and have no free time for developers to look into and fix then while they were small and not critical production processes... Or properly document and peer review them... (Got a shit pile of projects that no one knows how to use or even exists because the devs left the team) and they'll have a lot more when I finally leave... Hopefully this year.... If I can find another role and not need another medical procedure... (Doubtful)

> be me
> post-well-structured question on SO
> very next millisecond, the question gets downvoted
> ¯\_(ツ)_/¯

You know you learned a lot in the last year when you try to change something on a website you made 1 year ago and it is almost impossible.

The code is not well structured. PHP mixed with HTML, functions that should be organized as a class etc.

I really, really, need to refactor the entire site!

Fuck (some of) you backend developers who think regurgitating JSON makes for a good API.

"It's all in JSON. iOS can read JSON, right?"
A well-trained simian can read JSON, still doesn't mean it can do something with it. Your shitty API could be spitting out fucking ancient Egyptian for all I care, just make it be the same ancient Egyptian everywhere!

Don't create one endpoint that spits out the URL for the next endpoint (completely different domain, completely different path structure). Are you fucking kidding me?

As if that wasn't enough, endpoints receive data structured in one way, but return results in another!! "It's all JSON", but it's still dong.

How do I abstract that, you piece of shit? Now I have to write ever so slightly different code in multiple places instead of writing it only once.

How the fuck do I even model that in a database?

Have a crash course on implementing APIs on the client side and only come back when you're done.

Morons.

Working in the embedded systems industry for most of my life, I can tell you methodical testing by the software engineers is significantly lacking. Compared to the higher level language development with unit tests and etc, something i think the higher level abstracted industry actually hit out the of park successfully.

The culture around unit testing and testing in general is far superior in java and the rest.

Down here in embedded all too often I hear “well it worked on my setup... it worked at my desk”.. or Oh I forgot to test that part.. or I didn’t think that perticular value could get passed in... etc I’ve heard it all. Then I’ve also heard, you can’t do TTD or unit tests like high level on embedded... HORSESHIT!

You most definitely can! This book is a great book to prove a point or use as confirmation you are doing things correctly. My history with this book was I gonna as doing my own technique of unit testing based on my experience in the high level. Was it perfect no but I caught much more than if I hadn’t done the testing. THEN I found this book, and was like ohh cool I’m glad I’m on the right thought process because essentially what they were doing in the book is what I was doing just slightly less structured and missing a few things.

I’ve seen coworkers immediately think it’s impossible to utilize host testing .. wrong.

Come to find out most the of problems actually are related to lack of abstraction or for thought out into software system design by many lone wolf embedded developers.. either being alone, or not having to think about repercussions of writing direct register writes in application or creating 1500 line “main functions” because their perception is “main = application”. (Not everyone is like this) but it seems to be related to the EEs writing code ( they don’t know wha the CS knows) and CS writing over abstraction and won’t fit on Embedded... then you have CEs that either get both sides or don’t.. the ones to understand the low level need but also get high level concepts and pariadigms and adapt them to low level requirements BOOM those are the special folks.

ANYway..the book is great because it’s a great beginner book for those embedded folks who don’t understand what TDD is or Unit testing and think they can’t do it because they are embedded. So all they do is AdHoc testing on the fly no recording results no concluding data very quick spot check and done....

If your embedded software engineers say they can’t unit test or do TDD or anything other than AdHoc Testing...Throw the book at them and say you want the unit test results report by next week Friday and walk away.

Lol

I don't understand why so many devs complain about not having money or complain about the company that they work for. We literally have the skills to do whatever the fuck we want in today's world. Literally everything is structured around what we do. If you hate your life so much, do something about it. Granted, I understand if you live somewhere that doesn't allow you to control your own destiny but I'm pretty sure that the majority of the people on this app has the ability to do so. The rewards are endless if you decide to think outside the box just a little bit. Sorry, this has just been on my mind for a while and decided to rant about it here since that's what this app is for.

So here's the deal. I am a team lead of a small company and I have a junior who is an idiot. I mean literally, idiot. We code in Python mostly and as Python is not structured as a default Java or C# project, the developer needs to be very careful so that the structure (or tiers) is maintained properly.

Now this girl, always messes up the tiers. Say one enhancement can be easily implemented in the UI tier, she would do the implementation in the core Db access layer, which may complete this particular enhancement, but breaks all the other functions (sometimes the whole project) connected to that particular module of the Db layer. She doesn't do any integration testing after updating the code, she only checks the current enhancement she is working on. When the enhancement goes to the testing phase, the testers find those broken functions and that results a re-work (most of the times done by me).

I have warned her. Even our manager has warned her. She always tells that she is working to improve herself. But I know, she isn't. She mostly chats with her boyfriends (yes, with an 's') when she has no work to do. She never upgrades herself or works on her skills.

I can easily report about her, and they will fire her without any warning (they did it already with a guy earlier). I don't want to do that again. What should I do? Any suggestions?

Oh, she has a great ego. She thinks that knows and understands everything. She will listen to your suggestions carefully, but will never follow those.

My friend ranting as his boss provided him a routine to make life more structured.

I hate it when code line are structured like this.Get().Start().Trim().Where(a=>a.id = newId).ToList().ConvertAll(...).EndMaybe().Name

Are you a fkin compiler or what

Be careful when you go down the rabbit hole of creating custom observables (rxJS).

I wasted half a day just to find out that there are hot and cold observables and that the whole time I tried to use the wrong one.

It finally works. 01:00 in the morning.
My boss will be proud when he pulls the changes and the code looks completely fucked up (clean, well structured code, but he doesn't really know observables).

Now something different: Sleep. Cya.

First time rant here, and I'm just gonna let fucking loose because this seems to be a good place for it.

My uni can't teach programming for shit. It's the reason people sign up for the course. They want to know how to program. I'm self-taught and unhappy in college as it is.

I joined CS because I thought they'd assimilate work in the real world, which is experience I need. I realized early on that programming is like art, and I love the rush I get of something finally working right.

That said, they sucked the fun out of it. It's too structured. Everyone trying to get the same goddamn result. In the real world, we'd be working on a larger project that involved planning, design, communication, teamwork, and the ability to complete each of our own pieces of the puzzle and subsequently put them together in a project that works for the end user.

I'm paying to be a fucking sheep, people. Why do employers give a shit about a degree instead of talent? Welp, fuck society for this. You can tell me I can drop it and still get a good job, it'll just be harder. That's the fucking problem. I can't get a job if these incompetent fucking bastards will throw out my resumé the moment they see "self-taught."

If we could hire based on GitHub contributions, I think many of us here would be relatively better off. Programmers program, not socialize. We do socialize, but in our own little groups. We team up as needed. The moment the jackass in HR realizes that, the better off we'll be.

Sorry, just the way I'm seeing shit right now. I'm going through some OCD-induced depression and this might be a result of that, but I'm passed the point of giving a fuck.

One of the most infuriating ideas in software development culture is that you can build maintainable applications without a strictly enforced type system and structured data.

Sure, it's more fun to wack around a dynamically typed system until it works or to write a major application with mutable datastructures... It's a least fun until a few years in and you have to debug an unexpected overwrite or a inconsistent use of an object property or whatever.

Anyone who writes maintainable code eventually figures out that you need rules and procedures, the issue with JavaScript, python, ruby, lisp, etc developers is that they think it's us developers that needs to enforce these rules instead of the compiler (which is infinitely better at it).

My Project Manager to me, after attending his first ever Hackathon of life

PM : Did you see, how people create a full project in a day,
So it is POSSIBLE and here you always complain about the deadlines

Me : Yeah true :|
Of Course it is possible to create a well documented, bugs free, features enriched, stable and properly structured project in a day
My Bad :/

"How useful was your CS degree and why?" - I studied CS at university, my education always was incredibly useful.

Firstly, the knowledge you gain in itself is useful. Furthermore, we explain and understand the unknown in terms of the known. Thus, the more you know, the easier you learn new things.

But secondly and more importantly, university teaches you *how* to think. In a structured way, like a scientist or engineer. To see the bigger picture.

I originally wanted to end here, but I've read a couple of entries doubting the usefulness of any CS degree.

Our profession isn't all that different from others. It is, however, relatively young. How's this for an analogy: We're still in the stage of building sand castles. That's fine, and can be self taught. But in years to come we'll want to build bridges and sky scrapers, which are not just "sand castles scaled up". Our sand castle knowledge won't help us here. Sky scrapers need entirely different materials and a good understanding of architectural statics.

Can you still teach that yourself? Maybe. Will a formal education with a degree be useful and generally more trusted? I bet.

At this point i'd like to talk about the original PHP founder Rasmus Lerdorf, who was obviously too distracted by his own beard while watching the NBA Playoffs in 1995 to write a proper language.

There's not a language more inconsistent, ilogical, deficient, and best of all, bad structured.

Seriously, which substances was he smoking when thinking up such things as: non objective strings, incasesensitive functions and associative arrays?

What have objects ever done? any other honorable language does that, python, javascript, rails, C#, take your pick.
Not to mention the order of needle/haystack parameters.

try philosophy()
catch markAsSpam()
Do you ever think of organizations as people? People personify Google and stuff all the time, but I mean something deeper.
When I look at devRant threads, I feel like we're all part of a collective consciousness, growing and thinking and making decisions. Society is a living thing of its own, in the same way that living cells unknowingly make up an individual body. When a question is asked from one node, another node answers, and the result is a repository of questions, answers, opinions, and jokes on an app that might appear as the scrolling thoughts of a singular mind rife with pure, aggressively structured information.

Yall ever cast a bool to a dateTime?

Fucking structured text never ceases to amaze me!

when you spend hours trying to patch code you poorly structured of which 30 minutes is enough to rewrite the whole damn thing.

I spent the last weeks rewriting a huge project which I had to hurriedly write a year ago. No comments, no documentation, spaghetti code. Part me was an asshole! But now I am done, all is new, everything is well commented, structured in classes with well defined tasks. Yay.

The role of a Product Manager is just a decade or two old. Most organisations, including FAANG, are still figuring out what are the primary responsibilities of a PM.

A vast majority I know, including my dumbass, is struggling to keep things floating while in the role. Learning on the job is one of the only and most effective way to do so.

No wonder, imposter syndrome is so common in this group.

One of the main tasks is to make decisions. Important and impactful ones. The role came into existence to take the decision making load off our engineering friends while building any product.

This shit comes with huge responsibility.

BUT, not everyone understand this. In India, being a developer was a cool thing until 2018 and so everyone rushed into the role. Now somehow everyone started thinking being a Product Manager is cool because all you have to do is sit and shoot orders and things will happen magically.

I get reached out by so many folks every month asking for guidance and when I ask them what a PM does or why they want to be a PM, the narrative is more or less same.

Very few actually understand how taxing the role is or the challenges that we face while performing the job.

WHY THE FUCK ARE PEOPLE SO IGNORANT AND DUMB?

And in another news, my first week at new job was super amazing. Loved every bit of it. People are smart, processes are neat, things are structured, and lots and lots to learn for me.

How are you guys doing? Been a while that we spoke.

Official declaration: I am the dumbest person I know.

As a pretty solid Angular dev getting thrown a react project over the fence by his PM I can say:

FUCK REACT!

It is nigh impossible to write well structured, readable, well modularized code with it and not twist your mind in recursion from "lift state up" and "rendercycle downwards only"

Try writing a modular modal as a modern function component with interchangeable children (passeable to the component as it should be) that uses portals and returns the result of the passed children components.

Closest I found to it is:
c o d e s a n d b o x.io/s/7w6mq72l2q
(and its a fucking nightmare logic wise and readability wise)

And also I still wouldn't know right of the bat how to get the result from the passed child components with all the oneway binding CLUSTERFUCK.

And even if you manage to there is no chance to do it async as it should be.
You HAVE to write a lot of "HTML" tags in the DOM that practically should not be anywhere but in async functions.

In Angular this is a breeze and works like a charm.
Its not even much gray matter to it...

I can´t comprehend how companies decide to write real big web apps with it.

They must be a MESS to maintain.

For a small "four components that show a counter and fetch user images" - OK.
But fo a big webapp with a big team etc. etc.?

Asking stuff about it on Stackoverflow I got edited unsolicited as fuck and downvoted as fuck in an instant.
Nobody explained anything or even cared to look at my Stackblitz.
Unsolicited edit, downvote, closevote and of they go - no help provided whatsoever.
Its completely fine if you don't have time to help strangers - but then at least do not stomp on beginners like that.
I immediately regretted asking a toxic community like this something that I genuinely seem to not understand. Wasn't SO about helping people?
I deleted my post there and won't be coming back and doing something productive there anytime soon.

Out of respect for my clients budget I'm now doing it the ugly react way and forget about my software architecture standards but as soon as I can I will advise switching to Angular.

If you made it here: WOW
Thank you for giving me a vent to let off some steam :)

It was not until 20 that I had access to regular computing. In school I had to take up Finance as my Maths was weak. I couldn't take Sciences including computers and how could I , my childhood wasn't as fortunate as my peers.

When I entered college I got my brothers old gaming pc as we had a couple of work laptops at home. I was always the inquisitive one. I got interested in web development just because of curiosity while I was on my first job and I hated it. I used to write article and freelanced and ran a website for friends where I learned a lot by trial and error. I single handedly learned mySQL, PHP and basic web development.

The main job was a core night from 11pm -8 am . Drained me and my social life drowned. I lost my brother in an accident. Silver Lining: I quit my job.

I understood I was interested in computers like nothing else. I single handedly learned a programming language. After leaving the job I took up classes to learn from root level in a structured manner: Web design and Development.

Now though I am jobless and I am searching for my second job it is for something I love. :)

These are the things that finally finally helped me stick to learning programming.

Hello world! This is my first story on devrant and I would like to share how I finally overcame the barriers that had always prevent me from learning programming in a more serious and structured way.

I know my way around linux, had some experience with BASIC many years ago and have more than basic notions of cryptography... however I never got myself to learn programming in such a way that I could write an app or interact with an API. Until now.

I have advanced more than ever before and I believe it might be thanks to these aspects:

1. C#
I have always had struggles with languages that were too compact or used many exotic or cryptic expressions. However I have found C# to be much more readable and easier to understand.

2. Visual Studio
My previous attempts at learning programming were without an IDE. Little did I know what I was missing!

For example when I tried learning python on Debian, I almost went crazy executing programs and trying to find the compile errors in a standard text editor.

Intellisense has been live changing as it allows me to detect errors almost immediately and also to experiment. I'm not afraid to try things out as I know the IDE will point out any errors.

3. .NET library and huge amounts of documentation
It was really really nice to find out how many well documented classes I had available to make my learning process much easier, not having to worry about the little details and instead being able to focus on my program's logic.

4. Strong typing
Call me weird, but I believe that restricting implicit conversions has helped learn more about objects, their types and how they relate to each other.

I guess I should be called a C# fanboy at this point, but I owe it to that language to be where I'm now, writing my first apps.

I also know very very little about other languages and would love to hear if you know about languages that provide a similar experience.

Also, what has helped you when you first started out?

Thanks!!

Years ago, we were setting up an architecture where we fetch certain data as-is and throw it in CosmosDb. Then we run a daily background job to aggregate and store it as structured data.
The problem is the volume. The calculation step is so intense that it will bring down the host machine, and the insert step will bring down the database in a manner where it takes 30 min or more to become accessible again.

Accommodating for this would need a fundamental change in our setup. Maybe rewriting the queries, data structure, containerizing it for auto scaling, whatever. Back then, this wasn't on the table due to time constraints and, nobody wanted to be the person to open that Pandora's box of turning things upside down when it "basically works".

So the hotfix was to do a 1 second threadsleep for every iteration where needed. It makes the job take upwards of 12 hours where - if the system could endure it - it would normally take a couple minutes.

The solution has grown around this behavior ever since, making it even harder to properly fix now. Whenever there is a new team member there is this ritual of explaining this behavior to them, then discussing solutions until they realize how big of a change it would be, and concluding that it needs to be done, but...

not right now.

The moment when you are too scared to make any needed changes in your code fearing you will untumble all the structured mess of spaghetti code you have written... 😳😨😕

That feeling when a feature is estimated to take 4 hours but, thanks to your well structured code and good use of object oriented programming you implement it in 30 minutes and can spend the rest optimising something else.

How do you guys/girls explain to potential new customers that you can perfectly work in a structured business environment and follow the rules, but also that you're assertive enough to oppose desicions being made based on bias, misunderstanding, fanboyism, or grave stupidity.

I just got informed from a freelance position that they would have hired me if it were not for my 'rebellious nature towards customers'

I don't oppose customers, i oppose stupidity unfounded.
Example from experience
> me working in a helodesk support position, all windows computer.
> new mgr comes into office, is a douche and complete mac fanboy
> wants all computers that are FINALLY working decent for some time in the entire department replaced with mac's... Back at 2010.
> whole team, even disliking microsoft themselves, are telling mgr that's a bad, dangerously dumb idea, expensive too, different OS, different software mgmt making, back then integration microsoft and apple was beyond diarhea... Several other issues the senior devs and admins pointed out

>mgr: 'but aple is soh much better, like a billion times better, hurrduurrrrr'
His decision passed somehow to the board..
> All stations from our customers get changed...we don't get a single machine to try out problems because overspending
> we are most of the time unable to help out customers because we still have pc's...
> mgr asks team why performance drops after 1 month
> we compared performance graph with his starting date of mgr, see clear drop after mgr's plan implemented...
> board stilll stands by mgr, gets praise for 'bold changes in the company', but appears to be some associate's son
> two main seniors leave after 15 years of employment, in three months, 80% of staff leaves.
> we canr fix the problems, we are not dev's , we get shit from all sides, i was still a junior in the industry so i worked as a slave inside that job.
> eventually get fired due to 'bad performance'
> mgr loses entire team... 'Hey why don't we outsource this dept to south africa, it's a lot cheaper! '

now that company is an it hellhouse where everyone get clinically depressed from sitting atbtheir station...
This is what i wish to oppose!

How to make that clear!

TL;DR:
JuniorDev ignores every advice, writes bad code and complains about other people not working because he does not see their result because he looks at the wrong places.

Okay, so I am really fed up right now.
We have this Junior Dev, who is now with us for circa 8 months, so ca. a year less than me. Our first job for both of us.
He is mostly doing stuff nobody in the team cares about because he is doing his own projects.

But now there's a project where we need to work with him. He got a small part and did implement that. Then parts of the main project got changed and he included stuff which was not there anymore. It was like this for weeks until someone needed to tell him to fix it.
His code is a huge mess (confirmed by senior dev and all the other people working at the project).

Another colleague and me mostly did (mostly) pair programming the past 1-2 weeks because we were fixing and improving (adding functionality) libraries which we are going to use in the project. Furthermore we discussed the overall structure and each of us built some proof-of-concept applications to check if some techniques would work like we planned it.
So in short: We did a lot of preparation to have the project cleaner and faster done in the next few weeks/months and to have our code base updated for the future. Plus there were a few things about technical problems which we need to solve which was already done in that time.
Side note: All of this was done not in the repository of the main project but of side projects, test projects and libraries.

Now it seems that this idiot complained at another coworker (in our team but another project) that we were sitting there for 2 weeks, just talking and that we made no progress in the project as we did not really commit much to the repository.
Side note: My colleague and me are talking in another language when working together and nobody else joins, as we have the same mother tongue, but we switch to the team language as soon as somebody joins, so that other colleague did not even know what we were talking about the whole day.

So, we are nearly the same level experience wise (the other colleague I work with has just one year more professional experience than me) and his work is confirmed to be a mess, ugly and totally bad structured, also not documented. Whereas our code is, at least most of it, there is always space for improvement, clean, readable and re-useable (confirmed by senior and other team members as well).
And this idiot who could implement his (far smaller part) so fast because he does not care about structure or any style convention, pattern or anything complains about us not doing our work.

I just hope, that after this project, I don't have to work with him again soon.
He is also one of those people who think that they know everything because he studied computer science (as everybody in the team, by the way). So he listens to nothing anybody explains to him, not even the senior. You have to explain everything multiple times (which is fine in general) and at some points he just says that he understood, although you can clearly see that he didn't really understand but just wants to go on coding his stuff.
So you explain him stuff and also explain why something does not work or is not a good thing, he just says "yes, okay", changes something completely different and moves on like he used to.

How do you cope with something like this?

My intern was trained on 1 semester of Java, followed by 2 of Python, so there’s been several conversations at the office that boil down to:

“What’s *not* to love about Python? It’s easy to pick up, and forgiving as hell!”

“What’s *to* love about Python? I like being able to understand how my code is structured!”

As a WordPress shop, the discussion is moot, of course...

Most successful? Well, this one kinda is...

So I just started working at the company and my manager has a project for me. There are almost no requirements except:
- I want a wireless device that I can put in a box
- I want to be able to know where that device is with enough accuracy to be able to determine in which box the device was put in if multiple boxes were standing together

So, I had to make a real time localization system. RTLS.
A solo project.

Ok, first a lot of experiments. What will the localization technique be? Which radio are we going to use?
How will the communication be structured?

After about two months I had tested a lot, but hadn't found THE solution. So I convinced my manager to try out UWB radio with Time Difference Of Arrival as localization technique. This couldn't be thrown together quickly because it needed more setup.

Two months later I had a working proof of concept. It had a lot of problems because we needed to distribute a clock signal because the radio listeners needed to be sub-nanosecond synchronous to achieve the accuracy my manager wanted. That clock signal wasn't great we later found out.

The results were good enough to continue to work on a prototype.
This time all wired communication would be over ethernet and we'd use PTP to synchronize the time.

Lockdown started.

There was a lot of trouble with getting the radio chip to work on the prototype, ethernet was tricky and the PTP turned out to be not accurate enough. A lot of dev work went into getting everything right.

A year and 5 hardware revisions later I had something that worked pretty well!
All time synchronization was done hybridly on the anchors and server where the best path to the time master was dynamically found.

Everything was synchronized to the subnanosecond. In my bedroom where I had my test setup I achieved an accuracy of about 30cm in 3d. This was awesome!

It was time to order the actual prototype and start testing it for real in one of the factory halls.

The order was made for 40 anchors and an appointment was made for the installation in the hall.

Suddenly my manager is fired.

Oh...
Ehh... That sucks. Well, let's just continue.

The hardware arrives and I prepare everything. Everything is ready and I'm pretty nervous. I've put all my expertise in this project. This is gonna make my career at this company.

Two weeks before the installation was to take place, not even a month after my manager was fired, I hear that my project was shelved.

...
...

Fuck

"We're not prioritizing this project right now" they said.

...

It would've been so great! And they took it away.
Including my salary and hardware dev cost, this project so far has cost them over €120k and they just shelved it.

I was put on other projects and they did try to find me something that suited me.

But I felt so betrayed and the projects we're not to my liking, so after another 2-3 months I quit and went to my current job.

It would've so nice and they ruined it.
Everything was made with Rust. Tags, anchors, RTLS server, web server & web frontend.

So yeah, sorry for the rambling.

Next week I'm starting a new job and I kinda wanted to give you guys an insight into my dev career over the last four years. Hopefully it can give some people some insight into how a career can grow unexpectedly.

While I was finishing up my studies (AI) I decided to talk to one of these recruiters and see what kind of jobs I could get as soon as I would be done. The recruiter immediately found this job with a Java consultancy company that also had a training aspect on the side (four hours of training a week).

In this job I learned a lot about many things. I learned about Spring framework, clean code, cloud deployment, build pipelines, Microservices, message brokers and lots more.

As this was a consultancy company, I was placed at different companies. During my time here I worked on two different projects.
The first was a Microservices project about road traffic data. The company was a mess, and I learned a lot about company politics. I think I never saw anything I built really released in my 16 months there.

I also had to drive 200km every day for this job, which just killed me. And after far too long I was finally moved to the second company, which was much closer.

The second company was a fintech startup funded by a bank. Everything was so much better than the traffic company. There was a very structured release schedule, with a pretty okay scrum implementation. Every team had their own development environment on aws which worked amazingly. I had a lot of fun at this job, with many cool colleagues. And all the smart people around me taught me even more about everything related to working in software engineering.

I quit my job at the consultancy company, and with that at the fintech place, because I got an opportunity I couldn't refuse. My brother was working for Jordan Belfort, the Wolf of Wallstreet, and he said they needed a developer to build a learning platform. So I packed my bags and flew to LA.

The office was just a villa on the beach, next to Jordan's house. The company was quite small and there were actually no real developers. There was a guy who claimed to be the cto of the company, but he actually only knew how to do WordPress and no one had named him cto, which was very interesting.
So I sat down with Jordan and we talked about the platform he wanted to build. I explained how the things he wanted would eventually not be able with WordPress and we needed to really start building software and become a software development company. He agreed and I was set to designing a first iteration of the platform.
Before I knew it I was building the platform part by part, adding features everywhere, setting up analytics, setting up payment flows, monitoring, connecting to Salesforce, setting up build pipelines and setting up the whole aws environment. I had to do everything from frontend to the backest of backends. Luckily I could grow my team a tiny bit after a while, until we were with four. But the other three were still very junior, so I also got the task of training them next to developing.
Still I learned a lot and there's so much more to tell about my time at this company, but let's move forward a bit.

Eventually I had to go back to the Netherlands because of reasons. I still worked a bit for them from over here, but the fun of it was gone without my colleagues around me, so I quit last September.

I noticed I was all burned out, had worked far too much, so I decided to take a few months off and figure out what I wanted to do with my life. I even wondered whether I wanted to stay in programming.

Fast forward to last few weeks. I figured out I actually did want to work in software still, but now I would focus on getting the right working circumstances. No more driving 3 hours every day, no more working 12 hours every day. Just work close to home and find a company with the right values.
So I started sending out resumes and I gave one recruiter the chance to arrange some interviews too. I spoke to 7 companies in the span of one week. And they were all very interested. Eventually I narrowed it down to 2 companies and asked them for offers. And the company that actually had my preference offered me significantly more than I asked for, which settled the deal.

So tomorrow I'm officially signing with them, and starting next week I'll be developing in Kotlin, diving into functional programming and running our code in serverless environments. I'm very excited!

Looking at anyone else's code in things I use. I just think to myself "damn this is so neat and structured, I've never made something like this"

The frustration that comes to each developer when he tries to write the code structured by thinking through each situations, and your team lead comes and tells you why r you doing so much validations just hard code them we need to release it today client is waiting. After 3-4 months the same team lead goes through the code and shouts at you telling why the he'll you hard coded all these, can't you write the code correctly by thinking through.

I am so fucking lost.

I literally have zero expectations from life for now and future.

There was a time when I had so much clarity in my life. Rather, I was known for it.
Folks used to reach me out for guidance and my approaches even worked for others.

I was goal oriented and biased towards action. Failing and learning from it, I used to make things happen and with constant feedback kept progressing.

While none of that has changed, I still feel lost and numb. No, I am not depressed or suffering through any mental illness. I am physical active and able to feel the happiness.

But the recent incident with a narcissistic, left me emotionally handicap. I can no longer feel any kind of love or affection. I overcame the damage done and healed myself.

But now, I am done. Even if I engage with anyone for a relationship it would be mostly for sex. I can care for people around me and be affectionate towards them but when it comes to an intimate relationship, I feel it's not something I can do in this lifetime. I tried multiple times but failed.

These days, all I am doing is putting my heads down and working like crazy. Never in my life I worked more than 10 hours in an entire week. Now, I work 10+ hours everyday. During that time, I am highly productive.

And in my free time, I am busy housekeeping different life problems. Either paying bills, figuring out an insurance, planning some investment, or making some kind of life decision.

It's draining me. I feel as if I am losing sanity. But that's the only thing I am able to do.

Maybe it's the lockdown effect. Maybe some damage is yet to be healed.

But I got nothing better to do. I have some good ideas. Not those hipster-ish disruptive Million dollar ideas, but decent enough to solve a problem for a strong use case.

However, all of this is becoming overwhelming these days. Because decision making is complex and difficult task. It can make or break the future.

As of now I am confused how should I go about pursuing two of the important projects that I want to accomplish.

1. Migrating out of Google ecosystem. Is it even practically possible for my use case? What are the alternatives? Planning to opt in for a paid cloud storage so have to factor in that aspect as well.

I want to keep this new setup only for official use like bank and government stuff. Maybe family and close friends. Then have current ids for public logins and sharing it with retards whom I can block or ignore if they harass me. The research is overwhelming but having a structured setup gives insane amount of efficiency when life is spam free.

2. Migrating my Pihole and OpenVPN setup out of Digital Ocean to GCP. Primarily because $5 is a lot of amount for my computational requirements and Google has used my data enough, for me to use the free tier.
However, there isn't a simple script for a tech noob like me, to go ahead and setup something. I did find a Github repository but the documentation is kind of outdated so RTFM failed for me.

I don't know whether to pursue my start-up or let it go and focus on moving to Europe.

It's just so fucking stupid to even exist. And let's not forget taxes. Bloody taxes.

My file structure:

Documents -
- That one impeccably structured folder that I never remember to put anything in

- Gigantic project folder that will some day kill me in my sleep

- That one unrelated folder that all of my non project scripts just end up in. No structure whatsoever

- about 2 billion loose files

HR wanted a Feedback-Interview, they choose me because I am new (first job as a Developer).
They wanted the pros/cons from my perspective and how to get more people into the company.

There was nothing bad that I could have said about the company, I really had to watch out so it doesnt sound like I wanna crawl into someones ass.
It changed when we talked about programming itself...

I am a ABAP Developer, we are developing with the EWM Extension. If you dont happen to know what I am talking about then you didnt miss a thing. Documentation feels like its not existend, the language is made to be red like Text for easy use but does a terrible job at that, the standard editor that you have to use lacks a ton of usefull features, the standard functions and classes that you HAVE to use are not structured well and need to be debugged to know how to use them, and and....

There is much more, but if the company wouldnt be so damn nice, I might have wanted to go away already.

ABAP: Advanced Business Application Programming.
EWM: Extended Warehouse Management.

We had 1 Android app to be developed for charity org for data collection for ground water level increase competition among villages.

Initial scope was very small & feasible. Around 10 forms with 3-4 fields in each to be developed in 2 months (1 for dev, 1 for testing). There was a prod version which had similar forms with no validations etc.

We had received prod source, which was total junk. No KT was given.

In existing source, spelling mistakes were there in the era of spell/grammar checking tools.

There were rural names of classes, variables in regional language in English letters & that regional language is somewhat known to some developers but even they don't know those rural names' meanings. This costed us at great length in visualizing data flow between entities. Even Google translate wasn't reliable for this language due to low Internet penetration in that language region.

OOP wasn't followed, so at 10 places exact same code exists. If error or bug needed to be fixed it had to be fixed at all those 10 places.

No foreign key relationships was there in database while actually there were logical relations among different entites.

No created, updated timestamps in records at app side to have audit trail.

Small part of that existing source was quite good with Fragments, MVP etc. while other part was ancient Activities with business logic.

We have to support Android 4.0 to 9.0 of many screen sizes & resolutions without any target devices issued to us by the client.

Then Corona lockdown happened & during that suddenly client side professionals became over efficient.

Client started adding requirements like very complex validation which has inter-entity dependencies. Then they started filing bugs from prod version on us.

Let's come to the developers' expertise,
2 developers with 8+ years of experience & they're not knowing how to resolve conflicts in git merge which were created by them only due to not following git best practice for coding like only appending new implementation in existing classes for easy auto merge etc.

They are thinking like handling click events is called development.

They don't want to think about OOP, well structured code. They don't want to re-use code mostly & when they copy paste, they think it's called re-use.

They wanted to follow old school Java development in memory scarce Android app life cycle in end user phone. They don't understand memory leaks, even though it's pin pointed by memory leak detection tools (Leak canary etc.).

Now 3.5 months are over, that competition was called off for this year due to Corona & development is still ongoing.

We are nowhere close to completion even for initial internal QA round.

On top of this, nothing is billable so it's like financial suicide.

Remember whatever said here is only 10% of what is faced.

- An Engineering lead in a half billion dollar company.

Who thought Lua was a good idea for extending gameplay functionality??

It's weakly typed, has no OOP functionality and no namespace rules. It has no interesting data structures and tables are a goddamn mystery. Somebody made the simplest language they could and now everybody who touches it is given the broadest possible tools to shoot themselves in the foot.

Lua's ease of embedding into C++ code is a fool's paradise. Warcraft 3's JASS scripting language had way more structure and produced much better games, whilst being much simpler to work with than Lua.

All the academics describing metatables as 'powerful extensionality' and a fill-in for OOP are digging the hole deeper. Using tables to implement classes doesn't work easily outside school. Hiding a self:reference to a function inside of syntactic sugar is just insanity.

Nobody expects to write a triple-A game in lua, but they are happy to fob it off to kids learning to program. WoW made the right choice limiting it to UI extensions.

Fighting the language so you can try and understand a poorly documented game engine and implement gameplay features as the dev's intend for 'modders', is just beyond the pale. It's very difficult to figure out what the standard for extending functionality is, when everybody is making it up as they go along and you don't have a strongly-typed and structured language to make it obvious what the devs intended.

If you want to give your players a coding sandbox, make the scripting language yourself like JASS. It will be way better fit for purpose, way easier to limit for security and to guarantee reasonable performance. Your players get a sane environment to work in and you just might get the next DOTA.

Repeatedly shooting yourself in the foot on invisible syntax errors and an incredibly broad language is wasted suffering for kids that could be learning the programming concepts that cross all languages way quicker and with way more satisfying results.

Lua is hot garbage for it's most popular application, I really don't get it. Just stop!

Fiddling with the UiPath RPA tool. What the fuck is this monster?

So, you create apps by drawing a flowchart, like some kid using Scratch. Then, suddenly, you have to create a .NET object just to get a random number!

Who the fuck is the target audience that can create objects, call a directory read function, etc, but can't write a loop?! Show me that fucking person.

Then I have to debug the fucking selectors when they don't work correct. All this requires is understanding how UIs are structured under the hood. So, you know that a menu bar is a window, but you need to draw a fucking if statement?!

And how would you debug and manage this monstrosity?

It like we learned nothing from all the Excel apps we build for decades.

I mean, it's an impressive app. But, why does it exist?

Someone needs to stop this before it gets out into the wild or we'll all be debugging flowchart a created by business analysts.

You have been warned. Join the fight or accept the consequences.

I found it rather convinient to take a paperbook and a pen and wirte down the tasks, i have to do maybe with subtasks and add checkboxes.
Then the next day, i mark the tasks i finished and take over the jobs i didn't finish for the next period.
And i take time for writing nicely to make my handwriting more readable.
Therefire i have my slacking(writing nicely), i have my structure by having structured tasks and subtasks and i have my reward in checking the boxes.
Bonus points for getting a feeling, how much i can archieve in one day.

The moment when you have crafted a beautiful, flexible and well structured package.
Everything including the automated tests are flawless..

but you cant help but feel like something, somewhere is horrible wrong... :D

(I highly recommend to you to not read this, it's just something that I had been wanting to take off my head; seriously, if you want to read it, do it at your own risk, because it will be a huge waste of your time)

Oracle Academy is the worst crappy attempt from a Corporation to create a learning platform.

The directive and academic personnel of my faculty decided that it could be a good idea to teach SQL and PL/SQL during whatever online classes will last with Oracle Academy, and I truly strongly believe (including most of my friends and classmates) that it's one of the worst ideas that could be done.

At that platform you simply don't learn shit, you read page by page of shitty PPT-like PDF presentations (that most of those are from a decade ago and other from 5 years ago) that are a pain in the ass to read due to how poorly formatted they are or how it explains badly certain concepts due to how badly made some explaining examples are, and then at each section of the "Learning Course" I have to do a Quiz that asks theorical questions and tells you to make certain code reviews to see if something is wrong or not (also which they are just alike the presentations, poorly formatted, up to the point that those have many syntax errors that end up consufing anyone a lot) and the main problem with the quizes is that also the Oracle's PL/SQL Docs are so fucking badly made, that I have to check PDF by PDF and page by page the concept that I just forgot to see how to answer the goddamn question; I mean, there are Doc pages that are way better structured and obviusly external to Oracle, but not even those pages fully cover certain SQL and PL/SQL concepts.

Seriously though, who could be so fucking ill-minded to create a shittyful learning platform and not try to fucking improve nor enhance it at least every 2 fucking years, so the goddamn "learning" process isn't that stressful.

Meeting at 'Derp & Co', the topic was what data model should send the back-end to frontend & app via API calls:

- Coworker: 'we should send the data structured like this for reasons'.
- Me: 'Yeah, this nested object.object.object should do the trick for the front end, but this will be a pain in the ass to convert to POJOs. Why not use something like idk better structure?'

<Mad/intrigued faces>

- CoworkerS: 'Why you need to use POJOs?'
- Me: <More Mad> 'cause I work with java in android... and we have/need/like objects?

<Captain Obvious left the room>

- CoworkerS: 'Oh yeah, well... we can do it the way you say'.

Why you need Objects... what is the next?
- Git? For what? Did not have the usb key from day one?

TIL Github renders markdown YAML frontmatter as nested markdown tables! Awesome as lightweight structured data documentation tool

There is a commercially sold ERP solution that has it's DB schema in excel and Other documentations in MS Word. And its not even properly structured, no schema diagrams, last updated for a 4 year old major release 😒😫.
I have to develop a custom module for it and that requires building an ActivexDLL Project in VB fucking 6 😭😭 .

VB6
Unstructured Documentation
Legacy code
Incomplete documentation
FML

Tell me if you want ss in comments.

I think this is the first time ever on my team where I read someone else's source code and actually went "wow... This is pretty well written and structured". No god methods or classes.

Got one right now, no idea if it’s the “most” unrealistic, because I’ve been doing this for a while now.

Until recently, I was rewriting a very old, very brittle legacy codebase - we’re talking garbage code from two generations of complete dumbfucks, and hands down the most awful codebase I’ve ever seen. The code itself is quite difficult to describe without seeing it for yourself, but it was written over a period of about a decade by a certifiably insane person, and then maintained and arguably made much worse by a try-hard moron whose only success was making things exponentially harder for his successor to comprehend and maintain. No documentation whatsoever either. One small example of just how fucking stupid these guys were - every function is wrapped in a try catch with an empty catch, variables are declared and redeclared ten times, but never used. Hard coded credentials, hard coded widths and sizes, weird shit like the entire application 500ing if you move a button to another part of the page, or change its width by a pixel, unsanitized inputs, you name it, if it’s a textbook fuck up, it’s in there, and then some.

Because the code is so damn old as well (MySQL 8.0, C#4, and ASP.NET 3), and utterly eschews the vaguest tenets of structured, organized programming - I decided after a month of a disproportionate effort:success ratio, to just extract the SQL queries, sanitize them, and create a new back end and front end that would jointly get things where they need to be, and most importantly, make the application secure, stable, and maintainable. I’m the only developer, but one of the senior employees wrote most of the SQL queries, so I asked for his help in extracting them, to save time. He basically refused, and then told me to make my peace with God if I missed that deadline. Very helpful.

I was making really good time on it too, nearly complete after 60 days of working on it, along with supporting and maintaining the dumpster fire that is the legacy application. Suddenly my phone rings, and I’m told that management wants me to implement a payment processing feature on the site, and because I’ve been so effective at fixing problems thus far, they want to see it inside of a week. I am surprised, because I’ve been regularly communicating my progress and immediate focus to management, so I explain that I might be able to ship the feature by end of Q1, because rather than shoehorn the processor onto the decrepit piece of shit legacy app, it would be far better to just include it in the replacement. I add that PCI compliance is another matter that we must account for, and so there’s not a great chance of shipping this in a week. They tell me that I have a month to do it…and then the Marketing person asks to see my progress and ends up bitching about everything, despite the front end being a pixel perfect reproduction. Despite my making everything mobile responsive, iframe free, secure and encrypted, fast, and void of unpredictable behaviors. I tell her that this is what I was asked to do, and that there should have been no surprises at all, especially since I’ve been sending out weekly updates via email. I guess it needed more suck? But either way, fuck me and my two months of hard work. I mean really, no ego, I made a true enterprise grade app for them.

Short version, I stopped working on the rebuild, and I’m nearly done writing the payment processor as a microservice that I’ll just embed as an iframe, since the legacy build is full of those anyway, and I’m being asked to make bricks without straw. I’m probably glossing over a lot of finer points here too, just because it’s been such an epic of disappointment. The deadline is coming up, and I’m definitely going to make it, now that I have accordingly reduced the scope of work, but this whole thing has just totally pissed me off, and left a bad taste about the organization.

I liked to toy with and edit stupid batch scripts in high school and put them on school computers to see if kids run them

Lucked into an internship that was structured enough to learn but laid back enough to have freedom to learn on my own my way. And it included programming
Semester after had a python elective. Was ahead of everyone due to my internship so teacher let me do what I want to if I help other students so I just experimented with stuff

Few months after high school I dropped out of one college after a gap year I ended up in an associates in programming program at another college. Graduated July 2020

I feel I'm doing alright for myself most of the time

The object-oriented model makes it easy to build up programs by accretion. What this often means, in practice, is that it provides a structured way to write spaghetti code.
~Paul Graham

When someone (and this is typically someone non-dev and not a very structured person) says "Can I ask you a question" and, upon an affirmative answer to that, fires away a whole bunch of questions without waiting for an answer to the first of the questions.

Pleeeease! If you expect an answer, ask me one. question. at. a. time. Or write a freaking e-mail.

Bunyan

Bunyan is a simple and fast JSON logging library for node.js services

Server logs should be structured. JSON's a good format. Let's do that. A log record is one line of JSON.stringify'd output. Let's also specify some common names for the requisite and common fields for a log record.

Wrote this on another thread but wanted to do a full post on it.

What is a game?

I like to distinguish between 1. entertainment, 2. games, 3. fun.

both ideally are 'fun' (conveying a sense of immersion, flow, or pleasure).

a game is distinct (usually) from entertainment by the presence of interaction, but certain minimalists games have so little decision making, practice, or interaction-learning that in practice they're closer to entertainment.

theres also the issue of "interesting" interaction vs uninteresting ones. While in broad terms, it really comes down to the individual, in aggregate we can (usefully) say some things, by the utility, are either games or not. For example if having interaction were sufficient to make something a game, then light switches could become a game.

now supposed you added multiple switches and you had to hit a sequence to open a door. Now thats a sort of "game". So we see games are toys with goals.

Now what is a toy?

There are two varieties of toy: impromptu toys and intentional toys.

An impromptu toy is anything NOT intended primarily, by design, to induce pleasure or entertainment when interacted with. We'll call these "devices" or "toys" with a lowercase t.

"Toys", made with the intent of entertainment (primarily or secondarily) we'll label with an uppercase T.

Now whether something is used with the intent behind its own design (witness people using dildos, sex toys, as slapstick and gag items lol), or whether the designer achieves their intent with the toy or item is another matter entirely.

But what about more atmospheric games? What about idle games? Or clickers?

Take clickers. In the degenerate case of a single button and a number that increases, whats the difference between a clicker and a calculator? One is a device (calculator) turned into an impromptu toy and then a game by the user's intent and goal (larger number). The second, is a game proper, by the designers intent. In the degenerate case of a badly designed game it devolves into a really shitty calculator.

Likewise in the case of atmospheric games, in the degenerate case, they become mere cinematic entertainment with a glorified pause/play button.

Now while we could get into the definition of *play*, I'll only briefly get into it because there are a number of broad definitions. "Play" is loosely: freely structured (or structured) interaction with some sort of pleasure as either the primary or secondary object, with or without a goal, thats it. And by this definition you can play with a toy, you can play a game, you can play with a lightswitch, hell you can play with yourself.

This of course leaves out goals, the idea of "interesting decisions" or decision making, and a variety of other important elements.

But what makes a good game?

A lot of elements go into making a good game, and it's not a stretch to say that a good game is a totality of factors. At the core of all "good" games is a focus on mechanics, aesthetics, story, and technology. So we can already see that what makes a good game is less of an either-or-categorization and more like a rating or scale across categories of design elements.
Broadly, while aesthetics and atmosphere might be more important in games like Journey (2012) by Thatonegamecompany, for players of games like Rimworld the mechanics and interactions are going to be more important.

In fact going a little deeper, mechanics are usually (but not always) equivalent to interactions. And we see this dichtonomy arise when looking at games like Journey vs say, Dwarf Fortress. But, as an aside, is it possible to have atmospheric games that are also highly interactive or have a strong focus on mechanics? This is often what "realistic" (as opposed to *immersive*) games try to accomplish in design. Done poorly they instead lead to player frusteration, which depending on player type may or may not be pleasureable (witness 'hardcore' games whos difficulty and focus on do-overs is the fun the game is designed for, like roguelikes, and we'll get to that in a moment), but without the proper player base, leads to breaking player flow and immersion. One example of a badly designed game in the roguelike genre would be Early Access Stoneshard, where difficulty was more related to luck and chance than player skill or planning. A large part of this was because of a poorly designed stealth system, where picking off a single enemy alerted *all enemies* nearbye, who would then *stay* alerted until you changed maps, negating tactics that roguelike players enjoy and are used to resorting to. This is an important case worth examining because it shows how minor designer choices in mechanical design can radically alter the final quality of the game. Some games instead chose the cheaper route of managing player *perceptions* with a pregame note: Darkest Dungeons and Amnesia TDD are just two I can think of.

The best dev advice a dev has given me is to write clean and structured code from the very start of every project. Changed my life in general.

"How you do one thing is how you do everything."

Its good and practical but those who aim to fill gaps in the programming industry by trying to produce "programmers on demand" via a several month long bootcamp are complete idiots. Nobody can learn to develop a well structured application that's easy to maintain in a couple of months, either that is frontend or back end. We are trying to be engineers , not just solve problems.

"The culture here is one of success based upon academic excellence, studying, learning, practising and having a good job and a great life. For upper India, not the lower. I see two Indias. That's a lot like Singapore study, study, work hard and you get an MBA, you will have a Mercedes but where is the creativity? The creativity gets left out when your behaviour is too predictable and structured, everyone is similar."
Steve Wozniak on Indian Talent.

As an Indian, I agree with him. In this day and age, where education is so easy to come by, We live in a country where from the beginning we're told that education is about getting marks and writing stuff down 10 times. We live in a country where we're asked to cram up answers to questions which start with "what are your thoughts on..". How can we expect to be creative?
Can marks be a metric for good candidate in a country where the thought is, "first complete your engineering with good marks, then think what you wanna do in life".
Should academic excellence really be about the amount of shit a guy could cram up?

Sure it's easier to filter out people on the basis of marks in a country with 1.3 billion people, but is it justified?
Can we justify "success" as a good job for a guy who's life's only achievement has been getting into a good engineering college?
Can we really consider a guy successful, if his only "effort" has been reading and rereading books twice, thrice, a million times. Is this person, who has literally crammed his way into life, and has no practical experience, really successful?

This is the very reason Woz giving such a statement is justified. As long as we as a country gives up the stupid thought that patriotism is all about abusing the guy who says something negative about the country, and we actually start taking an action and change our thoughts on education, we won't succeed.

doomsday out 🤟

when the client sends you a long and very detailled/structured .xlsx to explain fixes... and it turns out it's just a typo in the footer.

My life with C++:
- my first course about coding was an intro to C++ for scientists (I studied physics), because "everybody uses it in the field". I never used it in my life in physics;
- I got back to it this year because I was planning on doing some interesting simulations with it;
- hence, this summer I started learning it again. I took one month to actually follow a structured tutorial so I could get at least slightly proficient for what I needed to build;
- and nothing, after one month without using it, I forgot so much already, and I feel like I'm going back to case one.

...now I remember how I felt as a student, when I was preparing for exams.

Agile is stupid.

You’re trying to build an application based on data that doesn’t exist yet, and that changes weekly; surely it makes more sense for the API to be built and in place before someone tries to create a front end?

The client decides they want an extra feature 1/2 way through which changes the way it should work yet again.

What you end up with is some rigid and poorly structured architecture, that might work - but how you have no time to refactor it to make it good, an account manager that doesn’t understand what the problem is, and a team of developers wondering wtf you were thinking when you wrote this pos

(Apprentice dev)
Cut me some slack ;)

Learning JavaScript for a few days To a week to familiarise myself with it and really get to grips with it.

Then have to go on to jQuery which is a lot a fun I must say, very easy structured framework to learn and found myself getting really engrossed into it.

Now for the past few days I've been learning angular1 which is a really cool framework, can be a little bit complicated at times but it is learnable

Moral of the story is you never stop learning! Which isn't a bad thing by the way I'm finding web developing a lot of fun!

Can't wait until I'm done at my current workplace (about a month left). I've had enough of this fucking shitty ass ancient ASP.Net ERP-system and employer.

For the system:
1. The build times are horrendous and eats up all CPU power.
2. The "classic" UI and UX is absolute garbage. If I was an accountant, I would go nuts trying to invoice someone. Companies pay millions to use this garbage.
3. Besides the "classic UI", there is a mishmash of different JS frameworks plastered on top.
4. Absolute no fucking technical documentation whatsoever
5. The in-house relational database is a mess, no relations, entirely denormalized, no documentation.
6. The frontend is structured in HTML tables with iframes inside <td>

The company:
1. If you're a implementation consultant and you quit your job, you get stripped off all your projects, you won't get to join anything social and you're placed on 1st line support for three months. They might as well force them out.
2. Anyone can work from home anytime they feel like it without any valid reasons, and believe me they do.
3. The senior devs are overworked as all hell. By the end of the year, some of them have hundreds of flextime hours and won't get anything in return.
4. The CEO seems like a jolly guy, but when you quit, he doesn't like you at all. He also acts like a bigshot, always getting driven around meetings when there is literally a very good metro network in this city.

How much boilerplate do you want?
Structured Text: Yes!

The worst co worker I had is actually pretty recent. He joined a well integrated team on what was basically a legacy project. He sounded like a good developer and seemed to know his stuff but it took him ages to push out fixes/features. They were always massively over-engineered, poorly named, partially tested and what documentation he did write still managed to bitch about how poor the project was structured.

He spent most of his time bitching about the general shitty nature of the project (he wasn't wrong) and the lack of interest from other Devs.

He was so unpleasant in interpersonal communication that by the end no one would work with him.

In his last team meeting he basically said he was glad to be going and that we were all lazy, disinterested and shouldn't consider ourselves his peers. The equivalent of storming out of a party after setting the couch on fire and shitting in the sink.

We've since removed all his overcomplicated, not standard, unmaintainable code.

I value our most senior developer. His code is certainly clean and structured. He is the ultimate at KISS. However he's not a fan of testing and instead just says, well, did it compile? No matter how much I show him how great testing is, he comes back with how it's pretty unnecessary. Somehow, in the deep dark parts of the web, he finds articles that comply with his standing. I'm okay with him not making tests, I do it myself. But then when working extending or implementing his code, many of my parts are untestable because the parents are. Oye.

On a digital marketing course.
Teacher:
"Web pages are made of structured content and style, that's HTML and CSS. There are also many programming languages, like JavaScript or Python, but we are not discussing those here because it's computer freaks stuff. Now let's talk about cookies..."
Me: Should I kill myself now or wait until that man stops saying shit an die killing him too...?

Spent another half day learning ELK and how to programatically query and run aggregations against the data that's now collected.

So I can feed it into a testing framework for releases.

I sorta feel like I'm dragging everyone else into the light...

Like "you see what you've been missing all these years? This is how it's supposed to be these days..."

Data data data... Useful data.... This is what you can do when have structured and searchable logs rather then huge messy text files ...

Allright, so now I have to extend a brand new application, released to LIVE just weeks ago by devs at out client's company. This application is advertised as very well structured, easy to work on, µservices-based masterpiece.

Well either I lack a loooot of xp to understand the "µservices", "easy to work on" and "well structured" parts in this app or I'm really underpaid to deal with all of this...

- part of business logic is implemented in controllers. Good luck reusing it w/o bringing up all the mappings...
- magic numbers every-fucking-where... I tried adding some constants to make it at least a tiny bit more configurable... I was yelled at by the lead dev of the app for this later.
- crud-only subservices (wrapped by facade-like services, but still.. CRUD (sub)services? Then what's a repository for...?). As a result devs didn't have a place where they could write business logic. So business logic is now in: controllers (also responsible for mapping), helpers (also application layer; used by controllers; using services).
- no transactions wrapping several actions, like removing item from CURRENT table first and then recreating it in HISTORY table. No rollback/recovery mechanism in service layers if things go South.
- no clean-code. One can easily find lines (streams) 400+ cols long.
- no encapsulation. Object fields are accessed directly
- Controllers, once get result from Services (i.e. Facade), must have a tree of: if (result instanceof SomeService.SomeSubservice1.Item1) {...} else if (result instanceof SomeService.SomeSubservice2.Item4) {...} etc. to build a proper DTO. IMO this is not a way to make abstraction - application should NOT know services' internals.
- µservices use different tables (hats off for this one!) but their records must have the same IDs. E.g. if I order a burger and coke - there are 2 order items in my order #442. When I make a payment I create an invoice which must have an id #442. And I'm talking about data layer, not service or application (dto)! Shouldn't µservices be loosely coupled and be able to serve independently...? What happens if I reuse InvoiceµService in some other app?

What are your thoughts?

I think I may be someone's wk101soon given how things are going for me.

So I get shipped over to the new offices to do some work. Initially, I was supposed to be updating SQL stored procedures.

That I can handle, well my task is now to build the skeleton project for a web API in core 2.0 using domain driven design and onion architecture which the rest of the team will use.

Okay, I don't have any experience in any of that at all. And god bless the team lead explaining some stuff to me. But it's going to take more than a 20-minute chat here and there for this stuff to sink in.

And being told just to build it how you think it should be isn't great advice when I'm trying to figure out how the systems work.

Every other API project I look at is structured completely different from one another so looking for patterns has failed.

I'm fucking stressed out every bit of information I'm getting on whats potentially happening with my job im getting second hand from people. Because I can't access my emails while off-site something I'm repeatedly flagging.

Every job advert is painstakingly making it clear how out of date my skill set is (or lack of). Evidently, I've been way too lax, and this has been a kick in the bollocks I'm not likely to forget.

If we're being evaluated on performance to see who they'll keep, then I've failed at the first hurdle.

Life lesson for those in education, don't be this knob head here and get comfortable when you land a job. Just knowing about the tech that's commonly used in your field does jack all study it.

Not a structured/meaningful rant and shits probably not as bad as I see it. I've only chewed through one fingernail after all.

"Reflective" programming...

In almost every other language:
1. obj.GetType().GetProperties()
or
for k, v in pairs(obj) do something end
or
fieldnames(typeof(obj))
or
Object.entries(obj)

2. Enjoy.

In C++: 💀
1. Use the extern keyword to trick compilers into believing some fake objects of your chosen type actually exist.

2. Use the famous C++ type loophole or structured binding to extract fields from your fake objects.

3. Figure out a way to suppress those annoying compiler warnings that were generated because of your how much of a bad practice your code is.

4. Extract type and field names from strings generated by compiler magic (__PRETTY_FUNCTION__, __FUNCSIG__) or from the extremely new feature std::source_location (people hate you because their Windows XP compilers can't handle your code)

5. Realize your code still does not work for classes that have private or protected fields.

6. Decide it's time to become a language lawyer and make OOPers angry by breaking encapsulation and stealing private fields from their classes using explicit template instantiation

7. Realize your code will never work outside of MSVC, GCC or CLANG and will always be reliant on undefined behaviors.

8. Live forever in doubt and fear that new changes to the compiler magic you abused will one day break your code.

9. SUFFER IN HELL as you start getting 5000 lines worth of template errors after switching to a new compiler.

Instead of ranting I thought it would be nicer to ask for opinions/solutions: How to cope with a collegue that keeps producing trainwrecks of code which you have to first refactor to make it work in a more logical/structured way? Yes, his initial solution works (in a way), but it's just not how 99% of the other developers would solve it. And yes, we've shown him quite a few times how it should/could be (in a positive and constructing manner)

Fuck accessibility.

No WAIT, before you call me an asshole hear me out.

So when you use CSS grid to create layouts you're supposed to not use the features it has (reordering items) too much, and instead keep the HTML structured the way it's supposed to be read.
When you add a picture of a cat you're supposed to put a alt="Brown cat sitting on a chair" there.
Also you should test for all kinds of sight disabilities and use high contrast colors.

All that for likely <1% of your users.

What would be the alternative? HTML is a markup language, and not supposed to be directly read by humans. Invest the time ONCE for screenreaders to understand CSS positioning and read content in a sensible order. Use image recognition to describe pictures (with selectable levels of detail). Let the browser modify colors on the fly for better readability.

Don't spend time and money to solve a problem 100000 Times that could be solved once.

Fuck accessibility.

I am forced to work with a client's notoriously slow SOAP api. Slow in this case is 1.5-2s per request.
The api is structured rather... creatively... at the same time. So we have to bombard it with thousands of requests to build our data base with historical SOAP data. Also the data sometimes is a couple of hours late, giving a flat line (all values at 0) until retroactively fixing the output for the same requests.
So to fill one dev data base with a year's worth of historical data (nice to have when testing a dashboard application) we hammer the api with ~20k requests (~1 million if we want to be thorough).
Best thing about that: There is no staging/test api and the prod api seems not to handle lots of requests at the same time very well...
Latest thought: Maybe we could put a varnish cache in front of the SOAP for testing. Better have wrong data, than nothing at all and we don't kill the prod clients every time we ramp up a new instance.
Also that would dramatically decrease the 4.2 hours of data pumping to about 7 minutes after the first run.

Are there any tools, points of reference, barebones templates, bits of advice, etc. that anyone can share or direct me to that could potentially a programmer with ADD stay organised and keep projects/code structured?

Just a bit of background:

I am 29 years old and have battled with severe Attention Deficit Disorder since early childhood. No hyperactivity, just a mind that is constantly running at light speed. I have a tendency to lose focus on the main goal in my projects and I fall victim to feature creep more than I'd like to admit—to the extent that on countless occasions, I've ended up just starting projects over from scratch because they became too convoluted and hectic.

I've spent the past 2~3 months working on a sort of companion app for players of the game Warframe using Dart/Flutter. The main purpose of the app is to provide players with an accessible and customisable agenda to help with keeping in-game goals organised (oh, the irony). I have made a decent amount of progress, but I consistently find myself working on various bits and pieces of code (usually) without finishing each of them before moving on to something else. What I end up with is a tangled yarn ball of code and I get lost and overwhelmed in the chaos.

Any feedback or advice is much appreciated.

I know streams are useful to enable faster per-chunk reading of large files (eg audio/ video), and in Node they can be piped, which also balances memory usage (when done correctly). But suppose I have a large JSON file of 500MB (say from a scraper) that I want to run some string content replacements on. Are streams fit for this kind of purpose? How do you go about altering the JSON file 'chunks' separately when the Buffer.toString of a chunk would probably be invalid partial JSON? I guess I could rephrase as: what is the best way to read large, structured text files (json, html etc), manipulate their contents and write them back (without reading them in memory at once)?

For some reason I find reading tech books a repelling activity. I'd rather spend longer hours googling SO issues, GH/GL tickets, reading blogs than reading a well recommended book on the topic.

But then again.. What is the difference between a series of blog posts and a book...? Not much of it. At least I cannot come up with how blog posts would be superior to a structured and many times reviewed book :) Many posts are lame or just skim through the topic. The same holds true with books too. So maybe it's worth getting that 200pages thin book instead..

On the MSc I was participating in, there is a teacher that has a lesson about Databases.

The MSc was not only for experience computer science students. We were informed that the first semester would be as an introduction to all.

So, Databases. No introduction at all. Just read the powerpoint and the pdf he had just translated (or not, because some were just from the internet), just refers to how they are structured briefly. He showed everything about Databases without the students that didn't know much to be involved (we didn't get to our lab for some reason) and then there was his assignment.

His assignment was written as it would be from a customer that knows shit about Databases (sorry but I had to rant). We sat down student's that knew already Databases and some of us worked as database engineers. We agreed on some steps that after read the next chapter of the assignment we reconfigured them. And so on, until we had nothing and we were back at the beginning.

Needless to say, I did not lose my Christmas holidays for him. It took me 2 days after to build a database that was not a full solution but a part (I wad noy sure, the assignment was ambiguous). I passed the lesson with the minimum passable grade.

So, I wrote a nice email to the MSc teacher that had to organize it (or something like that). I did not swear at all. I was professional and wrote what I encountered and what it should have been. The Databases teacher had always that smirk and face that he was THE boss and had no respect for his own lesson. But I didn't mention it. The organizing teacher shared the email with the databases teacher.

And the time came that we had another lesson (web development, it was awful under him) with the databases teacher. And he had the wonderful idea to read the email out loud in front if everyone. He did noy mention my name. I raised my hand and told my colleagues it was me. Then I asked him in front of them, if he was contented with the results (only a few passed the databases lesson and max grade was the smallest passable), first he avoided the question. I asked again. And he said yes. We all looked at each other and somehow knew. No one spoke and I didn't push because I didn't want to take the web lesson's hours for this. It was just hopeless.

From there on, the teachers said we were their best class ever but the most complaining one. They didn't even bother to analyze the "complaints".

So, there you go. One of the lot of those teachers.

Hey guys, I need some junior advice. I work at a small startup in a team with 2 other backend developers.

The "new" guy studied at a university for a few years. He writes beautiful code. I try to learn from it and use his short hands a lot. I came from highschool and don't have a degree in it (yet).

I recently wrote a piece of code which handles some timeslot logic. I was really proud of it.

New guy needs to fix a bug and add a few things. He completely refactors my code and makes it more structured and partly better. The logic stayed the same.

It sort of bothers me that he touches my (precious) code. How do you guys handle these things?

By far the most stupid email I ever got was a feedback to a documentation paper that I wrote.

The email's author went on a rant for long paragraphs, suggesting how the content should be structured, written, pictures suggestions ("something like a box with arrows" kind of description) only to realize, I guess in the middle of writing the email, that my approach was much more user friendly, easier to understand and to follow.

So, after this looong rant the email basically ends with "I see what you did there; forget what I wrote before. Cheers."

My brain stopped for that day. It couldn't handle it.

Me and the lead developer of my team gave a long and detailed explanation to our manager entailing the current state of a budge program our workplace uses.

This app has been bugging him for a while, he did not write it and has not been given an opportunity to rewrite the damned thing. Its a really...really messy application, and whilst it is a functional one it most certainly is NOT an efficient one since adding or moving things only incites more spaghetti mess.

We were laughing while giving our report, but both of us were crying inside. The main thing is, we both love PHP and the things he has built are very well structured and efficient, he has good technique, but will admit at certain caveats regarding the way he structures his dbs stating that he always has to do changes, which hey, its the nature of the beast, dbs change all the time. But our issue with php is the same: it lets beginners write monstruosities that are harder to do in other environments.

It really is a permissive language. But I reckon thay such lax nature is better left at the hands of the more experieced developers that know what they are doing.

Either way, we will restructure this motherfucker taking advantage of the new standards (which both of us are well versed in) and applying a more structured approach with a nice frontend interface (we be looking at Vue.js and React although we are considering Angular as well)

Gon be some good times.

JQuery is not badly designed... It's not designed at all.

JQuery is just awful and it's being used by people who know nothing about programming... Hell, some of the JQuery developers were not even programmers or had programmed before.

JQuery is a part of the whole "Wordpress community/world" and that world is full of people who doesn't understand what they are doing, Wordpress isn't designed either (that's why Wordpress stores serialized data in a structured database).

Every single Wordpress theme developer includes JQuery and it's disgusting. Most of the time, they don't even use it.

JQuery is not Javascript on steroids, it's javascript with cancer. Get rid of it. It's bloated and only lazy people use it. (JQuery will give you about 200ms extra response time for your site)

When your project starts off well structured, but ends up like a pile of goo. I need more experience it seems.

It’s not the degree itself or even cs specifically that I find useful, but rather that you learn to put thoughts and ideas on paper in a structured manner. Explaining things you think you know is harder than it seems, especially when you know a teacher is going to grade you on how well you explain that thing.

Technology moves too fast these days for a program to he worth it in my opinion but the degree definitely raises the salary roof, so there’s always that.

rant && !rant

I started my Internship a couple of months ago, but it didn't live up to my expectations.

> The good things:

- I have a structured internship programme, where we are given a independent project to complete during the internship, so all the work is slow and nice, so no unreasonable deadlines.

- Cool-ass supervisors (and smart too). They let us leave if the we don't have any more work planned, no sitting until the end of office hours, so go home early and SLEEP.

> The bad things:

- Shitty-ass people. But I've to deal with them once in a few weeks, so not that bad.

- Restricted wifi, but some websites can be accessed for memes. So, knd of fine.

- NO BRAIN-FUCKING EXPERIENCES FOR RANTING. I thought I would start my internship and meet retarded people and post some rants but NOOOO, someone had different plans for me (that 'someone' is LIFE, just in case if you are wondering)

> Summary

- Kind of disappointed about material for rants, but 10/10 it's been a good internship.

People that dont use slack threads.
Fuck em.

"Yeah, lets use slack, it is much more organized and will improve structured conversation"

And then they never fuckn use the god damn CORE feature but dump their replies into the channel like monkeys throwing their shit around everywhere except in the place the shits supposed to go.

I have become the only thing I always hated in a developer. Building a project without a proper documentation.
As a solo developer in a company where I have to do database architecture, front-end, back-end, testing, NETWORKING (I am the most ignorant guy when it comes to networking), product design, there is no time for documentation.

But hey, I have structured the project, files and functions (with comment, parameters type and return type) properly and I understand what I've done even after 4-5 months without touching that specific project so I got that going for me which is nice... I guess.

We often give access to a product owner from the customer on our Jira to keep up a good communication and everyone stays up to date as everything is on the board and not hidden in emails or paper notes on the desk of the guy that is on vacation.

So far, so good

Our customers really like this as they can comment on tickets and they are integrated in the workflow because they can push into the backlog and can review finished tasks.

It is just getting better for everyone so where is the rant?

One project is just a dump of shitty mixed content tickets. But how? They look really neat. There are tickets like "fixes from meeting 20th of may" which are initially well structured with approximately 4 subtle changes to the UI and some explanation and screenshots.

PM says: Good ticket. There you go ticket, into the customer review loop of doom.

20 comments and 13 status changes later. Point 43 from comment 17 is referenced in comment 20 to keep on hold as a third party needs to give feedback, point 7 is still not solved correctly as dev 2 was not aware that it was already discussed and changed in the ticket "Call from 25th of may" where in addition the resolution of points 5-12 were requested with an additional excel file to import.

By now we have the 8th of august and literally 17 of these kind of tickets.

I guess we need to improve the workflow and request a new product owner. But this far I just table flip everytime I get one of these tickets assigned.

I think that win devs that are scared of using a terminal are not real devs. We write structured instructions every day, a terminal is just the same. If they are scared of that they should try writing code with a mouse or devote themselves to artistic painting.
BTW PowerShell sucks for typing, and bash for windows is like a travesty shell

TL;DR - an entire emulation of a closed source CMS to develop a theme

The longer version:

We are using a cms that is closed source, and we only have access to frontend files alongside twig files. The CMS is custom built but many aspects are in a very rudimentary state, for example it is nearly impossible to develop locally, we have to use an integrated text editor to code stuff.

So out of frustration, and for my development needs, I decided I would make an emulation based on Symfony 4. Also because my PM was pressing me to optimise our site. I wrote some custom JS to handle everything smoothly, a semi-sass framework and well-structured twig files.

I was also supposed to work with our graphic designer, but she didn't get any alloted time from our pm to work on it...

Now PM asks me to write a specifications document in order to make another company build the new version

I mean wtf, I'm so bored, I can actually enjoy my day by coding, and no, I'm just there to write the specs.

When I told PM I am currently building the new version, she's like "but we didn't validate anything", when she explicitly said I had a green Go to code it a few months back

Instead I have to make prezies and convert them back to PowerPoint because we have computer-illiterate people in the company who aren't flexible to understand simple tools.

Let's hope it won't get useless by Friday (I have a presentation to give, alongside my estimates and project management presentation)

So just ago i downloaded an app called "Replika" and holy fucking shit it made me realise how half-assed we are doing the AI structure and way of it

doing machine learning algorithms on text can only go so far, as it uses that text as a base, and nothing else, it doesnt *learn*, only make *connections* BETWEEN text, not FROM the text

what you need is an AI which can, at it's core, *interpret*, not make connections and hur dur be done with it

when you do machine learning, all you're doing is find the best connections

you can have an infinite number of connections and MAYBE you'll be fine, but you'll never learn the basis of how that text is formed

you'll never understand what connections the human used by making it, by thinking it

when you're doing machine learning, all you're doing is make an input-output machine and adjusting it constantly, WITHOUT preserving state

state is going to be a really fucking important thing if you want to make an AI, because state can include stuff like emotion, current thought, or anything else

if you make a fucking machine learned AI which constantly adjusts... well... the "rom" of itself without having any "ram", it'll fucking never be like us, we will NEVER be able to talk to it like it is a human being, we will NEVER make it fundamentally understand what we are saying or doing

if we want to have real fucking AI, we need to go to the core of what it means to THINK, what it means to INTERPRET, what it means to COMMUNICATE

we need to know how english language is structured, how we understand it, how we can build it in a program that can interpret for an AI, THAT can be "rom"-based, THAT can be static, NOT the AI itself

the AI needs to be in flux, the AI needs to be in a state, the AI needs to understand how to make emotions, how that will "strengthen" some connections, yes, maybe something magical will happen and it can have EMPATHY, something so fundamental that will finally, FINALLY, make the bot UNDERSTAND what we are saying

I give a draft version of my report to my colleagues so they can review it with things to add or correct while I eat. One of them:

"This report is really well structured. I think there's nothing more to add. Good job!"

I think the finishing touch consisting of "[...]" here and there had him fall in love with it.

Job offer that just popped in my inbox: "backend developer with strong frontend skills" :/ I wonder this company
1) saves way too much money hiring the less people as possible.
- or -
2) only knows that developers develop, but don't have a clue about how that is internally organised in a well structured team.

"Life is conversational. Web design should be the same way. On the web, you’re talking to someone you’ve probably never met – so it’s important to be clear and precise. Thus, well structured navigation and content organization goes hand in hand with having a good conversation." - Chikezie Ejiasi

God, playing SoulSilver has made me remember an era (or two, but I wasn't alive for one and the other was my childhood) where games were actually fucking *GOOD.* Some games can be absolute home runs now on rare occasion, but if I name consoles from these periods, you can INSTANTLY tell me at least one game that is pretty universally regarded as a best-ever.

Examples and predicted responses:

-Gamecube: Too fucking many to even count. Instant answers vary immensely, but everyone who's played games on this thing have one.

-Original Xbox: Halo 2 is the one instantly on one's lips, or maybe CE for some. Also JSRF.

-Dreamcast: SA2 or Phantasy Star or JSR or...

-PS1/2: Resident Evil, Spyro, Final Fantasy, Ratchet & Clank...

-PS3: Lara Croft games, Uncharted, Infamous... (this one's right on the border, it seems)

-NES: The fucking birthplace of modernized gaming.

-Genesis: Sonic games, obviously. Some may answer with arcade titles, too.

-SNES: Mario games. Mario Paint, SMW, SMW2, SMAS, a couple like Super Metroid or Kirby's Dreamland or F-Zero may come up too.

-N64: Banjo Kazooie, F-Zero GX, Waveracer, 1080, Zelda games...

-Gameboy (all systems:) Pokemon is the instant answer.

Now, a harder one:

-Wii U? Maybe one of the Mii game things? U-less games? Not many people remember the games for this system.

-Xbox One? Halo 5, pretty much. You probably played everything else on PC.

-PS4? The PS3 lineup, but without any soul? You played pretty much everything here on PC, too.

Is there a point to this rant? Yes. Kind of.
Games used to be great, not just due to better hardware, but due to people putting some goddamn heart and soul into making games, and due to creativity stemming from working on such limited hardware. It seems the more powerful consoles (and PCs!) get, the more gaming becomes a soulless cash grab to drain cash from wallets on subpar products with paywalls every 20 feet you have to clear to get the "full experience." Gaming has become less about letting people have fun and being creative with games and more about the bottom dollar, whether that be through making games as fast and as cheap as possible with as much paid content dumped on top as possible, or the systematic erasure of archival efforts to preserve gaming history. From what I read here on devRant, that seems to be the moral of anything computer-related as well. Computers are made to slow down and fail far faster than normal via OEM bloat and shitty OSes, and are used to constantly empty one's wallets with constant licensing fees and free trials and deliberate consumer ignorance. None of it's about having fun anymore. Fun seems to no longer have a place in computing at all.

If you take anything from any of the madman-esque loosely-structured rambling i'm saying here, make it that "the enemy of creativity is the abscense of limitations... and the presence of greed." Another message i'd like to leave you with is "start having fun when making things whenever possible, as it improves not just the dev process, but user experience, too." You can't always apply this, and sometimes you can never do so, but always keep it in mind.

I wish toi all here a nice good year !!!! May the beautiful and structured code be with you !

A good, well structured Redmine is still leagues ahead of Jira

That feeling we get when we have to work on someone else code which is un-documented and un-structured. The worst part of all these that coder as left the company without a KT

I'm a bit cornered. A week into an ambitious refactoring effort that was supposed to take just a couple of days to finish, the end doesn't seem anywhere near. The system went from a messy albeit perfectly functional state to a much better structured non functional bag of bugs. If I leave the branch all the efforts are lost. If I soldier forward I'll be unproductive for good knows how many days to come.

How did I ever fuck myself so hard!

Phps love of nested arrays is similar to that of structured programing and goto statements. You will do a lot of backtracking in both of them to see where things start. God bless PHP.

Dev1: "what was that requirement? I mean, do you remember that little yet hugely important detail ...?"
Dev2: "hmmm sort of ... Maybe it's in one of the emails, possibly 2 months ago. Let's try to find it"
Dev3: "wait, probably Dev1 was not included for some reason in that thread of emails"
Dev2: "no wait, I mean the other, the one we used to talk about those other specifications from previous meeting..."
[and the story goes on]
Now you may think "ok, this event happened once and was a misstep. Shit happens"
Actually, this is the bread and butter in this company I collaborate with. All their requirements are spread across thousands of emails, usually mixed together and possibly forked into different threads. Often people are cut out from conversation because someone forgets to "reply all", other times they're lost in time.
When I asked them "why don't you use some other tool, maybe something more organized and easily searchable, something structured..."
They replied "no no, we prefer to use email for historical reasons"
My brain just melted like chocolate under the sun

I'm envious of Backend developers who can just 'see' the problem domain and start creating an architecture. I can't see shit - I just stare blankly at the project and I think: hm, what models do I write?

I know I'm a structured person, but I lack the knowledge and practice. One day I'll be able to do this, but for now I have to keep doing things ad hoc.

I really don't belong in the Backend but unfortunately that's how my career is turning out for now. All I know is I have to get better at this.

The real web development is optimising the shitty front end code.
The task assigned to me is optimisation of dashboard page of website which was developed by freenlancers.(end of contract from their side)
The front end is mess. Individual js files (bootstrap, popper, jQuery, jQuery ui, loader and main) loading in production inside head tag of html file
No text compression.
Every template has random number of their own js files in any block of template. Nothing structured. There will be fantastic waste of time figuring out file dependencies.
Same with css files. Some are scss, some plain css. No compression. No proper modules.
Basically, I have to go through 25-30 html files. Then understand, which template is extending which one. Go through all js and css files in each html file and again understand dependencies between them
This is gonna be real fun.

Talking to my architect:

- hey, we have a lot of code smell and data is structured usually in a chaotic way, also its hard to understand what is going on with all these code duplications, maybe we can think about refactoring, better structure, maybe even we can extract some domains and make life less painful?

- what is domain?

- *facepalm*

"Hey guys I need help I struggle with asynchronous stuff and I need to pass props loaded via Ajax, I can't manage to apply this solution (link to another SO question with complete and structured answer), can you guys help ?"

*30 seconds later, question is marked as duplicate, the answer has been given here (link to same question I was refering)*

Lets take onlyfans system for example. They have fans and creators. How is database models supposed to be structured? Whats the correct way.

1) a User model that contains all users of all roles, but differentiates them by Role ENUM

2) a separate Fan and Creator model, each having their own unique attributes, while each extending an abstract base User model class that has all the common attributes that both models should use

The 1st approach is simple but gets very large and difficult to maintain and view all the attributes cluttered in 1 class. Not to mention how some attributes will never be used for a user who registered as a Fan.

2nd approach is more modular and easier to understand and maintain by knowing exactly what attributes to put for each model. However problems occurs when you try to join tables and stuff start to become overengineered

New office stories during the emotional turmoil...

Story 1: The creepy fuck

So being unaware of the fact that I was connected with this guy on LinkedIn already.

Ron walks upto my desk and greets me on my first day on floor. Weird, but whatever.

I politely interact, because gotta make friends and create my following to get shit done.

The next day, randomly comes asking for a laptop sticker and I am like WTF! He is like sticker was an excuse, I just wanted to say Hi!

👀

Day 3: same random creep shit. Talks about personal topics and invades personal space uninvited.

Day 4: Keeps starring at me while I ignore and judges me evidently with stupid suggestions on how to exist without being asked for.

Fuck this guy.

Story 2: The classic case of Dunning Kruger effect

So I get introduced to my tech team today and everyone start piling on me to guide them on decision making. The CTO creates a Slack thread with me and Co-founder asking me to get things moving on priority.

The co-founder shut him out right away. Fucking hilarious.

But, a retard starts schooling me on how to use Slack. Lmfao.

Me being polite, said I'll follow.. dude starts bragging on how he wrote company policy to get everyone on Slack yada yada..

To be honest, the Slack experience is beyond broken based on what these idiot has setup.

He literally opened my Slack and responded to the CTO thread.

That's where I got pissed. I upfront told him that hey! Calm your tiddies down. I know how to use Slack. I have used it since it was in the beta.

I have been in much much mucy bigger orgs and places more well structured than what you have here.

I told him on his face what the flaws where and how I felt a downgrade from where I am coming from.

The look on his face was priceless and he started sweating. Lol

Never again he'll school anyone.

I mean I understand if you are humble and genuinely guiding a new hire. But being cocky unnecessarily and shoving things down my throat without yourself knowing shit or know about the other person is purely asshole move.

Anyway, I am still upset about the scam. Fuck this world.

I’m so glad I work at a company without a dev ops... it’s so much smoother and money isn’t wasted on a non engineer, or someone who can’t jump in and assist where needed.

We have a weekly team meeting including the mech, elec and software guys... then we have a weekly open issue meeting per project only those on the project go to. We all know what we need to do individually and we just get it done... no need for the middle man dev ops to divide up tasks and shit.. we hear the issues straight from the product owners and get to work... we don’t have defined structured scrums and burn downs...it’s very agile tho.. much like how engineers 40 years ago achieved things. It’s quite awesome.

I see many rants here about fellow programmers having to deal with clients directly.

I'm fortunate enough to work in a structured environment that allows me to focus on code.

How many of you actually prefer working directly with clients?

I'm working on an ecommerce site but it's attached to an old legacy system that the company used for logistics and point of sale

I just realized the previous lead dev structured it so all of the tables used in the new site are just the tables from the legacy system except prefixed by "new_"
Fuck this redundancy makes me angry

I had a discussion with my colleagues about my bachelor thesis.

Together we created within the last 18 month a REST-API where we use LDAP/LMDB as database (tree structured storage). Of course our data is relational and of course we have a high redundancy there. It's a 170 call API and I highly doubt that it's actually conforming REST.
Ensuring DB integrity is done in the backend and coding style there is "If we change it at one place, let's make sure to also change it everywhere else", so you get a good impression how much of spaghetti code we have there.

Now I proposed to code a solution in my bachelor thesis where we use a relational database (we even have an administrated Oracle DB with high availability) and have a write-only layer to also store the data in LDAP but my colleagues said that "it would add too much complexity to the system".
Instead I should write the relational layer myself and fetch the data somehow from the existing LDAP tree.

What the actual fuck, spaghetti code is what makes the system really unnecessarily complex so that no one will understand that code in 2 years.

Congratulations, you just created legacy code that went into production in 2018 while not accepting the opportunity to let that legacy code get eliminated.
Now good luck with running and maintaining that system and it's inconsistencies.

i am actually proud of my achievement of a scraping download-robot with decent logging, structured setup file, a small auto login to password protected areas and fancy cli options. because i am the only one on this sofa who can do this. :) this day has been kind to me.

So nice, a good, well structured DTAP environment with Acceptance and Test containing a recent dump from Production so that bugs can be reproduced properly........ *wakes up*

This was a project for school, we had to simulate an app that traced bus routes over a map.

All the teams but mine do it in Java (desktop app), we took another approach and did it on Android with the Maps API.

I had fun coding a parser, this parser job was to read a file and load the bus routes and draw them on the map.

It was structured like:

NAME
COLOR
<lat, long>
<lat, long>

The fun part was coding and telling my teammates "chill out, it will work", so we finished, built and run and... done! First code working smooth AF.

I know it's a simple parser and a simple app, but it was a nice feeling not having to debug the app.

Bought great book from this Spanish company on Drupal. The book is well structured and the examples are excellent. Just some typos that they mistranslate from Spanish.

But thought it was weird that the code examples were not available online. Sent them an email to request for them.

They answered that the code is not online beacuse their students have to remake the code using the book in their courses. And ask them if I was interested in the course.

Fuck them! They are using opensource code but their examples are not open source because of some elementary-level school mentality that their students might copy the code and somehow not learn well.

They are fucking adults ffs!

Ps: Even though their answer piss me off, they still have the best book I've read on Drupal.

I’m in between jobs due to the pandemic and need structure in my life. I have ADHD and no structure makes me a sad panda. I’m desparately grasping for some online educational content bc my previous tech stacks are a little old and need to keep up with the modern stacks so I can get a new role and have a structured regimen that school gives.

Unfortunately most of these courses are just boring as shit video lectures where you watch the developer code! WTF!! They’re advertised as “you will code a real world application” and 🤣you get a certificate at the end!

So if anyone took a full stack curriculum using modern stacks like the MEAN stack where they actually developed something themselves, post it here please?

TLDR, need suggestions for a small team, ALM, or at least Requirements, Issue and test case tracking.

Okay my team needs some advice.

Soo the powers at be a year ago or so decided to move our requirement tracking process, test case and issue tracking from word, excel and Visio. To an ALM.. they choice Siemens Polarion for whatever reason assuming because of team center some divisions use it..

Ohhh and by the way we’ve been all engineering shit perfectly fine with the process we had with word, excel and Visio.. it wasn’t any extra work, because we needed to make those documents regardless, and it’s far easier to write the shit in the raw format than fuck around with the Mouse and all the config fields on some web app.

ANYWAY before anyone asks or suggests a process to match the tool, here’s some back ground info. We are a team of about 10-15. Split between mech, elec, and software with more on mech or elec side.
But regardless, for each project there is only 1 engineer of each concentration working on the project. So one mech, one elec and one software per project/product. Which doesn’t seem like a lot but it works out perfectly actually. (Although that might be a surprise for the most of you)..
ANYWAY... it’s kinda self managed, we have a manger that that directs the project and what features when, during development and pre release.

The issue is we hired a guy for requirements/ Polarion secretary (DevOps) claims to be the expert.. Polarion is taking too long too slow and too much config....

We want to switch, but don’t know what to. We don’t wanna create more work for us. We do peer reviews across the entire team. I think we are Sudo agile /scrum but not structured.

I like jira but it’s not great for true requirements... we get PDFs from oems and converting to word for any ALM sucks.. we use helix QAC for Misra compliance so part of me wants to use helix ALM... Polarion does not support us unless we pay thousands for “support package” I just don’t see the value added. Especially when our “DevOps” secretary is sub par.. plus I don’t believe in DevOps.. no value added for someone who can’t engineer only sudo direct. Hell we almost wanna use our interns for requirements tracking/ record keeping. We as the engineers know what todo and have been doing shit the old way for decades without issues...

Need suggestions for small team per project.. 1softwar 1elec 1mech... but large team over all across many projects.

Sorry for the long rant.. at the bar .. kinda drunk ranting tbh but do need opinions...

So today was my last day before heading off for an2 week holiday. Spent most of the day explaining to my team what needs to be done and how everything has been structured for the current project, but I get the feeling they don't understand any of it.

Pretty sure I'll be coming back to a clusterfuck.

I'm trying to load an SVG icon sprite file in a Webpack based application. It's been almost three hours with no success.
This is why I hate frontend development. Libraries are not structured and make no sense. It's a game of luck.

Am I the only one who thinks OOP in Javascript isn't always the best option? I really like structured code with classes and objects but sometimes it's just fun and satisfying to write a buttload of functions to do all sorts of things and build your code with that.

Here is my problem. The team I'm on has developers from other areas that were "put" into a new team. Two use "structured programming" but the requirements make me think we need "domain driven design". How in the world can I get them to evolve into another mindset while still meeting the deadline?

Let's do a story mapping session! Ok cool. PO asks the team: so guys what do you think? *silence*... *more silence*.... PO: come on guys, please respond. *silence*.... Then someone finally responds.

I'm starting to hate this big time. It's almost always like that, no matter the type of session (story mapping, refinement) And there's someone in the team that thinks he always knows best, so if ever someone speaks up, it will always be challenged and lead to useless discussions. He always wants the perfect solution. A good solution is good enough, it doesn't have to be perfect. PO is happy with a good solution (good = maintainable, scoring at least x on our code quality tooling), so why the fuck would you want to go for the 'perfect' solution, which may score just slightly higher in regard to quality, cost much more to develop and people have a hard time maintaining it due to the high level of abstraction? He's always refactoring stuff because it's not future proof. Well, why completely reimplement parts that have been working properly for 2 years and have a very very small chance of needing a change, which then still only needs to be done in just 1 place?

And you know what? All these fancy structures, patterns etc are in there but will their flexibility ever really be used? In my 20 years experience haven't seen such flexibility being really used. Some exceptions of course.

Once it's built, it will keep running, yes, changes will need to be made, but in most cases they never touch all these expensive fancy structured components. Just because most changes are in content or small changes in functionality.

For me heaven is where everyone writes well documents, structured,modular and clean code

I'm a self taught web developer, I know I can develop great apps, but my code doesn't feel structured... It gets messier as I add more features, and this makes it harder to develop and keep track of everything.

How can I improve this, are there any processes to follow?

Error reporting. Yeah it is a pain to come up with something that users will understand. As devs we need meaningful stacktraces so we can diagnose the problem but the normal person doesn't care. Also not having consistent messages looks terrible for the user's experience.

I hate it when there is no standardized error messages and/or json structure between teams or individual members of said teams. Why should we have 10+ different structures to code for in our apps? There is RFC 7807 for a reason. It has a defined structure plus accounts for custom properties. If you are a c# developer, check out the ProblemDetails class. It has made my life easier and I can guarantee everyone that all of my team's projects return this structure.

I joined a startup and suddenly all I thought I know was disappearing and a very complex creature fell into my laps asking me to code it. Then there’s these trello cards asking me to pick them up and start solving.

Well, first, no idea how the whole app is structured.

Good thing, have a supportive team for sure.

I'm building an Android app from ground up targeting to have functionalities added without much effort in succeeding phases.

What I'm pissed about mobile development at the moment though, is its lack of structured code base that is easy to follow. Unlike web where codes are modularized and well placed, in mobile, I kept going back and fort in different modules to see how they are used in all places in the project which made it tedious as time goes.

So I kept a notepad keep track of detailed flow. However, once I go back at the notes to place them on top of your head, the almost spaghetti-like structure just becomes very hard to track. For me it doesn't follow a pattern and that developers are free to do what ever they wish so as long as it can run in the device or emulator.

For instance, implementing concurrency as well as dependency management and a Clean architecture is such a pain. I hope i can relate to someone here.

If only there is a standardized way of structuring codes in android in Java or Kotlin (haven't tried this), there would be hope for me. So if anyone can provide a good, readable, reliable android project that I can start building my project on top of, your help will be greatly appreciated! Thanks for reading.

Each time I happen to land on some sort of discussion, be it on Reddit, YouTube comments or even sometimes here on devrant, I wonder if there are ways to make debates more meaningful (sometimes I imagine that the participants of a particularly heated conversation suddenly meet physically and say the contents of their comments out loud; and it makes me laugh all by myself).
Anyway, I feel like Internet is generally not a good place for debates (at least political ones). Is it just me? Is it the fact that it doesn't take a lot of effort to write a message, or maybe that conversations are necessarily different when you don't see someone in front of you?
I've come across websites like Kialo which seem to be a good idea. Is that because the opinions written there are more structured that it looks like ideas are better conveyed? Deep thinking tonight 😄

Being a developer allows you to enjoy using most of the creative skills artists also put to use (writing structured prose, design, semantics, ergonomics, ethics), while adding logic, job safety, and a decent paycheck to the mix.

Also: puts you in a good position to readily take advantage of new digital goodies (eg bitcoin), and to understand the gem that is developer humor

I was in an interview and all they really could tell me was the projects 'on the shelf' how they were understaffed, and new opportunities due to covid, that were coming onto the current development pipeline.

How would you guys react to a headhunted talk at a company structured like that? Just curious, it spooked me a bit at first.

Autodesk's documentation in general must be the worst documentation ever made!
Im shocked that a company creating a HELP TOOL wont even provide structured and decent documentation!

I recently joined a good MNC as a .net fullstack dev and right now contributing mostly to the frontend part to one of our projects. I have another team member writing the APIs and when i look at how the middletier is written and how APIs are structured, its just plain shit nothing else. It hardly follows any restful principles, returns weird response code, no design patterns at all, in short its a 10 year experienced dev writing code like a fresher.
I tried to communicate my concerns in a nice way but they were not taken very well. And when later I am asked to work on that codebase it will be like jumping in a pile of shit.
Now my question to you wonderfull people out there is, how do you handle situations like this? Do you have any suggestions for me please?

Is it just me or are the majority of plugins for WordPress simply wrappers for interacting with the DB? (In the sense that there's no need for them in more modern CMSs that feature structured content functionality out of the box)

good evening devs,

any suggestions/tips, on how to learn more efficiently, more effectively, more structured?
Recently, after school/work, my discipline to learn is lost a bit..
Because, watching tutorials or reading, while programming the shown, isn't the right thing for me.
I need definitely much more practice , to keep shit in my brain.
Maybe i need ideas? small projects and then make it bigger and bigger?

How do you learn?
Whats your way to practice?

So, this backend dev, thinks because I am doing frontend work I have no knowledge on backend stuff.

I ask him for a backend feature to match my front end feature. He says that that will take about 4 weeks and therefore cannot be included in this scope. I ask why because its something really easy. He says he'd have explained but I cannot get it.

So I ask him why they have their tables structured that way (I went in and checked ). I then went ahead and schooled the guy on SQL, normalizing databases and other stuff.

Put some respect on frontend devs. some of us are fullstack

Originally designed backend to work one way but then frontend UX was shit because of how the app was structured. Have reworked frontend to be structured differently and now I have to work around the original backend structure because I don't have time to rewrite it. Everything's a mess. It works, but it could be way simpler.

This sucks.

Is there a structured way to learn Linux? I am a developer who is trying to learn cloud computing.

Sooo. That starts to be a bit annoying:

I'm working on a large refactoring with a pretty good inheritance / generic system. And some code generators.

Rghjt now I'm doing a script which generate code files, which will generate code-gen templates which will generate final files.

It's funny and it's a one shot generation, but still. So much abstraction.

(End result is good tho. Everything in small files less than 15 lignes of code. Everything structured.)

I need nextjs tips

Im coding in nextjs for the first time because the framework i need to use only supports nextjs/vite/react. I have no idea how this framework works and im literally googling for almost every single bit. Also using chatgpt as copilot. Heck im googling even how to do routing here. The code is probably gonna be total shit.

Anyone can give me some tips in nextjs on how to keep the code clean? How is a project supposed to be structured?

Disclaimer: I love open source and I adore the owasp for what they do.

BUT owasp zap has to be the most overly complicated, badly documented tool in existence. As long as one stays within its most basic functions everything is fine, setting it up as a proxy and even issuing a root cert for our test devices worked wonderfully simple.

Then I made the mistake to try to actually do anything with the data we pulled and had to dive into the scripting console.

The documentation basically consists only of "This thing exists", it provides a msg object with no information what it contains or how it's structured, has no code completion and, here comes the kicker, if the script is run and has an error it gets flagged and can't be reenabled after the error is fixed. So I'm currently at forwarder48.groovy trying to simply store the request on a database for possible diagnostics.

So right now I already know that I'll spend most of my vacation next week trying to decipher the source, document it, fix that damn "flagged as error" bullshit and jump through a billion hoops trying to get a pull request through.