Dude! We have toilets on each floor. Why do you push shit on git?

me.children += 1;
^_^

Words of wisdom (WOW) !!

How I feel when editing an Android Manifest file

FUCK!! It's been 3 days in the new office.
Can't find a single to rant about.
Why is everyone is so fucking nice??

LONG RANT AHEAD!

In my workplace (dev company) I am the only dev using Linux on my workstation. I joined project XX, a senior dev onboarded me. Downloaded the code, built the source, launched the app,.. BAM - an exception in catalina.out. ORM framework failed to map something.

mvn clean && mvn install

same thing happens again. I address this incident to sr dev and response is "well.... it works on my machine and has worked for all other devs. It must be your environment issue. Prolly linux is to blame?" So I spend another hour trying to dig up the bug. Narrowed it down to a single datamodel with ORM mapping annotation looking somewhat off. Fixed it.

mvn clean && mvn install

the app now works perfectly. Apparently this bug has been in the codebase for years and Windows used to mask it somehow w/o throwing an exception. God knows what undefined behaviour was happening in the background...

Months fly by and I'm invited to join another project. Sounds really cool! I get accesses, checkout the code, build it (after crossing the hell of VPNs on Linux). Run component 1/4 -- all goocy. run component 2,3/4 -- looks perfect. Run component 4/4 -- BAM: LinkageError. Turns out there is something wrong with OSGi dependencies as ClassLoader attempts to load the same class twice, from 2 different sources. Coworkers with Windows and MACs have never seen this kind of exception and lead dev replies with "I think you should use a normal environment for work rather than playing with your Linux". Wtf... It's java. Every env is "normal env" for JVM! I do some digging. One day passes by.. second one.. third.. the weekend.. The next Friday comes and I still haven't succeeded to launch component #4. Eventually I give up (since I cannot charge a client for a week I spent trying to set up my env) and walk away from that project. Ever since this LinkageError was always in my mind, for some reason I could not let it go. It was driving me CRAZY! So half a year passes by and one of the project devs gets a new MB pro. 2 days later I get a PM: "umm.. were you the one who used to get LinkageError while starting component #4 up?". You guys have NO IDEA how happy his message made me. I mean... I was frickin HIGH: all smiling, singing, even dancing behind my desk!! Apparently the guy had the same problem I did. Except he was familiar with the project quite well. It took 3 more days for him to figure out what was wrong and fix it. And it indeed was an error in the project -- not my "abnormal Linux env"! And again for some hell knows what reason Windows was masking a mistake in the codebase and not popping an error where it must have popped. Linux on the other hand found the error and crashed the app immediatelly so the product would not be shipped with God knows what bugs...

I do not mean to bring up a flame war or smth, but It's obvious I've kind of saved 2 projects from "undefined magical behaviour" by just using Linux. I guess what I really wanted to say is that no matter how good dev you are, whether you are a sr, lead or chief dev, if your coworker (let it be another sr or a jr dev) says he gets an error and YOU cannot figure out what the heck is wrong, you should not blame the dev or an environment w/o knowing it for a fact. If something is not working - figure out the WHATs and WHYs first. Analyze, compare data to other envs,... Not only you will help a new guy to join your team but also you'll learn something new. And in some cases something crucial, e.g. a serious messup in the codebase.

Douche: So your a programmer ?

Me: Yes

Douche: Excellent, I have an idea.....

Me: No

Douche: cmon bro, week be rich, this screensaver so will make us tons of money

Me: I have a question.

Douche: corz man waddup

Me: do you use a screensaver?

Douche: no, why?

Me: *walks away angrily

Dev life chose me

How web developers debug their markup...

.someBox {
background-color: pink;
}

Client: Glad to have you on the team, you come highly recommended for your experience in Microsoft technology, specifically asp.net

Me: I was contacted for a php, mariadb project

Client: well they're all the same

Me: actually sir no.... No they're not.

Client: then why was I told to contact you

Me: you tell me, your hiring manager contacted me for a php project not asp or. Net

Client: well I guess I know who to blame for your, sorry for taking your time. Can I contact you if we have a project made with that thing you mentioned?

Me: php?, Sure

Client: nice...... Take care

Me: you too

That went better than I expected

My first rant here, don't know how to start, but fuck these self proclaimed senior developers who can't even get their concepts right about basic things and don't believe in reading docs.

Fuck you for asking if sequelize has a method to return details of the logged in user of your app, it's a fucking ORM you dumbfuck. You are a "full stack" developer for fuck's sake.

Fuck you for making those "minor changes" which breaks build and then blame it on any random plugin or lib used, or my commits.

Fuck you for expecting me to review your code on Sundays because you couldn't finish it on time.

I don't like java, at all, but even I get that without it we wouldn't be where we are right now and can't reach where we aspire to reach. But you can't keep chanting "Java is dead, Java is dead" every chance you get. No, it's NOT dead. Nor is going to, anytime soon.

And for god's sake, please stop choosing one library/plugin over another just on the basis of stars on repo, it's not the only (or valid) criteria. Look if you actually even need it. Think.

And please learn how to google first, and also stop using "the" before every the noun, the adjective and the verb. It's the fucking the annoying to read.

And yes, there are different linting presets out there, and just because a piece of code in a plugin/library/boilerplate is not following your specific, and may I say horrible standard, doesn't mean it's a "bad code". It's written by people who have created/worked-on these libraries as side projects on which your entire career is based upon.

And I haven't even talked about the code you write or your domain knowledge or the way you treat other people. So get off your high horse and behave like a developer, a real one.

Seven months ago:
===============
Project Manager: - "Guys, we need to make this brand new ProjectX, here are the specs. What do you think?"

Bored Old Lead: - "I was going to resign this week but you've convinced me, this is a challenge, I never worked with this stack, I'm staying! I'll gladly play with this framework I never used before, it seems to work with this libA I can use here and this libB that I can use here! Such fun!"

Project Manager: - "Awesome! I'm counting on you!"

Six months ago:
====================
Cprn: - "So this part you asked me to implement is tons of work due to the way you're using libA. I really don't think we need it here. We could use a more common approach."

Bored Old Lead: - "No, I already rewrote parts of libB to work with libA, we're keeping it. Just do what's needed."

Cprn: - "Really? Oh, I see. It solves this one issue I'm having at least. Did you push the changes upstream?"

Bored Old Lead: - "No, nobody uses it like that, people don't need it."

Cprn: - "Wait... What? Then why did you even *think* about using those two libs together? It makes no sense."

Bored Old Lead: - "Come on, it's a challenge! Read it! Understand it! It'll make you a better coder!"

Four months ago:
==============
Cprn: - "That version of the framework you used is loosing support next month. We really should update."

Bored Old Lead: - "Yeah, we can't. I changed some core framework mechanics and the patches won't work with the new version. I'd have to rewrite these."

Cprn: - "Please do?"

Bored Old Lead: - "Nah, it's a waste of time! We're not updating!"

Three months ago:
===============
Bored Old Lead: - "The code you committed doesn't pass the tests."

Cprn: - "I just run it on my working copy and everything passes."

Bored Old Lead: - "Doesn't work on mine."

Cprn: - "Let me take a look... Ah! Here you go! You've misused these two options in the framework config for your dev environment."

Bored Old Lead: - "No, I had to hack them like that to work with libB."

Cprn: - "But the new framework version already brings everything we need from libB. We could just update and drop it."

Bored Old Lead: - "No! Can't update, remember?"

Last Friday:
=========
Bored Old Lead: - "You need to rewrite these tests. They work really slow. Two hours to pass all."

Cprn: - "What..? How come? I just run them on revision from this morning and all passed in a minute."

Bored Old Lead: - "Pull the changes and try again. I changed few input dataset objects and then copied results from error messages to assertions to make the tests pass and now it takes two hours. I've narrowed it to those weird tests here."

Cprn: - "Yeah, all of those use ORM. Maybe it's something with the model?"

Bored Old Lead: - "No, all is fine with the model. I was just there rewriting the way framework maps data types to accommodate for my new type that's really just an enum but I made it into a special custom object that needs special custom handling in the ORM. I haven't noticed any issues."

