It's all just noise. There's no substance to any of it - just vague circumstantial nonsense and wild, unsupported allegations.
180 karma · joined May 10, 2018
It's all just noise. There's no substance to any of it - just vague circumstantial nonsense and wild, unsupported allegations.
This whole debate is one big straw-man. I'm a vegan. I don't need burgers. I might want burgers, but they don't form a part of a standard diet just in the same way any kind of burger probably shouldn't form part of anybody's regular diet.
If you're eating processed food - there's a considerable chance that whatever it is you're eating - vegan or otherwise - is neither nutritious nor healthy. It probably tastes good though, which is why you want it in the first place.
Ultimately it boils down to this: if I'm eating a burger, then nutrition and health are more or less irrelevant - I'm after taste. I think the lives of animals are more important than my taste-buds, so I eat plant-based burgers. It's not really any more complicated than that.
Google became 'evil' as soon as it realised that exploiting user data was the route to profit. We live in the information age - any for-profit business is going to pursue that which makes it the most profit.
Since most people are used to the idea of online services being 'free' - they got used to the relationship imbalance, and few companies ever really inform their users about exactly how much value their usage produces.
The surveillance aspect is definitely real - but I suspect it emerged over time as Google was forced to work with law enforcement, security services etc as its reach and power grew.
The best way to improve this is just practice, plain and simple. Check out an open source project you like, and add a feature. You don't even need to create a PR for it - just do things you think might be good / useful - but add them to existing projects. It takes time to figure out how to separate signal from noise with other people's code - you just have to put the hours in.
> I have problems at paying attention in meetings. I struggled through the whole university too. I understood and learned almost everything at home for 5 years. Sometimes I even got asleep during important classes. I'm not talking about 1.5 hour long scrum groomings or reviews, sometimes I can't even pay attention during a 15 minute long standup in the morning. At my lost job they found it as a serious problem. Where to start?
If you can rule out a disorder like ADHD, then some of the best things you can do to improve concentration and attention span:
1) Get enough sleep (you mentioned falling asleep sometimes - a good sign that you're not getting enough generally)
2) Eat well, and regularly.
3) Stay hydrated
4) Take regular breaks (go for a walk, get some fresh air)
No solution is 100% effective - but they're things that have helped me.
I say all this as a non-US observer. The US' media and political figures are completely unfit for purpose.
There's no reason whatsoever to assume WL has any information about anything at any given time, unless they've publicly suggested that they have.
Many sectors & industries will undergo some degree of automation, either total or partial. Included in that is the work done by software developers.
Your initial suggestion was that you couldn't automate software engineering jobs (a straw-man). Now you're arguing that the US tech industry is better because it makes more and pays more than its EU counterpart. This is irrelevant to the discussion about whether software developers should unionise. Joining a union is about more than securing good pay.
But again, this is only true because of the delusional rock-star fantasy which grips the tech industry. The vast, vast majority of software developers are not rock-stars. They are seen as disposable - precisely because they are - which is why mass layoffs can continue to happen as a predictable part of a development lifecycle.
You are approaching this discussion as though the key factor is the pay of a company's top employees - but those people are a tiny, tiny fraction of the people employed in the software development industry.
> There is no argument whether American software/hardware industry is doing better than EU software/hardware industry
Yes, but what people are (rightly, and increasingly) concerned about is how well the employees of those industries are doing. The fact that US tech makes more money than EU tech is largely irrelevant to the discussion of whether and how those employees should unionise (they should).
> My point is none of these will ever solve the problems American SWEs are trying to solve. You cannot build an Uber this way. You cannot make rockets go to sky this way. You cannot write Airbus's OS this way. You cannot do these and retain the same, competitive quality required in this industry. You cannot do that unless you spend a lot of resources for R&D how to automate programming.
Yes, but again - most developers do not work on these problems. Most developers aren't building an Uber. They're not building rockets. They're not writing Airbus OS'. And in each of those areas - what can be automated will be.
> No C programmer ever got fired because GCC suddenly became too good at optimizing C and "their job was automated".
Plenty of developers have been fired because management decided that throwing faster hardware at slow software was more cost effective than paying slow humans to make slow software work on slow hardware. Optimisation of code wasn't really what I was thinking of in terms of 'automation'. Rather, what I was arguing is that machines, given a (relatively) well defined problem, will be able to implement a solution that is cost effective enough to be cheaper than hiring developers.
Everybody says that about highly skilled work. Humans excel at making skilled jobs obsolete. You don't need a perfect replacement for human skill / creativity. You just need an acceptable basic replacement to which you can attach bells, whistles, and marketing. Nobody is going to hire a rock-star when a session musician will still fill your bar - and you don't hire a session musician if a jukebox satisfies your customers enough to keep buying pints.
> What easily definable parts are there in SWE?
Most software developers are not software engineers. Most software is not a feat of engineering.
> From my point of view, the only reason USA tech industry is so much better than EU tech industry is because US companies realized the success of a company is strongly linked to its product's quality which can only be made by hiring better, more educated and more experienced engineers.
If your argument is that EU developers are dumber and less experienced than their US counterparts, then it's not much of an argument.
> Going back and trying to reduce engineering cost is backwards and no one will be able to survive like that in this competitive industry.
The problem is you're viewing 'software development' as the industry. But that's not how the rest of the world sees or interacts with it. Developers are not interchangeable. Software products are not interchangeable. Within each industry, jobs and processes which can be automated, will be. Most software developers do not work in the games industry. They are not creating new products. They aren't being creative (or at least, not particularly creative). The skills required to implement most software are generally already a few years behind where the technology actually is.
I really don't think this is nearly as true today as it was say, 20 years ago. Anecdotal evidence, sure - but my experience is that developers are crying out for unionisation, but have a bunch of rock-star crap in their heads which tells them that they're somehow going to release a groundbreaking new game or app that changes their lives completely, rather than acknowledging the more likely reality that they'll be constantly getting screwed by an industry that will automate their job away as soon as it becomes even vaguely possible.
I agree that tests can be bad, frustrating, badly designed or just plain incompetent - but ultimately I'd rather hire someone who knows what they don't know than someone who thinks they can wing it. When I've been tested like this in the past, I just explain which questions I can't answer and why. If they want to talk it through, then great. If not, then do I want to work for them anyway if the attitude seems negative?
The real issue you need to overcome is fear of failure. Aside from some specific cases, nobody in the hiring process really cares whether or not you 'pass' the test - it is (or should be) more important to assess how you approach the problem and whether you are capable of acknowledging what you don't know and talking through your thinking.
I agree that it's difficult to measure productivity / output - but it's by no means impossible - and sharp discrepancies in productivity between employees are often highly noticeable anyway.
I don't see why such a situation should need to affect salary transparency. It's also useful for employees to know the standards required to earn more.
There's no wider benefit to the public from this unless the chain is publicly verifiable, imo.
Generally speaking:
1) Stick to bug-fixing for a good few weeks / months. This is invaluable for figuring out the mess and understanding why it is the way it is.
2) Ask questions - don't be afraid of asking basic questions if you think something looks silly. More often than not there's a reason.
3) Improve the code in small chunks, but be mindful that what you consider an improvement may not be.
4) Understand that working as a team means you will need to accommodate varying levels of skill.
5) Don't blame individuals for bad code. Leave that to your superiors.