After listening to two of our senior devs play ping pong with a new member of our team for TWO DAYS!
DevA: "Try this.."
Junior: "Didn't work"
DevB: "Try that .."
Junior: "Still not working"

I ask..
Me:"What is the problem?"
Few ums...uhs..awkward seconds of silence

Junior: "App is really slow. Takes several seconds to launch and searching either crashes or takes a really long time."
DevA: "We've isolated the issue with Entity Framework. That application was written back when we used VS2010. Since that application isn't used very often, no one has had to update it since."
DevB: "Weird part is the app takes up over 3 gigs of ram. Its obviously a caching issue. We might have to open up a ticket with Microsoft."
Me: "Or remove EF and use ADO."
DevB: "That would be way too much work. The app is supposed to be fully deprecated and replaced this year."
Me: "Three of you for the past two days seems like a lot of work. If EF is the problem, you remove EF."
DevA: "The solution is way too complicated for that. There are 5 projects and 3 of those have circular dependencies. Its a mess."
DevB: "No fracking kidding...if it were written correctly the first time. There aren't even any fracking tests."
Me:"Pretty sure there are only two tables involved, maybe 3 stored procedures. A simple CRUD app like this should be fairly straight forward."
DevB: "Can't re-write the application, company won't allow it. A redesign of this magnitute could take months. If we can't fix the LINQ query, we'll going to have the DBAs change the structures to make the application faster. I don't see any other way."

Holy frack...he didn't just say that.

Over my lunch hour, I strip down the WPF application to the basics (too much to write about, but the included projects only had one or two files), and created an integration test for refactoring the data access to use ADO. After all the tests and EF removed, the app starts up instantly and searches are also instant. Didn't click through all the UI, but the basics worked.

Sat with Junior, pointed out my changes (the 'why' behind the 'what') ...and he how he could write unit tests around the ViewModel behavior in the UI (and making any changes to the data access as needed).

Today's standup:
Junior: "Employee app is fixed. Had some help removing Entity Framework and how it starts up fast and and searches are instant. Going to write unit tests today to verify the UI behaivor. I'll be able to deploy the application tomorrow."
DevA: "What?! No way! You did all that yesterday?"
Me: "I removed the Entity Framework over my lunch hour. Like I said, its basic CRUD and mostly in stored procedures. All the data points are covered by integration tests, but didn't have time for the unit tests. It's likely I broke some UI behavior, but the unit tests should catch those."
DevB: "I was going to do that today. I knew taking out Entity Framework wouldn't be a big deal."

Holy fracking frack. You fracking lying SOB. Deeeep breath...ahhh...thanks devRant. Flame thrower event diverted.

Being on devRant genuinely scares me. I mean, I know C#, Entity Framework, basic SQL, basic HTML (who doesn't?) and some Angular, but most people here know so,so much more. Maker me feel quite dumb :/

Assigned to a new project team..

Using git, in a creative way. So.. "master" is "dev" branch, usually. Everyone can push their branch to dev server .. so it's "dynamic for us". Production branch is whatever, as long as the branch has the release version. Sometimes, the release comes from "master".. that mean "dev" in normal geek..

That's just Git. The source code is a saturated spagetti of Entity framework and Caliburn. It is littered with antipatterns, especially basebean. Holy Christmas and Easter that baseclass do a lot of stuff that has no place as a base class ..

Fucking frameworks, I'm gonna start to evangelize frameworks as the no1 antipattern.

MS SQL as the main DB, but is dumped to json FILES through a scheduled task to increase read performance on web.

There is a soap endpoint to expose the json files, fml..

I am assuming I was placed here to improve stuff, I have never in my life seen anything like this before.

There is a special place in hell for this repository

Entity Framework Core Mapping LOL

I'm a "published" freelance dev!

Last night I made my first web application available to the internet. It's an internal enterprise management system for a small non-profit.

It's running on a single $6 a month digitalocean droplet, and the domain is $12 a year, so yearly cost for them is absolutely rock bottom.