Cprn: - "What!? This makes *zero* sense! You're rewriting vendor code and expect everything to just work!? You're using libs that aren't designed to work together in production code because you wanted a challenge!?? And when everything blows up you're blaming my test code that you're feeding with incorrect dataset!??? See you on Monday, I'm going home! *door slam*"

Today:
=====
Project Manager: - "Cprn, Bored Old Lead left on Friday. He said he can't work with you. You're responsible for Project X now."

Cringing when movies get programming things wrong 😷

Clint want custom CMS with php,

*makes custom CMS with php

Client thinks it's not php coz it looks pretty.

*shows php code

client still not convinced it's php

Sending a well typed professional email to your boss, but receiving a:

Sure thing

Dave

Sent from my iPhone

Being a software developer automatically qualifies you to fix paper jams and wi-fi issues in the eyes of your family.

Laravel is the worst framework ever.

Everything has to be made convenient and easy. That sounds amazing, because developers want to save time, worry less about boilerplate code, right? No more constructors, no more dependency injection, fuck all the tedious OOP shit... RIGHT?

It does one thing well: Make PHP syntax uniform and concise through easily integrated libraries such as Collection and Carbon. But those are actually not really part of the framework... just commonly integrated and associated with Laravel.

The framework itself is completely derailed: You can define code in a callback in the routes file. You can define a controller in the routes file. You can define middleware as a parameter to the route, as a fluent method to the route, you can stack them up in a service provider. Validators can be made in controllers, Request objects, service providers, etc. You can send mail inline, through Mailable objects, through Notification objects, etc.

Everything is macroable, injectable, and definable in a million different places. Ultimate freedom!

Guess what happens when you give 50 developers of various seniority a swiss army knife?

One hammers in a screw with a nail file, the other clips the head from the screw using scissors, and you end up with an unworkable mess and blunt tools.

And don't get me started about Eloquent, the Active Record ORM. It's cute for the simple blog/article/author/comment queries, but starts choking when you want more selective and performant queries or more complex aggregates, and provides such an opaque apple-esque interface which lets people think everything is OK, when in reality it's forcing the SQL server to slowly commit suicide.

*We colleagues were cursing Valentine's week*

Team Lead : Committed?
Me: No, I am single.
TL: *confused look* Did you committed that code?
Me: ohh yes! I raised the merge request as well.
TL: Ok. I will review it. *Moves away smiling inside*
Me: *looking at screen* *crying inside*

"I want to create a Linux distribution from scratch but i don't know how to code, I'll pay you $300 but i get to have the rights to it"

Never have I been so furious whilst at work as yesterday, I am still super pissed about going back today but knowing it's only for another few weeks makes it baerable.

I have been the lead developer on a project for the last 3~ months and our CTO is the product owner. So every now and then he decides to just work on a feature he is interested in- fair enough I guess. But everything I have to go and clean up his horrendous code. Everything he writes is an absolute joke, it's like he is constantly in Hackathon mode "let's just copy and paste some code here, hardcoded shit there and forgot about separation of code- it all goes in 1 file".

So yesterday he added a application to the project and instead of reusing a shared data access layer he added an entirely new ORM, which is near identical to the existing ORM in use, for this one application.

Being anal about these things, the first thing I did was delete his shit and simply reference the shared library then refactor a little code to make it compatible.

WELL!! I certainly hit a nerve, he went crazy spamming messages on Slack demanding I revert as it broke ONE SINGLE QUERY that he hadn't checked in (he does 1 huge commit for 10 of everyone else's). I stuck to my principals and explained both ORM's are similar and that we only needed one, the second would cause a fragmented codebase for no benefit whatsoever.

The lead Dev was then forced to come and convince me to revert, again I refused and called out the shit quality of their code. The battle raged on via the public slack group and I could hear colleagues enjoying the heated debate, new users even started joining the group just to get in on mine and the cto's difference of opinion.

I even offered to fix his code for him if he were to commit it, obviously that was not taken well ;).

Once I finally got a luck at the cluster fuck of shit he had written it took me around 5 minutes to fix and I ever improved performance. Regardless he was having none of it. Still the demands to revert continued.

I left the office steaming after long discussions with the lead Dev caught in the middle.

Fortunately my day was salvages with a positive technical discussion that evening at a company with whome I had a job offer from.

I really hate burning bridges and have never left a company under bad terms but this dictator is making me look forward to breaking the news today I will be gone in 4 weeks.

Got a new job as UX Developer! Drinks are on me guys 🍻

I like it when a boss is a Dev (or a former Dev). Makes them a bit more sympathetic towards us i think :)

I write code,
I am a writer.
I fight with bugs,
I am a fighter.
I optimise code,
to make it tighter.

The fact you’re older doesn’t give you the right to call other people’s 8-months’ engineering effort “shit work”, especially if you didn’t even see the code...

Sincerely,
Your tech lead - me :)

Ok, rant incoming.
Dates. Frigging dates. Apparently we as a species are so bloody incompetent we cannot even decide on a one format for how to write today. No, instead we have one for every language and framework, because every moron thinks they know better how to write the date. All of them equivalent and all of them different enough to make me start lactating out of frustration trying to parse this garbage... And when you finally manage to parse it on one platform it turns out that your ORM just decided to use the less common version of the date, and have fun converting one to the other. I hope that ever time someone comes up with a new date format will be hit in a face with a red hot frying pan untill they give up programming in favour of growing cactuses.

"SEO optimization"
Ever read what the "O" in SEO stands for, Einstein?

Stack Overflow documentation is gonna be awesome in a few years...

I recalled a seemingly simple task I took on.

We were building a booking system, and I had to figure out how to retrieve bookings by a certain date range.

Upfront, the tasked seemed simple until I realised I had to both figure out the logic and the SQL statements needed to retrieve all bookings within a certain date range in one query.

I ended up drawing a model to help me visualise the various date-range criteria to be satisfied. And used unit tests to help me think through each date range criterion and make sure they were accurate. Some were obviously from paranoia, but better to be safe than sorry...

After that, I had wrote down raw SQL directly into Sequel Pro first to make sure my query logic was accurate too, before translating into something the ORM equivalent. This was when I learned how to define and use variables in SQL. The variables were throw-away code; I just didn't want to have to hard-code the test date-ranges over and over again; minimise chances of spelling errors.

Needless to say, felt my problem-solving skills went up one level after this task. Saw my coding style and unit tests improve. And also the thought processes that go into how to maintain code quality...

Noisy collegues. Also the people who come to talk anytime.

So I found this sticker while cleaning my desk. Now my work laptop looks better

/* secret devRant script */

let joke = "why do Java developers wear glasses? Because they can't C#"

//check if rant was posted recently
if ( !recentRants.find(joke) ) {
postRant(joke)
}

Morning: Boss decided he was changing all the table names, used a different ORM than we are used to, and implemented it in such a way that the connections stay open and live forever, and had ultimately destroyed half our existing codebase.
Midday: clients keep messaging saying that everything is broken, and rather than accepting that we are fixing it, they want an entire breakdown of exactly what is wrong.
Afternoon: clients still say things are broken even though they have been fixed - they keep sending month old screenshots, which is obvious because the entire interface has changed since then.
Conclusion: shouldn't have gone to work today.

The effort I put into git commit messages directly reflects my mood and level of tiredness.

When a programmer casts a spell...

My son is taking a nap and you know what that means - time to write some code!

I love the skill requirements section of a junior Dev job advertisement.

To summarise "Basically you'll need all the skills and experience of a senior, but we are gonna pay you much much less". 😔

Yeah dude, if I'm wearing my headphones it means "do not disturb"

I’m so fuckin general I got asked in an interview what normalization was. I couldn’t think of the words to say. I practice normalization by common sense in any database I’ve designed but can’t break it down for you by its “n”s.

And yet when they ask me how a JWT token works, I give a detailed description of each step in its description.

No I can’t explain why symfonies ORM out beats laravel a eloquent. I tinker with laravel on one project, .net on another, django on another. I don’t care how each one does it, I’ll figure it out when I need it.

And yet when they ask me how to in real time notify a subset of active users on a page, I can describe the general need for a web socket and pub sub service to publish to a specific hash of subscribed clients.

The specifics don’t consume me. I’m not a symfony dev or a django dev. I’m a senior dev that has a wide spanning general tone for what is needed. I dive deep when I need to dive deep and I’m handicapped with not assigning to memory words traded for common sense like “normalization”.

