@Skayo No worries - thanks very much!

@Skayo Oooh, any chance I could get an invite too? Would love to see if I can get involved with anything

While I'm not disagreeing, do take what AWS say with a pinch of salt - they're always going to push their own products and being internal for a single cloud provider, they'll be able to take advantage of some specific features.

Plus, nothing stopping you from breaking up your IaC if you're concerned with a single over-priviledged user/role.

You could also use an ALB with a fixed response, and point the DNS entry to that. But that's way more expensive than an S3 bucket.

As far as I'm aware, you can't do a redirect straight from DNS - there has to be something intelligent in there.

@SortOfTested That's a really good point. We did have a kind of linter for a while to try and solve the problem, but it wasn't very good

@SortOfTested Yeah, another guy has argued to use sonarqube for the same reason (as well as the other benefits it brings). Might be time to actually add it

@StopWastingTime Not quite - it's a singleton object (hence the additional overhead and why it's not very good IMO). You can use the JvmStatic annotation to tell the Kotlin compiler to use traditional static properties and methods if you want.

Sounds a lot like my last place. Priorities changed multiple times a day, CEO didn't understand how to organise projects and we often had like 10 going at a time, with a team of like 5 devs. As you can imagine timescales kept slipping and everyone was super stressed. Glad I got out when I did.

@endor yeah the whole needing your phone number is a bit odd, but I guess their rationale is it's an easy account identifier as you'll be installing it on your phone? Much like WhatsApp. But I would rather some other arbitrary way to ID my account.

Tbh, I've pretty much resigned myself to everyone knowing my phone number, which is why I give these my secondary, "non personal" one.

People complete their side projects? ;)

I've been using it for quite a few years now and it's a godsend. I always used to forget to get backup codes or turn off 2FA for at least one account before resetting or setting up a new phone and it was such a pain setting them all up again (I have like 20 accounts with 2FA). Authy just makes the whole process so painless. Couldn't imagine going back.

@Eliot This is something I dislike about JS as a whole - as someone who isn't a full front-end dev, it's really hard to keep up

We use react for both web and Android apps. Much prefer Vue.js. Not a fan of JSX.

@mvelebit That's insane. Who on earth thought that was acceptable?? It's not like the status code standard is new.

People who don't use HTTP status codes correctly are the worst.

I think reading depends how your team works together. I really like rebasing because it keeps your history nice and clean (not littered with loads of horrible merge commits) but the caveat is that you need to be careful if multiple people are working on it. As a general rule of thumb, I'll only rebase as the final step before merging to minimise any confusion.

I don't like squashing though - you end up losing the entire history of that feature.

As for branching, everything comes from and goes into master, and we can then control which environment that goes to. Not seen this way of doing it before, but it's actually quite nice.

Yup, Spring Boot is your way to go. Creates a self-contained jar file with an embedded servlet that can easily run in a docker container.

And I tend to find these apps are way faster than PHP. Obviously depends on your code and the size of the app ;)

@Chea Java is definitely not just client side - a fair number of APIs are Java-based

@b3b3 I disagree that comments are bad as a generality.

I wholeheartedly agree that you should not need to explain what your code is doing, as your structure and naming should do that, but instead why. It's not always necessary, but if you had to do some research and/or experimentation, putting a comment in to explain why you chose your solution will prevent anyone else coming along and either getting confused or wanting to change it to something that you've already ruled out.

Docblocks can also be really useful for people unfamiliar with a function which calls a few other functions. Yes you can figure it out by following the code, but it's usually much easier and quicker to read a summary at the top level function.

@taigrr Yeah, people should see programming as problem solving, and one key aspect of problem solving is knowing where to get answers.

A lot of the job needs to be done by yourself, but taking advantage of the wealth of resources on the Internet is nothing to be ashamed about. You just need to understand how to apply the solution you've found to your use case, rather than just copy/pasting it. That's where a lot of the prejudice comes from.

Doesn't that mean you can just take a break? ;)

That happened to me too, on my very first day. No regrets.

I used to have to do this all the time at my previous job and it drove me around the bend. Why do I have to waste time finding the link when it's you who wants it??

@Frederick The only way that could get any worse is if they decided to reopen the school just as you got home

@BashouT Good point. But the same could be true of companies and having to filter through a mass of applicants who are only in it for the money. There's nothing stopping you from asking, though.

Personally, I feel that you should be able to get a good feel of how much the company might be intended to spend by understanding the size of the company, department, projects and from the level of seniority that the job description is asking for. Although I will conceded that companies will take the mick and be very unrealistic.

I certainly don't feel that an applicant is entitled to know the salary when applying (although there should be nothing stopping you from enquiring), and I consider that to be a nice addition, rather than viewing the absence of a salary as a negative.

Some companies do list the salary, some don't. I don't think there should be a requirement for them to do so in order for people to apply for a role.

IMO, the job description and how interesting the company would be to work for are far more important than the salary. You should be able to learn more about that once you get through the first hurdles - after all, this is a good way of filtering out those who aren't genuinely interested in the job.

If they don't offer the ability to negotiate the salary later on ... now that's a completely different story.

Having used PHP for almost a decade, I can totally see where people are coming from when they say it's a badly designed language (I think this article sums it up fairly well: https://goo.gl/enAk1X). As @C0D4 said, there's a lot of inconsistency in the language implementation itself that annoys pretty much everyone - I often have to refer to my IDE to find out which order I'm supposed to pass the arguments for, which you really shouldn't need to do.

Having said that, that's kinda what frameworks have been trying to resolve. If you can find a good framework that lets you programme well, you don't notice these issues quite as much. Possibly this isn't what frameworks should be for, but meh - if you can make good apps with a good framework, at the end of the day who cares? It's still a pretty powerful and common language,.

@sydneymlambo It ended up in a reboot loop that Startup Repair couldn't fix so I had to reinstall it. So much fun.

@RiderExMachina Maybe. I've just discovered that Windows has corrupted one of my hard drives so I'm currently manically trying to recover the data in Linux.

The saga continues ...

The best bit, is that every time I boot Windows it fails to install an update, so reboots and tries to install the update ... Which fails.

Guess I'm not using Windows, then