It's written in asp.net 6.0 razor pages, nginx reverse proxy, certbot for HTTPS certificates, fail2ban for ssh protection (ssh login is via ssl keys), entity framework with MySQL.

The site itself has automatic IP banning based on a few parameters like login spam, uses JWT tokens, and is fully secured.

All together, it's a lot of value for about $100 a year.

Big rant.
Just finished my first year of uni. I took an extra course on c# (mvc, entity framework) and android development in java. We learned a lot of stuff and at the end of the semester they held a contest. We had to develop an app respecting their specifications and add something from ourselves for extra points. Problem was that we were supposed to work on the project during our finals, which we didn't, finishing uni is on the first place. But we had a week after finals to work on it. I, like many others, slept very littlre during that week, only to work on that app, I worked for more than 13 hours a day to finish it (it was a pretty big app) and I was pretty happy with the end result. Today they were supposed to announce the apps that made it to the final. They just announced that no app deserves to be in the final. They know that we had finals, but that we could still do better. They just peed on our work, probably threw our code away, fucking +13 hours a day, 5-6 hours of sleep everyday, almost no fun for a whole week after finals, and they think no one deserves to win. Fuck them, fuck their shit contest. Fuck you essensys, I hope your devs read this, fuck you bell ends.

Useful as fuck

Not an enemy yet, but I’ve just debated with a senior dev that said stored procedure is faster, safer, and works better than entity framework

I agree with faster (only a bit) but the rest is just bs

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 ?

So I started in a new job a week ago for a two weeks probation period, im getting payed double than my last job but it's so professionally frustrating.

They use a full php stack with a framework called tinymvc that I never heard of and the last commit is from 2009.

Beside this they implement some sort of "flexible" MVC where a great amount of the logic are inside the views. They have one model for each entity (in theory) but in reality one model have methods for a lot of tables.

Beside this the i18n is done by querying the database for all the translation strings and copying it in every user session, so every session file it's about 400kb where around 380 are duplicated translations.

The views folder is empty because they decided to modify the framework to look for the views in another folder called resource's and the development must be done connected directly to the production database

Above all this shit all the many-to-many relations in the database (MySQL) are handled creating a comma separated field on one of the tables, completely breaking the reference integrity.

So, after a week of work I can't stop thinking who the fuck developed this? In which world this shit is okay? How can I work around this big lake of shit?

When I was around 13 I started programming html and designing websites on and off over the years. Later during my first year of college I picked up C++ and loved it. I always had this idea that web design was very elementary programming until recently.

I recently got forced into learning C# and ASP.NET Core MVC by my internship. Holy shit was I wrong. Web design is so insanely complex and interesting!

C#, ASP.NET Core MVC, HTML, CSS, JS, Entity Framework Core, and the list goes on.....all to create a single website/web application.

I apologize for my ignorance to the website development community.

I’m so excited to learn all of this! =D

What EF thinks the singular of AttendanceLeaves is

I don't always fight with entity framework, but when I do

I inject raw SQL

Fuck entity

Too lazy to implement DB Transaction. I hope I won't get fired for this.

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.

Worst thing? Absuse LINQ and not in a fun sexy way.

Entity framework > check.
LINQ query > check.
Standard IEnunerable magic > check

The developer had decided that it would be a good idea to thread the enumerable all over the place and collapse it anytime they wanted access to the data.

I know it’s a rookie mistake a lot of people make, but it was some pretty core data that ended up being used all over the place, so it was a nightmare to correct and it really impacted performance.

Needless to say they felt very silly when we explained how LINQ was deferred.

Most recently... taking something previous devs had failed at and knocking it out of the park.

Best example was a statistical regression and graphing tool on ASP MVC.

The devs were doing a massive brute force recalculation on the server layer. It would take 24h then fail to save (Entity framework brute force).

We moved it to the database layer and got it down to a passable time.

The same devs were outputting charts to ie 9, chrome, firefox... same deal, half an hour on the initial request (parser churn in the browser)... then failure.