My mother is so ashamed of me.
she tells everybody that I'm a Drug dealer.

PHP Developer here.

Today we have a client visiting work. Dressing like a proper business person is mandatory 🙄

Why the fuck someone write "used linux to speed up development" in your resume. But when you have to use it, questions like "where to download git for linux?" appears?

Giving functions exciting names so you can feel like a Bond villain while programming:

execute(); destroy(); fire(); isDead();

God this code is hideous

* git blame *

Ahhhh

*slowly back away from the computer*

Using Sololearn: feel like a pro.
Open Devrant: feel like a noob.

When someone comes to your desk and asks "did you get my slack message".... Which they sent 23 seconds ago 😒

Shut Up Dirty Mind! I am learning React Native.

When developers can't use Regex:

'Your credit card number cannot contain spaces'

ಠ_ಠ

I loved Java very much..
Then i started using it.

*Writes a recursive function that works first time*

*Feels like programming God*

When you are in a hurry to make payment .. and some fucker has done this.

Height of Confidence.

Expecting your client to be nice with you just because you are nice to them is like expecting lion not to eat you, because you don't eat lions.

GoodGuy BroCow
Senoir problem
2years back

Senoir dev was assigned to make a webapp for billing

Dude uses dreamviewer and writes code like a bitch

Phpmysqljqueryhtml whole thing mixed very badly and undocumented

His function name format fun_1()

a simple update cost him a day,

Told him to use brackets atleast and also a framework ,guy denies

Days go by

He learns a lot of stuffs from me ,like how to use inspect in chrome lol, how to use sqlite for small projects , and orm and frameworks.

He used to pin his mistakes on me, so that boss gets angry on me

Then i quit the job

2 years went by

Now he is unemployed, nobody wants a 24 year old plain php coder and template editing web developer

Anyway I hired him, he was my first senior, whatever he did,it didnt matter to me, bcoz i remember

the days we spent on the same hall right next to each other coding in php,

days we brainstormed to fix a div

Also the days we ate lunch and breakfast together

At last got mine! Thanks Devrant!

I wonder how much of my life I have spent waiting for 'npm install'

I was working on a very database heavy PHP app about six months ago. All database access was done directly, with hardcoded SQL strings.
I'd suggested switching over to an ORM during the upcoming major verson's rewrite, and FINALLY got approval to start integrating one.
The next week I'm told that I need to trash all the code I'd just written, since the decision to use an orm has been reversed.

The rationale? According to management, ORMs aren't "scalable enough for our application" and would "reduce developer productivity". I pointed out that we would be processing ~10 concurrent operations, maximum; I was told that the technically details didn't matter and the person I was working under had the final say because they'd worked at IBM, briefly, as an intern.

I stopped working on that project about two weeks later, thankfully.

That moment when you change your mindset from "I'll probably leave the office by 6pm" to "I hope I'll leave before midnight"

This is really creepy. Yesterday I was talking to my parents about buying a Thermosteel flask. Today I opened Amazon and this is what I see.. (attached pic)
I am pretty sure, I didn't looked for it even on Google.
It may be co-incidence but still..

When I tell my relatives that I'm a backend developer. Then the image they have in mind is...

So almost burst a vein today because of a teacher who kept telling us that the .NET orm , Entity framework , loaded the whole database in memory at a context's instantiation , i thought that's kind of stupid thing for an ORM today,considering the hit on performance and memory consumption with large DBs, and asked her to argument why they would adopt such an approach , at the end she said it worked like that and that me saying it's inconvenient is just my stupid opinion . when i looked it up on the internet i couldn't for the life of me find any mention of that behavior and that she was completely WRONG !! i fucking hate this dumbshit university am going to , anyone looking for an intern trying to escape dumb fucks ?

Hello (World)! Noob here. I installed devRant around 5 days ago. I just keep reading the rants and didn't created my account because i was not sure if i will stay here for long time coz most (cr-)apps are boring.

After 5 days:
I owe all of you a tons of '++'.

I want a boss like @Linux have. (i know tags work only in comments)

Gonna stay here till i stay in IT industry.(maybe)

My most satisfying bug fix?

I found a core concurrency issue in this gnarly homegrown ORM and reported it to the lead devs, who (very defensively, having written the damn thing) argued that it would never pop up in a prod environment and I was stupid for even bringing it up. Theoretically, this bug could cause pretty much every foreign key to be assigned to the wrong parent, but only if multiple instances of the application were open/running at once. They were so certain it would never happen on live that they explicitly instructed me not to fix it. After all, this bug had been active for many years on a previous project and nobody complained.

Problem was, that previous project was something that only a single user had open most of the time (think: a manager). The new project was something that would be used by multiple people at the same time (think: all the employees). Once we released this new-project-with-old-orm, it didn't take long at all for our customers to start complaining.

After that, they let me fix the bug. :)

Once I didn't knew anything about coding or development.
Someone suggested me to start with Java.

Still looking for that Mada-foker.

Worst documentation I've seen?

Our "Coding Standards" 20+ page document. The team who put it together got so detailed, there wasn't much 'wiggle room' for natural deviations in a developer's coding style. For example, a section devoted to no abbreviations. So if you had a variable 'invoiceId', they complained you violated 'standards', even though 'invoiceId' matched a field name in a database table. Using Dapper or another ORM that relied on the 1:1 name match? Nope, you were still forced to inject your own mappers so the code didn't violate standards.

As you can probably guess, such a long, detailed document would have contradictions. I pointed out one of the contradictions. Example:

Page 5: Section B, sub-section B-5, paragraph 3 : "To minimize network traffic, when querying the database, request all the data necessary for the application."
Page 8: Section K, sub-section K-2, paragraph 4 : "For maximum performance, when querying the database, request only the most minimum amount of data necessary for the application ."

In a review I pointed out this contradiction (there were several more)
Me: "If we satisfy A, one could say the code is in violation of B. Which is it?"
<Pointy-Hair-Boss throws his pencil on the table>
PHB: "WHAT IS YOUR PROBLEM WITH STANDARDS! It couldn't be more clear! We are a company of standards because without standards <blah blah..straw man argument..blah blah>"
<deciding not to die on that hill, I move on>
Me: "On page 12, paragraph 9 code is in violation if a method has more than 3 parameters. That seems a little restrictive given our interaction with 3rd party products."
PHB: "There you go again. As stated in the document, ALL code used by the company will comply to our standards. What part of 'ALL' do you not understand?"

Was he bluffing about requiring 3rd party vendors complying with our standards? Heck no. That's a story for another day.

finally!!! after loads of time (go Israeli post service) stickers are here!!!
thanks devRant

I wish I could do TDD on my life decisions

Video call interviews are the best! You don’t even need trousers...

"A comment isn't needed if the name is good and the responsibility is clear" - M.Howell

Rant!

Been working on 'MVP' features of a new product for the past 14 months. Customer has no f**king clue on how to design for performance. An uncomfortable amount of faith was placed on the ORM (ORMs are not bad as long as you know what you are doing) and the magic that the current framework provides. (Again, magic is good so long as you understand what happens behind the smoke and mirrors - but f**k all that... coz hey, productivity, right?). Customer was so focussed on features that no one ever thought of giving any attention to subtler things like 'hey, my transaction is doing a gazillion joins across trizillion tables while making a million calls to the db - maybe I should put more f**king thought into my design.' We foresaw performance and concurrency issues and raised them way ahead of the release. How did the customer respond? By hiring a performance tester. Fair enough - but what did that translate into? Nothing. Nada. Zilch. Hiring a perf tester doesn't automagically fix issues. The perf tester did not have a stable environment, a stable build or anything that is required to do a test with meaningful results. As the release date approached, the customer launched a pilot and things started failing spectacularly with the system not able to support more than 15 concurrent users. WTF! (My 'I told you so' moment) Emails started flying in all directions and the hunt for the scapegoat was on (I'm a sucker for CYA so I was covered). People started pointing in all directions but no one bothered to take a step back and understand what was causing the issues. Numero uno reason for transaction failure was deadlocks. We were using a proprietary DB with kickass tooling. No one bothered to use the tooling to understand what was the resource in contention let alone how to fix the contention. Absolute panic - its like they just froze. Debugging shit and doing the same thing again and again just so that management knew they were upto something. Most of the indexes had a fragmentation of 99.8% - I shit you not. Anywho, we now have a 'war room' where the perf tester needs to script the entire project by tonight and come up with some numbers that will amount to nothing while we stay up and keep profiling the shit out of the application under load.

