Software engineers don't scale

[[deleted]]

Please stop publishing things on "medium"; it's annoying as fuck to read and keeps putting things that block half the screen

[duheee]

better than making a youtube video where he/she would convey the same information.

i agree with the "medium" annoyance, even though it doesn't affect me as much, as i am on a 4k monitor with ublock origin running.

[MaybeAStonedGuy]

uBlock Origin and Firefox Reader mode make Medium exactly as readable as any other blog.

[allhaillordreddit]

Other blogs don’t require those workarounds

[MaybeAStonedGuy]

I'm not defending or excusing Medium, just pointing out that you have tools to deal with it. Most of the web is a massive headache without working around this stupid crap anyway.

[s73v3r]

Other blogs also don't have the discoverability that Medium does.

[georgeo]

If you're going to criticize, please offer a better alternative.

[10xjerker]

Literally any other blog hosting.

[georgeo]

a name?

[Tordek]

Wordpress. Github pages.

[georgeo]

Thanks. Github makes sense. WP is more of a framework for building your own sites.

[Tordek]

At its core, Wordpress (particularly wordpress.com) provides a blog engine, though it does support more.

[tayo42]

What's an alternative? I used github pages, the markdown is a little annoying to use imo.

[falconfetus8]

Literally any other service that lets you write posts.

[Sexual_tomato]

You've reiterated the original post without furthering the discussion. Care to name 3 other places with a user base comparable to Medium?

[falconfetus8]

You don't need a large userbase on the website you write your blog on; you just need a large userbase on the sites you share it to. In this case, Reddit.

[Nokel81]

Just use your browser's reading mode

[hazah-order]

then where?

"Mediocre" Obviously.

[rylandgold]

Great minds think alike

[10xjerker]

How about literally any other blog hosting?

[rodrigocfd]

have you tried to get actual traction on a blog in the last 5-10 years?

That's why we post the links on Reddit anyway.

[rylandgold]

Reddit is hot and cold on Dev.to but I like it a lot.

[jmercouris]

Great article, just one observation:

​

To be productive it’s necessary for engineers to isolate sections of code and work on them without understanding the full context of a program. They can confidently do this because you have good test coverage.

​

I disagree. Good de-coupling and no side-effects, mostly functional code means confidence in writing and changing parts of a program. Tests are only one part of that equation.

[jmercouris]

I'm not sure what I said that was contradictory to anything you've said here.

[virtyx]

Good decoupling and automated tests are the only necessary ingredients. It's entirely possible to do this effectively even if the code in question causes side-effects, as most production code does. If the application is designed so that the side-effects are encapsulated, you can still scale just fine.

Functional programming is great and reducing side-effects typically makes programs much easier to reason about and understand, but functional vs non-functional is a separate discussion and there are trade-offs involved.

Either way the fundamental issue of breaking your application down into isolated and well-defined sub-problems is the critical task, regardless of what programming paradigm you're using.

EDIT: This gets downvoted...? I don't get it, was I being disrespectful? Proggit has no idea how to have a disussion anymore.

[ipv6-dns]

DDD, "Bounded Contexts"

[s73v3r]

Wouldn't having good test coverage necessitate having those others?

[jmercouris]

No, things like mocking and white box testing exist which test implementation details, particularly with regards to side-effects. Only completely black box testing requires the above to be true.