Again got it into a passable time by switching to web sockets and long polling then outputting 1000 or so points at a time to give the browser time to render.

Taking those two cock ups and making them a workable solution was awesome.

Since then, teaching. We have apprentices, newcomers, interns all jumping in and looking to get working. They're all different, what works to teach one person won't the next, each of them so far has caught on to what I was teaching. It's a proud moment to be able to impart knowledge and see someone pick it up, enthusiastically... it's also awesome to see someone excited about what you do.

Detour

Last day of agile project i get asked for confirmation that the alpha system can handle 100000 records. We have had no load testing requests only feature pushes every sprint.

I see the back-end guys have used EF in a search function that eager joins a bunch of tables. Then the results get sorted and filtered in application code. It works fine for a few hundred records but the customer will do about 100k new records a year.

Yeah this won’t meet requirements. I wish they asked for some load testing before the last day. They aren’t going to like that one person can do a search every 15 seconds by the end of the year when I tell them. FML

STOOOOP TELLING ME THE TABLE DOESN'T EXIST. YOU'RE FUCKING SUPPOSED TO CREATE THE DAMN TABLE NOT TELL ME IT DOESN'T EXIST! YOU FUCKING DID IT AT HOME ON MY DESKTOP SO WHY DO YOU DO THIS TO MEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEeeAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Spending hours upon hours trying to understand C# entity framework relational data mappings, going to the extreme of looking at LINQ queries, writing and rewriting over 100 lines of code only to find I needed to write the joins in dot notation on the include!

When you add a bunch of entity framework relationships in code, and it works the first time... Wtf.

!rant

Wrote an literal assload of stored procedures for my DB.
Got introduced to Enitity Framework.
My brain just exploded with rainbows and possibilities :D

Not to mention it feels so much cleaner :v

So we’ve taken over from a project team that disbanded... read: “cut their contracts because fuck this, I can earn more working for better people”.

Me and one other guy have been tasked with saving this heap of shit.

Obviously the project guys left saying “it’s nearly done, just this one feature”. Because cut contracts are easier to deal with if “everything is almost done”.

We jump on and find that’s not the case at all... this thing, is a beast, a big old stats analysis program... so we’re like “cool, let’s see what’s going o...OH MY GOD”.

The “recalculation” function was core to this POS. The contractors had done it in C# through entity framework... it took 24 hours to run, over a reasonably small data set that was due to double every 2-5 years.

So... here’s the deal, it ran over night.... then failed. And no cunt had noticed. Entity framework “can’t commit because I’m muddled up as fuck, did you really just put the whole db in EF in memory to work with it?” Exception.

Que 6 months of me and my lead doing the job properly.

Anyway, the failure: I ended up in Hospital again with a Crohn’s flare up... about 5 months in.

Fuckall to do with all this nonsense I just wanted to tell a story. it was an interesting/fun project to fix and my lead was a legend... so happy days.

Similar story, different set of contracted devs... they’d been defining requirements with the business users using the term “Risk” which the business users knew as a group of risks.

The domain model had been written RiskGroup<>—

New day. New legacy project that needs triage.

The project has existed since before 2000 so it all "works" and has no known business logic bugs. It does however have performance issues which sure I can have a look. It can actually be quite fun and rewarding to optimize performance.

This is a titanic dotnet framework leviathan consisting of over 12,000 cs files using razorpages, entity framework, and... nhibernate? I have my gripes with both EF and NH but they are both fine if used correctly, like any other tool. I've never seen them used together however.

As It Turns Out™, NH was implemented first and at a time when NH did not support async operations. It made sense if you look it up and it's meant to delegate commands via a separate layer, but different story.

Then for... reasons... EF came in and gradually took over.

Because of the way this is all set up, everything will faceplant if you try doing anything async, even if it has nothing to do with calling the db. Any attempt in making this work leads you down a slippery slope of having to rewrite the entire thing, which is out of the question in terms of their budget and expectations.