Lessons learnt - When you foresee a problem make a LOT of noise to get people to act upon it and not wait till it comes back and bites you in the ass. Better yet, try not to get into a team where people can't understand the implications of shitty design choices. War room my ass!

Oh dear god no

Now this is true. Devrant changed me and now, after one of the devranters post I'm finally searching for a new job. Most of the time I was using PHP, but here I've seen lot of rants about laravel. Now I'm building a website with it and going to change my job. Thank you Devrant creators and community.

When people include the entire jQuery library to animate one single div 😑

Had to consume a soap webservice which spits out a XML of 5000 lines with ambiguous node names and a shitload of data that needs to be parsed.

Built a ORM model to hold all the data and I already built a Xmlparser which works like a boss.. untill now..

I've been debugging for 3 hours, cursing every God man ever made up. Swearing at my screen like a madman... but this particular set of nodes just didn't got saved properly to the DB...

Alright, so my ORM definition is fucked... nope... Alright, so my XmlParser is fucked... nope...

Whaaaaat the fuuuuck...

Oh wait, I've been checking the wrong table for hours....

Hooray for ambiguous tables because I followed the ambiguous structure.

I am going to get drunk now.

X

Stack overflow was down..
I don't know why, but it developed some kind of respect for senior developers who don't had access to stack overflow in their time.

Instantly thought about new js framework name

made a Facebook app once that allowed users to submit their stories for a competition to win a tablet. The HTML form had no limit on length but ORM defaulted to 1000 characters in database, imagine the sourprise when we exported the data for the client at the end...

Programming on a train is always interesting. I expect a minimum of one dirty/confused look off a member of the public.

Alright lads here is the thing, have not been posting anything other than replies to things cuz I have been busy being miserable at school and dealing with work stuff.

Our manager left us back in February. Because she was leaving I decided that I wanted to try a different path and went on to become a programmer analyst for my institution, if anything I knew that it was going to be pretty boring work, but it came with nice monetary compensation and a foot in the door for other data science related jobs in the future. Thing is, the department head asked me to stay in the web technologies department because we had a lack of people there and hiring is hard as shit, we do not do remote jobs since our work usually requires a level of discretion and security. Thus I have been working in the web tech department since she left albeit with a different title since I aced the interview for the analyst position and the team there were more than happy to have me. I have done very few things for them, some reports here and there and mostly working directly with the DBA in some projects. One migration project would have costed my institution a total of 58k and we managed to save the cost by building the migration software ourselves.....honestly it was a fucking cake walk, if you had any doubts about the shaddyness of enterprise level applications regarding selling overpriced shit with different levels of complexity, keep them, enterprise is shaddy af indeed. But I digress.

I wrote the specification for the manager position along the previous manager, we had decided that the next candidate needed to be strong with development knowledge as well as other things as to properly understand and manage a software team, we made the academic requirement(fuck you, yes we did ask for academic requirements) to be either in the Computer Science/software engineering area or at least on the Business Administration side. We were willing to consider BA holders in exchange for having knowledge of the development process of different products and a complete understanding of what developers go through. NOT ONE SINGLE motherfucker was able to satisfy this, some of them were idiots that I knew from before that had ABSOLUTELY no business even considering applying to the position, the courage it took for some of these assholes to apply would have hurt their mothers, their God if they had one, and their country, they were just that fucking bad in their jobs as well as being overall shit people.

Then we had 1 candidate actually fall through the cracks enough to get an interview. My dude here was lying out of his ass through the interview process. According to him he had "lots of Laravel experience and experience managing Laravel projects" and mentioned repeatedly how it would be a technology that we should consider for our products. I was to interview him alongside the vice president of our institution due to the head of my department and the rest of the managers for I.T being on vacation leave all at the same bloody time.

Backstory before the interview:
Whilst I was going over the interview questions with the vice president literally offered me the job instead. I replied with honesty, reflecting how I did not originally wanted him but feeling that our institution was ready to settle on any candidate due to the lack of potentials. He was happy to do it since apparently both him and the HOD were expecting me to step up sooner or later. I was floored.

Regardless, out of kindness he wanted to go through the interview.
So, going back to the interview. As soon as the person in question referenced the framework I started to ask him about it, just simple questions, the first was "what are your thoughts on the Eloquent ORM? I am not too fond of it and want to know what you as a full time laravel dev think of it"
his reply: "I am sorry I am not too familiar with it, I don't know what that is" <--- I appreciated his honesty in this but thought it funny that someone would say that he was a Laravel developer whilst not knowing what an ORM was since you can't really get away from using it on the initial stages of learning about Laravel, maybe if one wanted to go through the hurdle of switching to something like doctrine...but even then, it was....odd.

So I met with the hod when he came back, he was stoked at the prospect of having me become the manager and I happily accepted the position. It will be hell, but I don't even need to hit the ground running since I have been the face of the department since ages. My team were ecstatic about it since we are all close friends and they have been following my directions without complaints(but the ocational eat a dick puto) for some time, we work well together and we are happy to finally have someone to stop the constant barrage that comes from people taking advantage of a missing manager.

Its gonna get good, its gonna get fun, and i am getting to see how shit goes.

BuT wHy Do YoU uSe An ORM? YoU sHoUlD wRiTe RaW SQL fOr P e R f O r M a N c E

Kiss for fucks sake! What the fuck of an ORM is Sequelize? How the fuck do I have to write a 50 line query json to get a query for a single object going, which doesn't work then because that shit peace of software has a bug that breaks findOne and forces you to use findAll and use the first and only hit?!

Well yes, I looked in your garbage SEO docs for that issue, but whenever I look for something specific I just end up on your optimized as hell querying for noobs doc page. FUCK YOU!

Seriously, you guys working with Sequelize saved me many hours. But fuck your fuckups! And ajfjekidjjskrhbdkaowbdjdkwobdnfie

This is a public service announcement with a threat at the end of it:

"Do not, I repeat, do NOT attempt to write web applications, or any particular sort of application that works with a relational database (damn near more than half of applications) without a PROPER grasp and knowledge of SQL.
I do not want to see you reaching out for an ORM either, no, you need to learn to properly design a database or to properly interact with them AT most before you even attempt using an ORM OR designing an application from the beginning, shit will only hurt you in the long term I promise, learning SQL can go a looooong fucking way and most DBA's I know make way tf more than people think they make, it might even be an interesting career choice"

If you do not follow the above advise, and I see your ass reaching for building a web application without the above knowledge I will be under your bed at night, putting oil in my hairy body before I jump into bed to you and leave you confused for the rest of your life.

Build to learn, YES, but for the love of Chamberlain and Boyce PLEASE do not neglect SQL. I have seen such neglect REACH production and I am currently wishing I had these mfkers close to me.

My day:
5:30AM - 2yo son wakes me up, I send him back to his bed
6AM - wakes me up again, gotta grab a coffee
7:30AM - leaving towards the office
8:30AM - finally arriving to the office, after horrible traffic.
*continue working on major schema change I started yesterday*
12:30PM - Lunch + Beer
1:30PM - Tequila time!
*back to work*
7:30PM - Finally done with coding, leaving the office
8PM - home at last
9:30PM - Beer time
9:31PM - "I'll just write a couple of more lines"
12:30AM - "That's it, no more code for today"
12:31AM - "I'll just scroll through devRant"

Finally moving to new job. From monolith PHP dev, to nodejs.

Curious did any of you have a specific reason to learn how to program?

I wanted to be involved in aerospace but realised I'd probably never be an Astronaut, but i could learn how to write the software that controls the spacecrafts!

Thanks from England!

2 years ago..

Me : How can i learn Java?
College Senior : Do some online courses.

*did a course for a month! Still not confident*

Me: it ain't working for me.
Senior: Do some project.

*Created an Android App under internship! Still not confident*

After wasting my 6 months on Java, i reached to the conclusion that: "Java Sucks" (at least for me)

No Offence!

List of shit my superior said and wrote in the project:

