w4tson

Also, imagine if they delivered the ship 2 years later and the client said "its all about on-land ships these days, we really need it to move on land too, oh and can we make it with sails, sails are cool. But we don't want to compromise on speed"

I dislike the way it looks like JSON but isn't.

My opinion is that QML not going to supersede web tech any time soon. As broken as CSS is, it is here to stay for the a while yet. The tooling for QML isn't great. You're heavily relying on QT Creator etc and the licensing around all that stuff. The exact opposite of FOSS that the web embraces.

Also FWIW, I know it's a holy issue but when you copy lines round in python etc you ARE having to add and remove those extra bits of syntax except they're invisible, they're spaces/tabs (don't even). Any sane person would have to have white space visibility turned on in their editor so would just be looking at cruft anyways.

I find both sluggish compared to sublime text. I flipping love that tool.

Totally unusable. Interesting topic though

294 Installed on my iPhone. Few dozen more I've uninstalled.

There is a way to do this. It took me a bit of googling but it is possible. I needed the function keys or IntelliJ would be rendered useless

Woah! That's no small side project. Impressive

Yeah but the truth isn't as exciting as thinking you can write DJango app to save the NHS. It's far more fun to think you can knock something up with your friends in a few months.

Then requirements start coming in, the stakeholders, the politics. The multi faceted organizations, the disparate teams with never ending edge cases.

3 years later when it's past phase 2 and creaking at the seams, along comes the next upstart... DJango! Which idiot picked that?!!! Me n my friends could....

+1 for the advent of code. Good for beginners and experts alike. It's well thought out, bite sized and easy to pickup and leave

:D

Done. Cheers! Took 15 mins once I'd faffed about and organised things. Plus the Alexa integration works a charm!

Try going for a run. You get some alone time, the exercise does you good and the endorphins released afterwards can ease the problem

I find myself more energized getting straight to work after a run.

Hope you work it out

But it's not a random walk. And it sure beats custom apis returning random bags of data for any given UI screen.

Sometimes you do a few more web calls than you might otherwise. If you can get away with it then great! Because the benefits are plenty

Hell! Even just having the uri of where the resource came from is useful enough. That's before you've introduced related resources.

Hey why doesn't someone just check the sourcecode? ...

I did this yesterday. However IntelliJ had my back. It's History feature has saved my bacon on more than one occasion.

One time I was able to go back weeks to fetch some code I'd long since deleted and was nowhere to be found in git.

I also have cmake installed for Mac w/Homebrew and used a binary install of qt-5.8.

After adding the clang_64/bin dir on the $PATH I too am getting 'ld: framework not found QtCore'.

Anyone able to suggest where I'm going wrong?

That's interesting. Instead of step 7. we have a separate release CI job which when is a one click, test build tag release.

This outputs artifacts to a sonatype nexus repo. From there, the binary can be promoted either automatically or manually to various environments.

It breaks Gitlabs rules of CI modifying the repo (with no explanation) but it allows any developer with any level of experience to easily release the product

Couldn't agree more with this. There's a lot of cargo culting with fit.

There isn't one size fits all, different teams develop at different rates because of ability, requirements, deadlines, culture.

Just keep it simple stupid! Why have a separate branch for tags? Or hot fixes even ?

I'm trying out some embedded rust on arm. Tried using the rump kernel but it was a non starter. Now making headway with the yocto project [0].

I'd be interested to know if you're running rust embedded and if so how easy it is to get started.

[0] https://www.yoctoproject.org/

In JVM land I look for another language on the JVM. If Scalia, groovy, kotlin haven't piqued the interest of a potential hire then it says a lot about them.

A few years ago it would have a been a nice to have. Now it's actually suspicious if they haven't dabbled!

Me too. Her writing is superb. I find her presenting a little more rambling and less informative/entertaining.

It's ballsy to write a blog asking questions about docker.

Surely if a package manger provides the ability to store in VCS then it's admitting defeat for reproducible builds. I'm thinking npm here

My kingdom for a backpack that will standupright! How many times I've cursed the backpack gods when I've placed my bag on the floor to get something out and if I'm not a ninja holding it in place with my feet it will tumble to the deck regardless of how much stuff is inside

Currently using flyway on an enterprise Java project. Brilliant library. Excellent documentation, developers sing its praises all day everyday.

Interesting, I'd not come across tabbedout.

I'm hoping a business plan will form when we follow the good peoples advice in this thread.

Doing a plan at this stage feels a bit like waterfall to me. I realise you can't get far without one but sitting down and writing one before we've established the pain points, opportunities & demands feels too early.

Maybe I'm just naive

This article has been our mantra from the beginning. Thanks for the advice. I think we knew this in our guts but when you don't have any experience it's all too easy to do the technical stuff which is more familiar.

It was actually option 6 ;-) thanks for the input. That is our hunch too however I suppose the difficulty has been knowing when to engage: too early and you're just some guys with promises and vapourware, too late and you've got a feature rich app that has missed the boat.

It is for this reason we set ourselves a mini goal of a prototype with cut down features.

Devs should never be checking in code that results in a compilation error. Regardless of whether something needs generating.

Also there’s a difference between an entire companies code in one VCS and a product with many modules.

I’ve had experience with the latter and can tell you some of the pro’s:

1. A single version for your product. This helps communications with QA, clients and managers. And communication is the game we are in whether we like it or not

2. Reduced friction in developing features that cut across modules. Lets say I need to add a column to a database and then expose in the Ui. update the sql, added the field in a webservice, make the necessary adjustments in the UI, write the tests all on the same commit.

3. Increased collaboration. Quite often invisible lines are drawn on development teams where devs are feel they are unable to modify a module because they didn’t write it, they don’t understand it or they just feel that its not a part of their job. With everything in one repo this reduces the barrier to entry

Its not a free lunch though. Like you mention build times go up For one.

I’m a jvm dev and I find gradle extremely useful in this regard. Features like Muti project builds and concurrent builds are invaluable

I thought Google was running containers in kubernetes? AFAIK you can install Kubs on VMs

Its an interesting concept however I'd like to mention that people are the real asset. Sure the code is fundamental but the reason why companies like google and Facebook make acq~hires is not get the code or even the individual. Its teams that are the real gold.