Sometimes it's a detriment when it works in spite of its issues.

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

I spent a whole day trying to debug why the backend would stop sending data after a while (-> it filled up its connection pool)
but after I turned pooling off, there were a number of dangling Client-Idle-Read DB connections
//not using Entity Framework in these N services, it's pure SQL and DB-AccessLayer here

Never happened before, looked up conf, looked up SO
Changed connectionClose to mandatory Dispose
Still didnt work.

long story short. Turns out in 1 of the services, the DataReader to POCO static method, was disposing/closing the READER and not the CONNECTION.

I sent it as tuple instead of 2 separate variables (reader, connection), and the Item1, Item2 got mixed up (:

Totally my fault, and imma avoid name-less tuples from now on like they a plague -.- thats my 2024-resolution

Forced ASP Identity Claim refreshes by abusing the login partial.

I am now going to attempt the problem solving ritual.
Requirements:
-have a problem or piece of unoptimized code and you don't know how tk fix/improve it
-be able to sleep/take a nap

Now before I fall asleep the ritual should provide me with an epiphany to solve my problem

Plan b:
I have a class ninja (model), with an observablecollection<property> properties and an observablecollection<gearslot> gearslots;
,a class gear with an observablecollection<property> properties and an Category category:
And a class gearslot with a Gear gear and a Category category;
Via entity framework this results in several property entries per ninja
And several property entries per gear item

All good so far.

I now actually want the ninja property values, to be the sum of the gear property values

So a ninja has int, agi and str of 0.
Gear has 0 or more stats.
If the ninja has two pieces of gear on with agi +1, then the ninja agi should be 2

If possible i would like the logic in the model.
Else i have to put it in the viewmodel.
That i can figure out, its just so inelegant....

I love getting an immediate response on GitHub for Entity Framework Core issues from Microsoft.

was working on a project once where we needed a database mapping to some c# code
tasked one of our less experienced guys on it to maybe give him some experience

now I'm assuming most people here who have worked in .NET for a reasonable amount of time know about entity framework, and I did tell the guy about it.

three days after giving him that task he comes up to me smiling and says he's done

great! what did he do? he wrote the database mapping from scratch using hard coded SQL queries using lists to chain queries together in a sea of if-else statements...

let's just say the code broke down and needed last minute fixing when it was time to present it

I so hate working with legacy db code! I wish I could migrate all to entity framework but the migration is a pain in the ass and would take hours which the client wouldn't like.

Entity framework driving me crazy.. but finally some decent result, but looking for < 100ms

Entity framework core!
I thought you would be cool, but I hate you!!!

Pretty sure Entity Framework is the worst thing invented for devs... So frustrating. Hey devrant, what's your tech stack? (Please don't say entity framework. Please?)

EF/asp.net core issue..
I've got a many to many relationship between idea and hashtag.
Currently i can POST an new idea with new hashtags just fine, but if i then POST a new idea, with the same hashtags, it tries to insert the hashtag again into hashtags on sql server, and fails since the hashtags should be unique...
What i expect of it is to just update junction table using the already created hashtag from first POST and create the new idea 😅

I fucking hate entity framework.
It turns 10 mins of work into fucking hours of stress and bloat and shit.

It’s the one thing in dotnet that I cannot fucking stand.

Literally did a bit of work in 10 mins (using ef I might add), but because it’s not the”ef way” I need to create an extra table/class and then fuck about mapping the relationship in a complicated way to do what I had just done in only a few lines of code with one table.

Spend over an hour trying to get it to understand the relationship before I gave up for the day. Fuck it

Any Unity3D devs out there?

My thoughts: Unity3D is an amazing game engine. It lets you really quickly go from concept to implementation and allows you to prototype very quickly. My concern is that I find it incredibly hard to write good code using it. It's very difficult to write in a test driven way, especially if you put any logic in a MonoBehaviour. It is possible to work around this by using Zenject or another DI framework. You could even use entitas which is an entity component system. But these all have their downsides too. Zenject I find to be quite boilerplatey and not that easy to test either. I also find it really frustrating to be using a really old very of C# (maybe C#4 equivalent but I think it's customised in some way for the engine).