1. Prefer to write "pure" SQL statement rather than ORM to handle basic CRUD ops.

2. Mixing frontend and backend data transformation.

3. Dump validation, data transformation, DB update in one fucking single function.

4. Calculate the datetime manually instead of using library like momentjs or Carbon.

5. No version control until I requested it. Even with vcs, I still have to fucking FTP into the staging and upload file one by one because they don't use SSH (wtf you tell me you don't know basic unix command?)

6. Don't care about efficiency, just loop through thousands of record for every columns in the table. An O(n) ops becomes O(n * m)

7. 6MB for loading a fucking webpage are you kidding me?

Now you telling me you want to make it into AJAX so it'll response faster? #kthxbye

left the office early today to see my 2 years old son before he goes to bed.
it's 11pm and I'm working from home, gonna wake up around 5:30am to commute to work.
I really need to move closer to work

Are any of you guys sentimental about your early programming efforts? I still have my first few simple Python programs on my computer, from years ago!

print("hello world")

First month of project we suggest that we test that Entity Framework has made reasonable DB queries because the system will need to handle a lot of records. “Not a priority in this sprint because we need features.” Devs try to get it into every sprint. The last week of the project they want us to dump in a ton of records so they can test it. The N+1 SELECT query issue is on main queries. It is so bad and slow with more records that a simple query causes the container management to auto scale the application on a single query. They can have max 8 users in the system at a time and it will take 10 seconds to do a simple page refresh.

They get on our case and we dredge up all of the correspondence where they completely ignored our advice. Fix it now! We need another sprint. Fix it free! No.

Client: "documentation, oh you mean those grey texts the previous code guy wrote on the code files"

Me: I kinda need more than "grey texts on the code files" if you want me to actually fix the system and implement the new specs.

Client: oh you mean the Microsoft asp books

Me: It's a Laravel system sir, it's php not asp.net

Client: what are those?

Me:.................

If I made £1 for every new JavaScript framework that came out, i would never need to work again.

PyCharm (and other IntelliJ based stuff), because it's second to none.

Bank holiday weekend setup...

I'm having a strong urge to kill that asshole that asked me, on a SECOND interview for a SENIOR position if I knew what ORM was!!!
Are you making me fucking waste my time you fucking cunt???
Did you fucking read my CV?
Obviously not because you would have seen several ORM technologies on it you fucking piece of shit.

You made me waste my time, and now I have no choice but to slice your fucking throat!

I'll be waiting for you, in the dark you mother fucker.

Why won't you just approve my PR???

Whats wrong with you?!

I don't understand your cryptic one-sentence feedback. I'm not even sure you understand what you're asking yourself.

What the hell does "make it a transaction" mean? Don't give me pseudo-code examples that don't even work fucking asshole!

Its a small change that does NOT need a canary build dammit. Don't go testing the ORM, its a goddamn standard library. Why does working with you make everything so complicated?!?!

The code fucking works! There is no need to make it comply to your specific tastes goddamn it. Working with you is like pulling teeth!

/endrant

We liked your portfolio work, but could you please show us an example of a Fibonacci sequence

ಠ_ಠ

Porn is Ok. I have to open incognito for my Dev Queries.

My last company had a code base originating in the 90's and they still write most parts of the GUI with a library that is a thin layer on top of Win32 API, with a self-rolled "ORM" for DB access (with LOTS of enums) and all that with >2million lines of C++ code. The code includes at least two implementations of std vector and std:list. One of which is even *named* std::vector. Feels good remembering that I have left that behind

I had once an sql error that took me two days to resolve it.
The error message was a syntax error but I was using an ORM to write my queries (doctrine with php) .I didn't have too much to debug as the code was pretty simple and clear so I got to the point that I convinced myself that this a bug and I'm gonna try to mess around it to avoid it.

Second day late night, something popped up in my mind '' hey what about those reserved words? Could it be the reason? '' aaaaand BINGO the key '' option '' is a fucking reserved word for mysql.

Tip : always check that list before writing your data models (specially if you're a noob like me)

devRant is great. It's like Yik Yak but for things I can relate to!

I think I can learn English here.
HAHAHA
I can also learn professional knowledge.

**I am a Korean.**

And...
Succeed!
Android studio AVD powered pictures

The more I work with performance, the less I like generated queries (incl. ORM-driven generators).

Like this other team came to me complaining that some query takes >3minutes to execute (an OLTP qry) and the HTTP timeout is 60 seconds, so.... there's a problem.

Sure, a simple explain analyze suggests that some UIDPK index is queried repeatedly for ~1M times (the qry plan was generated for 300k expected invocations), each Index Scan lasts for 0.15ms. So there you go.. Ofc I'd really like to see more decimal zeroes, rather than just 0.15, but still..

Rewriting the query with a CTE cut down the execution time to pathetic 0.04sec (40ms) w/o any loops in the plan.

I suggest that change to the team and I am responded a big fat NO - they cannot make any query changes since they don't have any control on their queries

....
*sigh*
....
*sigh*
but down to 0.04sec from 3+ minutes....
*sigh*

alright, let's try to VACUUM ANALYZE, although I doubt this will be of any help. IDK what I'll do if that doesn't change the execution plan :/ Prolly suggest finding a DBA (which they won't, as the client has no € for a DBA).

All this because developers, the very people sho should have COMPLETE control over the product's code, have no control over the SQLs.

This sucks!

When you apply HTML tags to the real world senario...

on one hand- got a new job, on the other hand getting a new MacBook pro just before they release a new generation

Cosmonaut is a simple and lightweight ORM for CosmosDB.

# Retrospective as Backend engineer

Once upon a time, I was rejected by a startup who tries to snag me from another company that I was working with.
They are looking for Senior / Supervisor level backend engineer and my profile looks like a fit for them.
So they contacted me, arranged a technical test, system design test, and interview with their lead backend engineer who also happens to be co-founder of the startup.

## The Interview

As usual, they asked me what are my contribution to previous workplace.
I answered them with achievements that I think are the best for each company that I worked with, and how to technologically achieve them.

One of it includes designing and implementing a `CQRS+ES` system in the backend.
With complete capability of what I `brag` as `Time Machine` through replaying event.

## The Rejection

And of course I was rejected by the startup, maybe specifically by the co-founder. As I asked around on the reason of rejection from an insider.

They insisted I am a guy who overengineer thing that are not needed, by doing `CQRS+ES`, and only suitable for RND, non-production stuffs.

Nobody needs that kind of `Time Machine`.

## Ironically

After switching jobs (to another company), becoming fullstack developer, learning about react and redux.
I can reflect back on this past experience and say this:

The same company that says `CQRS+ES` is an over engineering, also uses `React+Redux`.
Never did they realize the concept behind `React+Redux` is very similar to `CQRS+ES`.

- Separation of concern
- CQRS: `Command` is separated from `Query`
- Redux: Side effect / `Action` in `Thunk` separated from the presentation
- Managing State of Application
- ES: Through sequence of `Event` produced by `Command`
- Redux: Through action data produced / dispatched by `Action`
- Replayability
- ES: Through replaying `Event` into the `Applier`
- Redux: Through replay `Action` which trigger dispatch to `Reducer`

---

The same company that says `CQRS` is an over engineering also uses `ElasticSearch+MySQL`.
Never did they realize they are separating `WRITE` database into `MySQL` as their `Single Source Of Truth`, and `READ` database into `ElasticSearch` is also inline with `CQRS` principle.

## Value as Backend Engineer

It's a sad days as Backend Engineer these days. At least in the country I live in.
Seems like being a backend engineer is often under-appreciated.
Company (or people) seems to think of backend engineer is the guy who ONLY makes `CRUD` API endpoint to database.

- I've heard from Fullstack engineer who comes from React background complains about Backend engineers have it easy by only doing CRUD without having to worry about application.
- The same guy fails when given task in Backend to make a simple round-robin ticketing system.
- I've seen company who only hires Fullstack engineer with strong Frontend experience, fails to have basic understanding of how SQL Transaction and Connection Pool works.
- I've seen company Fullstack engineer relies on ORM to do super complex query instead of writing proper SQL, and prefer to translate SQL into ORM query language.
- I've seen company Fullstack engineer with strong React background brags about Uncle Bob clean code but fail to know on how to do basic dependency injection.
- I've heard company who made webapp criticize my way of handling `session` through http secure cookie. Saying it's a bad practice and better to use local storage. Despite my argument of `secure` in the cookie and ability to control cookie via backend.

