w4tson

It sounds like you’re frustrated with some complexity surrounding package managers.

They can be complicated but they’re not invented to torture people. They solve real world problems.

Some are better than others. The best thing I can say about Rust’s Cargo is I have no clue how it works because Its never given me cause to find out (ok I roughly know).

Maybe. But that’s also a race to the bottom. And it’s not like you need many developers to get stuff done. The right team and autonomy to choose their tools can be way more productive that a big team

I live in London, UK. I can’t drive. Last time I was behind a wheel it was 1999 and I failed my driving test.

I get the train places and taxis the other end (Uber if the city allows).

I’ll admit a few times a year I think it would be nice to drive and I intend to take my test again one day but It’s down list of stuff do with learn the banjo and work on my Haskell

I’ve wasted enough time tinkering with gulp, grunt and webpack to sympathize

If the previous commenter was familiar was familiar with 47 build tools and has discounted a lot of them as extraneous. Is he advocating building an npm module with make? What about a jar? Nuget package? Cargo module?

Its seems more likely that they’re frustrated about the sheer amount to learn and they probably know make quite well.

But there are real advantages to these tools. There’s a lot of vanity libraries out there but not many vanity build tools.

And while you’re at it can you make it idempotent when building sub artifacts which inputs haven’t changed.

And can it do it all incrementally in parallel too please because enterprise shops tend to have a ton of code

Oh and it would be really nice if you could make it so if someone else somewhere in the org has compiled that thing then could we just use their computed binary to save the time compiling locally.

THANKS!

;)

EXACTLY. It’s just software. There’s no easy answers here. There’s vulns in everything from hypervisors to node modules. Building from scratch isn’t going help.

Pragmatic solutions where possible. Like scanning containers, using OWASP tools on your repos etc

How many IDEs have you used? Off the top of my head I’ve been a Borland, Jdeveloper, netbeans, eclipse, Xcode, Visual Studio.

None of these comes close JetBrains current offerings. They’re totally killing it at the moment. Certainly for typed languages at any rate.

A lot of C# devs I know prefer Rider to VS which tells a story I think.

Great explanation: AOP at a macro level. You made an interesting point about a homogenous language across services. It’s prescient problem in my team. I’m not alone in thinking that shared binary code for the “ilities” produces more problems in the long term than it solves.

At this point the solutions seem to be intro a service mesh or copy pasta.

Don’t forget those rust vs go threads. 300 comments of people talking past each other ;-)

The “,0,0” makes me think the person had inside knowledge

Interesting, I got the impression that the problem was being restricted to a single thread. “being single-threaded, couldn’t process operations in parallel”.

Wonder what the article would have said in a parallel universe where the problem was migrated to something like the Akka framework on the JVM?

My “3” key quite often repeats on mine. I really dislike the keyboard.

The up and down arrow keys are so small it makes it really difficult to touch type. Especially when coding and you’re navigating about using the keyboard.

It’s the stupid race to the bottom to get the worlds thinnest laptop at the expense of functionality.

How about Kotlin? First class support on Android. Great tooling and compiles to JS

It’s more than this. The difference is important. Employed in the right areas like the article suggests they can be an effective weapon against bugs creeping into data access, messaging or web client components.

The speed at which they run is their side effect. It’s possible to write slow running unit tests

While it may be a hallmark of DI it’s not necessary. Spring is perhaps the most famous DI framework of them all and is frequently used by “classpath scanning” relevant components to wire in

This is cool. Where did you learn this?

The contract of a Java servlet filter is

  doFilter(req, resp, chain)

You could use that if it Is more suited to your style?

I have no experience at being either but I have seen many a few dozen each over the years.

From a developer perspective the two roles seem alien to each other. While it is a natural career progression, the skills aren’t necessarily the same.

Project managers tend to manage the expectation of seniors while trying to keep devs on track, QA doing their thing all the while reporting that some critical feature will certainly done by a date X.

Programme Managers tend to need way more political skills in large organizations. They are often fending the for the very existence of a project. They may be concerned with power grabs by rival teams/programme managers or trying to satisfy people who hold the purse strings which is often at odds with what customers or projects deem a priority.

In my opinion the higher up you go the more sociopathic they get so everyone is playing a large game of chess, forging relationships, writing memos, holding secret talks etc

These are entirely opinions based on little evidence other than amusing observations.

One last thought. Those write the code hold the most power, but seem not to realize this or wield it far less.

That’s not the advice Mark Reinhold gives. From the talk I saw some give last year he advises moving with the versions.

If it’s one thing we’ve learned in software it’s embrace the change. Little and often is the way to stop technical debt accruing

Also interesting he was not keen on “I am the Walrus”.

He didn’t seem to mention production either. Sgt Peppers was the birth of concept album recorded in stereo!

Probably saying something like

  public String getDescription() {
    return “some constant”;
  }

Versus

  public String getDescription() {
    return FOO_DESCRIPTION;
  }

it’s a fairly weak example but you get the idea.

I really like flyway. It’s lightweight and the best thing I can say about it is that I rarely have to bother with it. It just works.

I too find it useful to keep the migrations small and succinct. For Oracle do migrations where the DDL cannot be rolledback I choose to separate these from straight data manipulation.

A downside to the project that I see is that although it’s quite mature the author is very very slow to engage with open source modifications.

I’d still make it my first choice because of its simplicity.

You can get feedback before the compiler kicks in by asking IntelliJ to explicitly define the type.

It’s a trick I used quite a bit when playing about with rust, and Kotlin actually.

Alt + Enter should invoke intentions pop up, you can do it from there. (I think)

Totally agree with all these points. This is my favorite answer so far.

I’d like to emphasize the people aspect point.

It seems like the more experience you gain, the more you realize you’re not in the business of 1s and 0s, you’re actually in the business of people

Want to ditch that oracle DB? You can’t do it with code, you need to influence someone.

Want a requirement to disappear, you need to explain why it can be solved another way.

Want to get better at what you do? Work WITH someone and learn their keyboard shortcuts, design patterns, ways of thinking & command line fu

I own 7 shares and I’m irate ;)

JetBrains IntelliJ.

Over the years I’ve used Xcode, VisualStudio, Borland, Eclipse, JDeveloper, Netbeans, Notepad, Atom, Sublime etc to write code

I use IntelliJ/IDEA because it’s a tool that delights. Not many bits of software are such that I interrupt other colleagues to show them some neat feature or shortcut.

That might be a start. But there’s even more subtle things going on.

What about the person who can resolve conflict. The person who always takes on a task to the bitter end regardless how bad it smells. The person who thinks ahead. The developer who loves process and documentation. The developer who can code you out of a tricky situation. The person who’s always trying new things.

Personally I think it’s a lottery. Like putting together a football team but we don’t even know the positions yet. We just know they can play football

I spoke to guy once who was researching what makes a high functioning team for some large (unarmed) company. His insight over the various studies he’d looked at was as follows.

1. High functioning teams are in the order of 5–10 people 2. Everyone in the team is respected for what they bring to the group regardless of experience.

If you’ve 20 years experience you’re valued for your knowledge of pitfalls etc. If you’ve 2 years you might be valued for your enthusiasm. Or if your a fresh graduate you could be valued on your ability to question conventions that others do not.

My question is: given this, how would an interview ever hope to sift out a potential candidate. Especially when the qualities of the final aren’t (could never?) be properly specified relative to the team they were due to go into.

That’s just general search. When looking for code issues and snippets it’s worse

Don’t even get me started with github. Half of humanity’s code seems to be in some bucket that doesn’t understand punctuation when you search