What to do when you think a junior is working hard, you're generally happy with quality, but speed is way below where it needs to be?

I wouldn't say it's upsetting but confusing.

I had an interview at a household name where I asked for feedback. They only told me I did well in the technical and every other area, and that I was the first person they interviewed in the last 2 months to make it passed the technical part.

Less than half a day later I got a rejection email.

Working as a Dev for a while now, I tell new people not to bother with it. There is never any job satisfaction as people in charge never understand the basics.

Instead of learning to write efficient code, figure out how to solve real business problems, work towards a maintainable flexible product to quickly deliver value on changing requirements, write automated tests to improve quality, maintainability and prevent live issues - basically do anything a good Dev strives for - you will just constantly end up working for people with no interest beyond the next couple days, on a shit code base that no one can understand, with people that don't want to learn anything about software design and just check boxes off.

Apart from pay this must be the worst career possible in a technical field.

My company got bought out. Supposedly a good thing... Anyone got stories?

For a .net developer is it normal not to know what an abstract class is? I interviewed someone today that didn't know, and a colleague told me it wasn't that unusual.

To me this is the same level as knowing what an interface is

Are PRs only to help juniors? I don't think so but someone I know does.

What gets me is that still, even now, most bosses do not seem to understand that quality will give you speed.

Why is this even still a fucking debate..

Is it possible to really learn azure or aws on your own without spending much money?

My company doesn't intend to go for cloud solutions but I feel that's what I want to work on. I'm nervous about accidentally creating a huge bill.

had to reject a junior candidate today. Couldn't really write an if else statement.

Always feels bad, I remember being mortified when I was at that level.

I'm trying out some stuff I read. I have rich domain models with private fields. In order to create EF core entities my domain models create snapshots with public properties.

So 3 models - domain, snapshot, entity.

Now I am thinking about introducing a fourth for the API.

This seems mental and that I have misunderstood something. Automapper might help clean this up.

I despair at how most devs don't want to learn or self reflect if their code is clean.

It makes me hate this job some days.

I had a conversation that almost became an argument with a someone I manage the other day. It revolved around how we should do just the basic parts first as that's what the business needs quickly and the code base is in a bad state right now so I didn't want to build new features on a poor foundation, particularly as those new features might not be forwards compatible and might have no way of fixing.

Once basic is in, refactor and cleanup, add secondary features. Their point was to just do it all at once in a big bang. It devolved into them getting angry and telling me to leave them out of all future discussions because now we "aren't ever doing the secondary features", just give them the task and leave them alone.

I let this go, but now I've found out they went to another high up person on the team and presumably lied to them about what was said.

What to do?

Just casually learning if I don't fix a bunch of stuff I know nothing about in a technology I have never touched within 2 weeks the company loses a 100k contract.

Should book holiday.

Today I was told that full stack is another name for a shit developer who wont be able to develop anything good because they aren't focused on one skill.

But it was by a person who claims to like OOP but doesn't know the 4 principles, SOLID, GoF, or DDD. So I take it with salt. But he claims his entire company follows this philosophy.

I think that some developers just decide that they're hot shit and refuse to talk about any other skills they don't know about since they must not be needed if they don't know them. Code is code.

Dear .Net developers.

I wrote this tonight:
https://github.com/Future-Forward-S...

Please let me know if I am extremely clever, or extremely stupid.

P.s. I know it's not exactly ports and adapters. Rename needed maybe.

That you can't get by on intelligence. School had not prepared me for actually learning.

"Where's the database server gone?"

How do you move clients from an old and insecure integration API, to a new implementation?

I'd live in a ditch

What's a good way to guage someone's domain modelling expertise in an interview? I don't want to make people go do an at-home project because we aren't big enough to be filtering candidates who won't do it, simply because they can't be doing that for every application.

Technology I can ask questions about, but stuff like DDD I think it's hard to know without seeing them work.

By any chance can someone explain logarithms to me and how they relate to complexity growth? I can do the calculation but it's only from memorisation. I just don't understand how it relates to a graph.

I am working on an event driven system that uses a message bus and has a few services that talk to each other asynchronously via the bus.

I'm writing in memory integration tests for one of those services, but I just realised the fundamental flaw here with such tests. I only have 1 application running, but I need several. This is quite a serious flaw I should have seen before.

Anyone else tried integration testing event driven distributed services? I imagine all I can do is stub the message broker...

Today I spent 9 hours trying to resolve an issue with .net core integration testing a project with soap services created using a third party soap library since .net core doesn't support soap anymore. And WCF is before my time.

The tests run in-process so that we can override services like the database, file storage, basically io settings but not code.

This morning I write the first test by creating a connected service reference to generate a service client. That way I don't need to worry about generating soap messages and keeping them in sync with the code.

I sent my first request and... Can't find endpoint.

3 hours later I learn via fiddler that a real request is being made. It's not using the virtual in-process server and http client, it's sending an actual network request that fiddler picks up, and of course that needs a real server accepting requests... Which I don't have.

So I start on MSDN. Please God help me. Nope. Nothing. Makes sense since soap is dead on .net core.

Now what? Nothing on the internet because above. Nothing in the third party soap library. Nothing. At this point I question of I have hit my wall as a developer.

Another 4 hours later I have reverse engineered the Microsoft code on GitHub and figured out that I am fucked. It's so hard to understand.

2 more hours later I have figured out a solution. It's pure filth..I hide it away in another tooling project and move all the filth to internal classes :D the equivalent of tidying your room as a kid by shoving it all under the bed. But fuck it.

My soap tests now use the correct http client with the virtual server. I am a magician.

Today I used NDepend to analyse my new jobs code base. It looks like the classic big ball of mud :(

Can anyone point me to some example of a .net project that doesn't scale because not using async await for IO?

I'm not sure how to measure impact of not doing this...

I tried SOAP for the first time today. It wasn't bad. I had a client for the service built automatically instead of writing my own.

Why is SOAP dead?

!Dev

Bought my first house :) 3 bedroom house to myself. It's insane to me.

Logarithms give me a headache

Learn more about networking, revisit computer science fundamentals, memorise agile frameworks, practice DDD properly, learn about basic property and conveyancing law for my new job, get through 1 tech book every 2 weeks, revisit Linux as it's been a long time, learn the basics of developing and deploying with azure, learn terraform and docker, finally finish building my own product that has been going for 3 years now, continue learning about mobile development and build a mobile app for my new product.

Should be fine xD

Are there any class based JavaScript test frameworks? I dislike the whole describe/it setup. I know it's basically the same thing, but I prefer the class setup in .net with xunit. I like being able to write abstract classes for tests..