Do you guys ever feel like you lose the ability to be objective about your own work. I've looked at my website for so long now, I don't know if I think it's good or not...

Every time I think I've seen the worst there's someone to prove me wrong...

GRANT ALL ON ALL TABLES/SEQUENCES
To web user on production

if (x == 1) y = 1;
else y = x;

loop through a collection and get 'few' relations using ORM - 1000s of queries and not a single join - but don't worry, "The ITs will just add more RAM and some CPU cores to the server"

4th day off and I already miss this

Man collapses in the street, his wife "help, we need a doctor".

Dev speaks up "I did recently move to a standing desk"

I present to you a php framework with an "orm" that doesnt support table joins. Yes, you heard it right.

I just want to say few things to the developers community -
If you are a bad programmer, please spend your time at improving rather than writing frameworks, or making the stupid decision on using SUCH SHIT FRAMEWORK AT A CORPORATE COMPANY!

Also if you are not sure if you are a good programmer or not, chances are you aren't. That's just how it is.

Eloquent is so fucking slow, my (dead) grandma queries faster. It takes the fucking double of time on a simple query with only one join for maybe ~200 rows... From now on I go fucking back to raw SQL in my Laravel projects. 😤

Tough decisions of life...

Day after Tomorrow will be my first day at my first job.

Any advice ??

> finds awesome front-end design software
> build a decent layout
> adds Phalcon stuff (started to use that a few days ago, works really nicely, just don't like the ORM as much as Propel2)
> software can no longer display the site layout properly

FML

<opinion>
You may be a prod ninja but I believe that every dev should have a decent level of exposure with a low level language(s). Sure you can make an HTTP server, do a sentimental analysis, topic modeling, set up multinode clusters, write ORM queries from dbs and all sorts of awesome stuffs with Python/Ruby/PHP/JS/GO etc but none of them teaches you what happens at kernel level. Things like memory leaks, threading, multiprocessing, memory allocations etc can only be better learnt from a low level language.
</opinion>

P.S. Not a C/C++ fanboy. I'm a python dev 😄

It is time for my own dumbass's favorite pastime: not letting go on retro tech.

I am gonna build a small and complete RESTful web API with Vbscript and Classic ASP with errrthing thrown in this mfker including JWT authentication and i am gonna see how the idea of an ORM goes. I know that COM interop was a thing, dunno if it still is.

I am fucking bored. The graduate degree is killing me and I need a distraction.

Thinking about being a purist and keeping the COM libraries to be made with VB.NET :P

Fuck yeah for being a masochistic retard.

I legit love vb net tho

Our HR will contact you soon.

Copy-pasting 90% of our entities including logic and merging some - creating thousands of duplicated lines - and then creating views for those abnomalies just to speed up the ORM fetching which could have been done with a single join...

Took me some time to delete all of that fking shitty untested code full of bugs...

Again someone testing in Prod

- become a system administrator (I am in final year rn )

- write a book (fiction)

I really hate PHP frameworks.

I also often write my own frameworks but propriety. I have two decades experience doing without frameworks, writing frameworks and using frameworks.

Virtually every PHP framework I've ever used has causes more headaches than if I had simply written the code.

Let me give you an example. I want a tinyint in my database.

> Unknown column type "tinyint" requested.

Oh, doctrine doesn't support it and wont fix. Doctrine is a library that takes a perfectly good feature rich powerful enough database system and nerfs it to the capabilities of mysql 1.0.0 for portability and because the devs don't actually have the time to create a full ORM library. Sadly it's also the defacto for certain filthy disgusting frameworks whose name I shan't speak.

So I add my own type class. Annoying but what can you do.

I have to try to use it and to do so I have to register it in two places like this (pseudo)...

Types::add(Tinyint::class);
Doctrine::add(Tinyint::class);

Seems simply enough so I run it and see...

> Type tinyint already exists.

So I assume it's doing some magic loading it based on the directory and commend out the Type::add line to see.

> Type to be overwritten tinyint does not exist.

Are you fucking kidding me?

At this point I figure out it must be running twice. It's booting twice. Do I get a stack trace by default from a CLI command? Of course not because who would ever need that?

I take a quick look at parent::boot(). HttpKernel is the standard for Cli Commands?

I notice it has state, uses a protected booted property but I'm curious why it tries to boot so many times. I assume it's user error.

After some fiddling around I get a stack trace but only one boot. How is it possible?

It's not user error, the program flow of the framework is just sub par and it just calls boot all over the place.

I use the state variable and I have to do it in a weird way...

> $booted = $this->booted;parent::boot();if (!$booted) {doStuffOnceThatDependsOnParentBootage();}

A bit awkward but not life and death. I could probably just return but believe or not the parent is doing some crap if already booted. A common ugly practice but one that works is to usually call doSomething and have something only work around the state.

The thing is, doctrine does use TINYINT for bool and it gets all super confused now running commands like updates. It keeps trying to push changes when nothing changed. I'm building my own schema differential system for another project and it doesn't have these problems out of the box. It's not clever enough to handle ambiguous reverse mappings when single types are defined and it should be possible to match the right one or heck both are fine in this case. I'd expect ambiguity to be a problem with reverse engineer, not compare schema to an exact schema.

This is numpty country. Changing TINYINT UNSIGNED to TINYINT UNSIGNED. IT can't even compare two before and after strings.

There's a few other boots I could use but who cares. The internet seems to want to use that boot function. There's also init stages missing. Believe it or not there's a shutdown and reboot for the kernel. It might not be obvious but the Type::add line wants to go not in the boot method but in the top level scope along with the class definition. The top level scope is run only once.

I think people using OOP frameworks forget that there's a scope outside of the object in PHP. It's not ideal but does the trick given the functionality is confined to static only. The register command appears to have it's own check and noop or simply overwrite if the command is issued twice making things more confusing as it was working with register type before to merely alias a type to an existing type so that it could detect it from SQL when reverse engineering.

I start to wonder if I should just use columnDefinition.

It's this. Constantly on a daily basis using these pretentious stuck up frameworks and libraries.

It's not just the palava which in this case is relatively mild compared to some of the headaches that arise. It's that if you use a framework you expect basic things out of the box like oh I don't know support for the byte/char/tinyint/int8 type and a differential command that's able to compare two strings to see if they're different.

Some people might say you're using it wrong. There is such a thing as a learning curve and this one goes down, learning all the things it can't do. It's cripplesauce.

Amen...

body {
overflow-x: hidden;
}

is a bit like trying to fix a broken arm by wearing a long sleeve shirt 😅

This moment when someone mentions you in an PR of an huge ORM clusterfuck with associative tables and discriminators...

And you accidentially say "Yes I'll look at it later" because you thought it was an tiny PR -.-

Should have opened that link first.

These fuckin morons piss on the toilet seats. They should get potty training also. Chutiye Saale!

Hello fellow devs, how do you clear your mind when you cant make something work? I think most of you had this feeling like 'fuck that, creating from beggining will be easier'

hunting bugs less than 24hrs. before delivery... OH JOY!!!

I might be pushing my 4 years old macbook pro too hard with 2 IDEs, 1 instance of datagrip, and tons of open browser tabs, all on 4gb of RAM..

better than beer? bug hunting with beer!

Well, this is not my cup of tea..

I remember the era when the first suggestion to every problem was:

REBOOT THE SYSTEM

The first 30 minutes of a working day often consist of me saying, "who broke this then?" Then a liberal use of git blame.

To all the people who complain about writing a delete or update query. Not to talk you down, but seriously. STOP WRITING RAW QUERIES AND USE AN ORM!

*last call POST Breakup*

She : make a PROMISE, no CALLBACK!

Me: Got it.

*That's how it started*

I discover last week Eloquent ORM.
A php database abstraction layer.
How to make things quickly! Great tools!

Good knowledge of ORM tools like web services and XML? Really?

Here comes your millennial diagnosis of a hype word filled architecture and how its affecting me:

I was diagnosed with a mentally and socially crippling degree of OCD at a young age. As I got older and away from areas that contain hundreds of people on daily basis, my tendencies resided but still manifest themselves in lesser ways. Over the last 8 years of development, I've taught myself to steer these compulsive tendencies into the art of software architecture and code quality.

Over the last 3 years Ive become more obsessed with the concept of designing agnostic, pluggable pieces that are weighed down by very few dependencies. I had not read any books on pluggable architecture or dove deep into what SOLID means to me. It just "naturally" felt like an evolutionary step in where my software quality needed to go. I had never approached microservice architecture and at the time knew little of it so instead I went as far as breaking php or node components up into their own packages on npm/packagist. Making packages of them was as far as I could go to assure my components were entirely plug and play. It helped my mind understand them as separate entities and devs after me know that they in no way could depend on my core suite of services.

Then I ran into this "Clean architecture" book and my initial reaction through out it was "hmm, this is a much better way of achieving what I've organically been coming to". Inverted dependency was new to me. I had heard it a thousand times but never put it to practice. I approached agnostic behavior by much harder means of separating binaries into their own address spaces or combining them from different binaries to run in synchrony. The idea of pushing hard decisions off and separating concerns through interfaces was an eye opener but my it still does not solve the issue of monster repos.

I don't understand how teams allow services to grow exponentially with little check and Idk want to know. It doesnt take a principle dev with 20 years experience to say "this shits starting to get out of hand, lets split it". The minute you are forced to use your IDE's global search to work efficiently within the code base, it's too late. As silly as separating a project by npm packages sounds, it still was just a logical means of breaking up something far too complex so that it doesnt get in its own way.

Then came micro-services or my final realization of it. Ive found a perfect placement that satisfies my own compulsion for cleanliness between the principles of clean arch (or onion, or port arch) and service oriented arch. Teams work well within small codebases. They work well with low dependencies. They work well in a suite of services that can be plucked and rewritten without cascading dependencies to consider. Teams work well when given hard http specs to abide by when talking with other services or with a gateway.

Now someone tell me where in the flipping fuck I can work where these architectures are taken advantage of. Ive been through 3 companies in three years and each has been a shit show of monolithic web apps, mono api's. Shit our last suite thats now sunsetted was 600k lines of vanilla php, no framework, no orm, different approaches to architecture that did not unify, high dependencies, one repo.

The biggest thing coming out of that for me was knowing what I despise in architecture. Having these horror stories to pass on forever when discussing our bright futures. Im rambling now but I suppose that becomes the closure needed for this ted talk. Going through hell and coming out with a lesson learned. Feeding my mental disadvantages in life with best practices in my career.

Are people using Vim doing it for the sake of it? Is there such a thing as a Vim hipster?

I mean, nano is just nicer 😇

I like this motto...

Using Sequelize after years of using Entity Framework is like going from a space shuttle to a kite.

I once found a bug that I couldn't figure out from the code, so I started putting log statements that would print out the variables on screen (yes I have xDebug, but old habits die hard). Then the entire website didn't load anymore and eventually the entire container crashed.

It took me an hour to realize I was trying to var_dump an object from the ORM, resulting in a memory overload since there were like 20 related objects that recursively tried to load all the data in the database.

In my defense, it was friday afternoon...

Service's like freelance and people per hour are a farce. It's just a constant race to the bottom price-wise.

'Yeah sure I can make you a blog website in 24 hours for £5'

Desk fans whirling. Sweating co-workers. An extra short stand-up.

That's right, the English summer has arrived.

I fucking HATE ORMs. Fuck this bullshit, they always have some use case that is stupidly difficult or obscure that no one knows how to deal with because the creators didn't think of the one thing I want to fucking do.

Screw this bullshit, homebrew SQL is ALWAYS the way to go; I've never encountered an ORM that didn't turn in to a troubleshooting, dialect-learning timesink.

I love how our industry has invented such important sounding yet meaningless job titles...

Developer, software engineer, software architect, developer evangelist, dev ops engineer, systems analyst, quality assurance engineer, code monkey...

I don't know why... But I cringe when somebody says "coding", "coder". Maybe it's because it's an Americanism...

Don't people learn the basics of how things work anymore ?!

I am cleaning this project, where some juniors have implemente a lot of the code.

Apparently, the way of deleting an entity from the database is:

1) SELECT the entire row and cast it to a model class