Anyone else struggle to enjoy writing code for Unity3D games?

Today I (/ later together with some colleagues) spent almost 4 hours trying to improve a Entity Framework LINQ to SQL query.
The initial problem was, that one of our List API endpoints took longer the more you "page" (besides the long response time it had anyways).
So after
- brainstorming in the team
- brainstorming alone
- hacking around and
- shouting at screens
- googling
we
- got nothing optimized
- got confused about what EF does
- lost the believe in our development skills

So Entity Framework is really a nice thing. But as soon as you look deeper, trying to figure out what it really does between ToList() and "yeah my data arrived" it is just....demonic.

Unit testing Entity Framework.

Balls.

Dapper or Entity framework ?????

I underatand that Entity Framework makes things easy when it works. But when it doesnt, it is the worst thing ever. And it works less often than it should. THANK YOU FORMER EMPLOYEE FOR LEAVING US WITH A SYSTEM THAT HAS A MIND OF ITS OWN.

Not ranting. Just wonder, dapper + repository pattern, a good idea? And how it relates to unit of work? As dapper doesnt have iqueryable like entity framework has. C# dev ranters, enlighten me, show me the way 🐒💡💡

Pardon the rant; some of it can probably attributed to me, but please indulge me of you could.

I'm tasked with creating a report that pulls data from some sql tables in c#and presents it using javascript. My manager was nice enough to lend me his old sql query, so I run with that using sql connections. Now I find out AFTER I get my sql query string working and retrieving data properly that my manager wanted it done using linq and entity framework, so now I have to start over, a process made only more "fun" by the confusing and unintuitive column names of our sql tables.

Moral of the story: don't take the easy way out.

After I spend some time fixing that up, I have to print out the data using javascript and html, which my manager was kind enough to lend me. Cue me shutting off my brain and thinking that I should have the program open and display this stuff itself. Let me tell you that converting a console application to a Windows form application is not a fun experience, especially when entity framework makes classes named "application" and "form" from your database tables. After finally getting the WebBrowser form to work, I'm hit with a javascript error from the library my manager referenced (he is a programmer himself). I tell him about the error and he just tells me to write the html code to a .html on disk like he did, but never explicitly said he did until just now.

Fixed moral of the story: don't take the easy way out, unless you should.

I should clarify I was given the whole raw sql query and html with some embedded javascript and a reference to chart.js.

I started a project to practice and familiarize myself with SQL more and Entity Framework Core and prove how much I’ve learned from reading this book.

It was originally gonna be small program with a small database but over the course of me designing the database I thought of more features I could add. It’s been awhile since I’ve had a project and it feels good to have one.

Right now I’m only messing with SQLite but since the position I want to apply for asks for SQL Server I want to mess with that eventually.

My boss is a very smart man, but sometimes he's superstitious as hell. He cannot trust context.list.find() in c# to accept null values, despite that being a thing forever. He's certain that it will break in a future entity framework update, so we have all these duplicate if statements all over our site.