2) CONVERT that model class to a DTO class

3) READ the Id property from the DTO class

4) SELECT the entire row, again, and this time cast it to a DTO class

5) CONVERT that DTO class to a model class

6) Use you pancy-pants ORM delete method using the entire model class as input argument..

FUCK YOU !

inb4 what about reference checks ?
- Nope. That is done separately using only the Id

inb4 what about checking if someone else has altered it before deleting
- Nope, the entire entity is not used for that either.

whats your biggest aha-experience learning about programming? mine was probably finally realizing what an orm does and how it eliminates your need need to write sql manually

Age+=1

First time, I am this far from home on my B'day. But atleast I am with my friends and these fuckers wrote "Antarvasna writer" on my cake.

npm install yarn

I feel guilty...

When I have to be responsible for shit that others do.

When a university student approaches you, to do their coursework for them! 😡😓

My manager always tell that we're less process oriented and self sufficient.

Later on, I understand what that means
- Poorly written JIRA tickets
- JIRA tickets with only title, rest for you to fill
- Two teams did same task, client side team pushing their change directly on master, while mine still waiting on code review will eventually get rejected
- Client writing raw SQL in ORM framework instead of using any single feature of ORM.

The lead developer is away this week, what will I do if somebody asks me for a deadline 😰

Created a docker stack that can run on a swarm, tried out an actor system framework with a really nice message passing interface, used a web server framework built on that actor framework, used a really cool ORM that relies heavily on code generation, did some experimenting with Alpine Linux, and re-learned for the 100th time how to deal with CORS

Python file truncate instead of actually deleting file contents...
there goes a weekend of log backups.. FML

Brewmaster.
I've been brewing my own beer for about 6 months now and super positive feedback keeps on coming :)

I wonder what is going on in the minds of inexperienced developers. It must be very interesting.

I just read this bit of code
The task was to implement a certain schema into a database. They were given an ORM library, and several tutorials explaining what an ORM was and how it did it.

The result were these 3 models:
- A defaultUser with all of the defaults values for the User model. It wasn't even supposed to be instantiated, just accessed by `defaultUser.fields.username.default`
- another default table for another model.
- The "main" model, containing all other models in the form of JSON fields that would contain an array with other JSON objects that would represent the instances themselves.

I will say though, they made a home-brew ORM with (most of) all the logic a normal ORM has by parsing through the "main model", except, of course, common sense

developer oriented saas? well yeah, you could've at least develop a decent SDK for one language, or just let people send JSON payloads instead of XMLs..a**holes

I think I need to work a little to rest from my family vacation

Support for an app that long handed over. This time, a customer is supposed to be deleted. The client probably wants me to delete the customer from the live database.

Why can't he delete the customer himself? Well, the button is disabled. And apparently, he doesn't want to pay for my time to figure out why the button is disabled. Or that's normal, who knows. I don't know the app.

I open up the database. Try to generate a model of all connected tables to the customer table. No luck. The tables aren't connected, the ORM handles relations. I hate that. Probably have to go through and delete all of those manually in a live database. Argh!

Okay, let's see why we cannot just click the button. Alright, yeah, there is a disabled on the button. Hmm... I wonder. Removed the disabled in the web browser inspector and hit the button. Seconds later, the entry disappears from the database.

My predecessors were sloppy. Probably thought it's the admin menu. We don't have to protect our customer from himself.

That just saved me a lot of time.

11:30AM is NOT the best time to vacuum around here!!!!

Writing a design document.

So I developed this proxy server that will throttle down API calls to one of our providers so we don't get blocked for TOS violation...
Some dude had a tool running all day long which crashed 2 minutes before I left work.
This literally ruined my day until I recalled it's all cached!!!!
Mood is back again and I deserve my beer!

My work product: Or why I learned to get twitchy around Java...

I maintain a Java based test system, that tests a raster image processor. The client is a Java swing project that contains CORBA bindings to the internal API of the raster image processor. It also has custom written UI elements and duplicated functionality that became available in later versions of Java, but because some of the third party tools we use don't work with later versions of Java for some reason, it's not possible to upgrade Java to gain things as simple as recursive directory deletion, yes the version of Java we have to use does not support something as simple as that and custom code had to be written to support it.

Because of the requirement to build the API bindings along with the client the whole application must be built with the raster image processor build chain, which is a heavily customised jam build system. So an ant task calls out to execute a jam task and jam does about 90% of the heavy lifting.

In addition to the Java code there's code for interpreting PostScript files, as these can be used to alter the behaviour of the raster image processor during testing.

As if that weren't enough, there's a beanshell interface to allow users to script the test system, but none of the users know Java well enough to feel confident writing interpreted Java scripts (and that's too close to JavaScript for my comfort). I once tried swapping this out for the Rhino JavaScript interpreter and got all the verbal support in the world but no developer time to design an API that'd work for all the departments.

The server isn't much better though. It's a tomcat based application that was written by someone who had never built a tomcat application before, or any web application for that matter and uses raw SQL strings instead of an orm, it doesn't use MVC in any way, and insane amount of functionality is dumped into the jsp files.

It too interacts with a raster image processor to create difference masks of the output, running PostScript as needed. It spawns off multiple threads and can spend days processing hundreds of gigabytes of image output (depending on the size of the tests).

We're stuck on Tomcat seven because we can't upgrade beyond Java 6, which brings a whole manner of security issues, but that eager little Java updated will break the tool chain if it gets its way.

Between these two components we have the Java RMI server (sometimes) working to help generate image data on the client side before all images are pulled across a UNC network path onto the server that processes test jobs (in PDF format), by reading into the xref table of said PDF, finding the embedded image data (for our server consumed test files are just flate encoded TIFF files wrapped around just enough PDF to make them valid) and uses a tool to create a difference mask of two images.

This tool is very error prone, it can't difference images of different sizes, colour spaces, orientations or pixel depths, but it's the best we have.

The tool is installed in both the client and server if the client can generate images it'll query from the server which ones it needs to and if it can't the server will use the tool itself.

Our shells have custom profiles for linking to a whole manner of third party tools and libraries, including a link to visual studio 2005 (more indirectly related build dependencies), the whole profile has to ensure that absolutely no operating system pollution gets into the shell, most of our apps are installed in our home directories and we have to ensure our paths are correct for every single application we add.

And... Fucking and!

Most of the tools are stored as source bundles in a version control system... Not got or mercurial, not perforce or svn, not even CVS... They use a custom built version control system that is built on top of RCS, it keeps a central database of locked files (using soft and hard locks along with write protecting the files in the file system) to ensure users can't get merge conflicts by preventing other users from writing to the files at all.

Branching is heavy weight and can take the best part of a day to create a new branch and populate the history.

Gathering the tools alone to build the Dev environment to build my project takes the best part of a week.

What should be a joy come hardware refresh year becomes a curse ("Well fuck, now I loose a week spending it setting up the Dev environment on ANOTHER machine").

Needless to say, I enjoy NOT working with Java. A lot of this isn't Javas fault, but there's a lot of things that Java (specifically the Java 6 version we're stuck on) does not make easy.

This is why I prefer to build my web apps in python or node, hell, I'd even take Lua... Just... Compiling web pages into executable Java classes, why? I mean I understand the implementation of how this happens, but why did my predecessor have to choose this? Why?

I want to develop a django quiz app which will show questions to all online users at same time and allot a short time slot(1min) for answering questions.

How can i do that?
Any kind of help/link/hint is appreciated.
Thanks in advance.

Just spent a lot of time on custom building an Ubuntu docker container, and forgot to save the image before I accidentally reset the whole thing to blank

When your VP Engineer says we DONT NEED AN ORM.

Raw sql queries are just fine and he even can help with that!!

It's only monday.

Two senior developers were baffled at why their Web application built using sql server wouldn't just instantly work using sqlite... The Web application uses some pretty advanced queries and ORM.

I hate computers and computing things, sometimes

I HATE WINDOWS' WINDOW MANAGEMENT. I have two monitors and nothing can be maximized. Windows' spaces are terrible as well.
I am building in the back end in VS Code.
I have three terminals open because I need them to run multiple parts of the app locally.
I have postman open to try requests.
I have firefox for the orm system's documentation.
I have my database tool running as well.
I have an ERD diagram floating in a window.
I have another VS Code window showing a diff of my JSON compared to the version I'm replacing.
Also all of my team communication tools.

I have never hated shuffling windows around so much. Would it kill us to use some command line tools for http instead of Postman? Could we please get a decent shell in windows? Could we get some simple ways to switch between virtual desktops? Click click click. I can't automate clicking. Why do we use the most clicky tools we can find?

No proper normalization and database structure practices seems to continue to be the bane of my fucking existence at work.

One would think that it would be the quirks carried through by the language stacks in question, those are fucking absolutely ridiculously horrible by the way, y'all think you've seen bad Javascript and PHP? these would make you cry, laugh, wonder in amazement and then fucking pity me and eventually buy me a beer NO JOKE.

Y'all think you have seen some obscenely unoptimized SQL code? think of the worst fucking possible output from the shitty-est most error prone boundary checking inefficient ORM out there and multiply it by 10k. Then refer to my other point, and do the same thing for me which culminates in alcoholic consumption.

Worst thing? the developer that wrote most of this is a college level TEACHER rn....i've met the smug piece of shit, he acted severely condescending to everyone around him and I just smiled because I know how much of a piece of shit he is.

The other dude in question (it was two of them that I am talking about) left for another city and currently holds a senior developer position....i-fucking-magine that.

Fuck I hate these mfkers and I really wish they gave me a chance to fucking blow up on them.

Im fucking fed up with overbloated "all in one" ORMs.

For shit I cant find simple ORM that would literally just do fucking CRUD for me.

Thats all I require for some small project, yet still for few tables I have 2 choices:
a) do it without ORM and write models with raw SQL (which I usually end up doing, as its just more fault tolerant and works better)
b) install overloaded ORM that I wont use even 1% of features

Guys, why the fuck nobody created anything small, tiny and yet usefull? I know my SQL sucks and that is reason I want to use ORM in the first place. But when Im just forced?

Best what I found in terms of ease of use, and beeing not too heavy was RedBeanPHP.

A freaking ORM that will create database on the fly. It's awesome, sure. It's usefull, sure.

BUT STILL ALL I NEED IN SMALL PROJECT IS 1% OF THAT FUNCTIONALITY.

Does literally every single ORM dev want to feel their dick when they list out features list?

There should be allways proper tool for proper job. Its like using symfony for creating onepage website with contact form. WTF.

The project my company agreed to work with 1 year ago is totally shitty.

We basically use Python 2, Tornado, MySQL and driver for it from 2005, custom made "ORM" where you have to write SQL in strings in Python, custom asynchronous service that runs jobs and all such...

The rest of the team writes code really badly and only after a year of fucking with this shit we made them do pull requests.

I became totally neurotic because of the shit I have to go through daily at work. I do not develop myself, no new things I have learned in the past year or so. What do I do, devrant? What is your advice?

Going over some NodeJS code, and I feel like the scene from "Dude Where's My Car" - "And then....And then..."

Coming from almost three years of 99% python, this hurts my eyes so much

I fucking hate people who uses complex words to describe something simple.

Describing a frame work

Show-off : "..you can define what objects/tables to expose, what values in that object you want to expose...if you are using some orm, then because you have models defined. Once you update your model, your endpoints get the new model..."
Simpleton : "something like parse..."

Wtf is 'fixedUUID'?

Show-off: "..hardcoded UUID is fixed (constant) value, with format of UUID, hardcoded UUID will be unique value between backend and frontend,
you will need to store it as constant value in your codebase ( we may encrypt/ decrypt it for security reasons)..."
Simpleton : "a secret password only u & I know"

--why whyyyyyyyyyy

During my internship, I fixed a bug in android app related to user data updation..

BUT I didn't knew it's root cause and I have no idea how I fixed it.
Also, it was satisfying.

Dreading the end of this bank holiday weekend, tomorrow I must wake up and return to working with legacy code.

!python/ORM

Someone got quality tutorial/blog about Sqlalchemy ?

Even tho I am dealing with py+flask+sqlalchemy last 3 years I am still able to get super confused about contexts/syntaxes.

(Model.query vs session.query(Model), etc.)
😪