If(blah == null){ //stuff}
Thing thing = context.things.find(blah);
If(thing == null){//stuff}

It kills me a little each time, but I guess he could be worse. I'm glad that he's finally trusting the null conditional operator, because it's a fucking lifesaver for duplicate code!

My project setup:
-Entity Framework (Code first)
-Autofac (Dependency Injection)
-Asp.Net MVC C# with service layer pattern.

How is your setup? :)

I swear I touched some weird and complex programming shit in over a decade of programming.
I interfaced myself through C# to C++ Firmware, I wrote Rfid antennas calibration and reading software with a crappy framework called OctaneSDK (seems easy until you have to know how radio signal math and ins and outs work to configure antennas for good performance), I wrote full blown, full stack enterprise web portals and applications.with most weird ass dbs since the era of JDBC, ODBC up to managed data access and entity framework, cloud documental databases and everything.

Please, please, please, PLEASE I BEG YOU, anyone, I don't even have the enough life force to pour into this, explain me why the hell Jest is still a thing in javascript testing.

I read on the site:
"Jest is a delightful JavaScript Testing Framework with a focus on simplicity."

Using jest doesn't feel any delightful and I can't see any spark of focus and simplicity in it.

I tried to configure it in an angular project and it's a clustefuck of your worst nightmares put togheter.

The amount of errors and problems and configurations I had to put up felt like setting up a clunky version of a rube goldberg's machine.

I had to uninstall karma/jasmine, creating config files floating around, configure project files and tell trough them to jest that he has to do path transformations because he can't read his own test files by itself and can't even read file dependencies and now it has a ton of errors importing dependencies.

Sure, it's focused on simplicity.

Moreover, the test are utter trash.

Hey launch this method and verify it's been launched 1 time.
Hey check if the page title is "x"

God, I hate js with passion since years, but every shit for js I put my hands on I always hope it will rehab its reputation to me, instead every fucking time it's worse than before.

Fuck entity framework code first! It's a pain in the ass making relationships work with code first! 😑😑

Remind me again why we have to use/support a weird entity creating framework across all microservices? So that every entity is consistent? (Who cares? Microservices shouldn't) Because hibernate is hard? (It isn't, and it's better documented than this, which needs hibernate anyway).

I'm just building a fragile distributed monolith.

It's now 3am and this issue has been keeping me up for inner an hour... In Entity Framework..

I have a 2 tables/classes in a relationship: Item has many Tags.

I'm trying to delete some Tags using context.allTags.RemoveRange({list of tag objects I want deleted}) but now for some reason it's trying to reinsert/duplicate all Items and thereby violating all uniqueness constraints.

Guess will post the source code TMR but this is like wtf?

So I’m not having too much trouble with my project. Does that mean I’m doing something too easy or have I actually just absorbed the knowledge I’ve been reading?

I’ve never actually used EF Core before and I thought this would be harder, and more time consuming.

Good acronym for this stack?

Angular, . Net, entity framework, Sql

Dase (daze)? Never Sean one for this but mean and others around.

Forced to work with ASP.NET for a project. Not minding it though, even found it nice, kinda excited about .NET Core now.

HOWEVER, spent over 3 hours figuring out why can't I make a virtual property (Entity Framework actually provides proxy classes to be able to override behaviors of navigational properties, but I digress).

Says I don't have a type named 'virtual'. 3 hours in, no changes (git confirms), and IT SUDDENLY WORKS.

Fuck Visual Studio.

There needs to be a new (MOOC) class for people like me.

Hi, I'm William. I can't get my head around designing systems. I've read GoF and a few breakdowns of it as well. I find some patterns obvious for my field of interest (game dev, woot!) while I'm reading through the stuff, but have a pretty hard time retaining much of it. I'm aware of the danger of over using patterns, so I don't worry that much about it. I'll look something up when I'm sure I need it.

Still, I'm tired of the tutorial blues. I can watch a few different people write entire games, usually not in the language of choice, but that only helps me so much.

How do I fight scope creep? In the meantime, how can I make things extensible? Scope does need to creep some, after all.

People joke about starting with (visual) BASIC ruining you forever. I don't believe in that crap, but is this just denial? Am I too dumb for this? Not that I'd ever seriously blame a language for that.

I've been a hobbyist for well over 10 years, please don't make me count exactly how long I've been unsuccessful.

I'm baffled by Löve. I think it's the coolest shit I've seen, maybe ever (unless we're counting IPFS).

I think what really prompted this rant, apart from the obvious degradation of my mental health, was my search for an entity component system for Löve/Lua. Hold your replies. I know there's a few of them, and I'm positive that they're fantastic. I'd roll my own, but that requires actual Lua specific knowledge that I just haven't dug all that deep into yet. I can't wrap my head around the ones that exist, even though I can tell their complexity is next to none really.

I have severe tool anxiety, I'm shocked that I've stuck with ZeroBrane Studio as long as I have. It feels good though.

Sorry to use this as "Devs Anonymous", but I think that's how this community helps (me) best.

I feel like I should stop now and just say: Advice? before this gets much deeper/less readable.

So for awhile now I’ve been preparing myself for my first dev job as a .NET dev, and I’ve mostly just been polishing my C# knowledge with OOP, Entity Framework, ASP.NET and it’s been going really well.

So my self assigned time limit (end of August-beginning of September) is coming up and that’s when I’m gonna apply, so I decided today to take some time from programming to actually make my resume.

I did not use a template so it looks boring and I don’t have a lot to put on it but what I did put on it was important and I feel is solid (for not having worked before).

I’m having a few people I know look at it from a professional stand point and gave me feed back I implemented and it is better now.

I already linked my github, should I link my LinkedIn?

will people actually care if I don’t use a template to make it visually pop because I’d honestly rather keep it how it looks as is if I can.

Yesterday evening: committed my day's work to git. Tested everything and it all worked like a charm apart from a bug in my seeder I intended to fix today.

Today: failed to fix the error for 6 hours. Decided to go back to my commit from the day before only to discover now even my migrations won't work anymore.

Ready to smash my laptop

#whydoivencommit?

"Validation failed for one or more entities. See 'EntityValidationErrors' property for more details."
That really helps in my error log Entity Framework ❤

Any opinions on using Entity Framework vs Dapper for an API for a vue SPA Web app?
I have used both, and it seems it is a trade off of more control vs convenience.

I have about a dozen Entity Framework models to write and a webpage to get running (at least for a quick demo) by three but I guess now is a good time for Windows Updates.

I hate Windows. And it’s a company laptop so I can’t change the policies.

So I’m sitting here twiddling my thumbs unable to work.

I'm going insane.

So let's say you have an object in database, with 20-30 related objects (Or lists of objects) (All related objects have a foregn key to the "main" object).

Now, as long as you just edit/create thinga everything is fine.

But the deletion... Oh MY GOD

"Just put on delete cascade", right ? RIGHT ?

WRONG ! presence of some objects should block delete, while others can be deleted and some are "situational" depending on the first object state.

So delete operation with all the checks takes .... 1 - 2 seconds.

Seems fine ? WRONG ! When you have 40 or more objects to delete, even 1 second is too long.

Should I say "fuck it" and just write a stored proc which will crash if object cannot be deleted for any reason ? because with Entity Framework, I don't see how I can do it effitenly.

But I HATE stored proc, after couple of month/years noone remembers how they work...

RHAAAAA.

Ok I feel better.

The worst tech I've been working on is not related to a programming language, is more about the codebase itself.
One of them was in .net, the guy reinvented the wheel creating a custom mvc framework and a custom entity framework, copying from cakephp models, was disgusting and felt terribly wrong to work with.
Then I moved to an old cms written in php on top of an old version of cakephp, that was a nightmare too. Fat controllers and a disgusting db schema, no coding standards whatsoever. Everything so deeply convoluted and connected that was impossible to change something without breaking something else.
The technology itself is never the worst thing, people who thinks they are the best ninja developers, are the real problem imho, and the code they leave behind speaks for them. Yuck

Guidewire is the work of satan. It is the worst framework I have ever worked with. OOTB code is full of antipatterns, creating gui is a pain, and it has its own language that is a pure joke. Every task I had had to have some sort of workarounds. You cant junit test it. Entity builders are a mess and you cant mock gosu classes. I hate it so much.

Finishing work on a Friday when cascade delete won't cascade delete in EF and throws foreign key issues. That's my weekend doomed to be spent obsessing over why.

Piss.

What a marvellous money making combination. Entity Framework generated queries and Azure DTUs. Satyr Nadella laughing all the way to the bank

Hibernate vs Entity Framework
which one do you prefer?