I've noticed a similar trend on YouTube and Bandcamp too. Sadly, I personally know a few people who are engaged in those activities in my business school class.
The usage of generative AI has significantly lowered the barrier to entry for the creative industry, leading to an influx of AI generated products that are easily consumable and can be used to generate revenue.
Until the platforms begin to regulate AI art, which I don't see why they would, we can expect to see more of them in the near future.
With sufficient education, awareness, and incentives. I don't see why not.
There's already a massive shift in the hospitality industry with paper straws and bio-decompositable cutlery, saving the world from a tremendous amount of plastic.
I would think that education and awareness could work for another generation, though them being bombarded with a popular social media image of life it may be hard. Incentives work to some extent (the biggest being a cost of doing the good thing being lower enough than doing the bad thing), but if you will make costs of doing bad things artificially bigger (I know, it is about things the society currently thinks as free) you risk populists getting to power.
If you are applying for a junior role, I don't know much about Europe, but in India the defence and security sector often have internship programmes for university students.
Alternatively, same as all other jobs, keep your eye open and make sure your CV and cover letter is catered towards the job.
You don't need to be a misanthrope to work in defence and security. Despite the bad PR, it's comforting knowing that your work is making the world a safer place.
That 'making safer place' is 50:50 at best, every single arms/bombs/rocket/ammunition manufacturer has seen its products used for smaller or bigger genocides of civilian population across whole age spectrum, with obviously the biggest being US and Russia/CCCP.
Its supremely dumb to blame manufacturers in any way of course, they are just (pretty efficient) tools.
Seconded, there's no tangible nor financial benefit to him for releasing the information to the world. Also: how would publishing the data "make the world a better place"?
At the same time it'll incur a non trivial amount of reputational and professional risk.
> Also: how would publishing the data "make the world a better place"?
For example, schematics of Apple devices would help people fix them on a deeper level than Apple wants (Apple doesn't do board-level repair, one 3-cent component fails and you're getting your entire motherboard replaced). Diagnostic software would help with that too. Documentation about any artificial limitations Apple imposes on these devices for its own profit, like part pairing, would make these limitations easier to bypass. Documentation about software or proprietary network protocols would help with adversarial interoperability. Even documentation on manufacturing techniques might be useful for someone building hardware — if not to copy, then to learn from it.
I often draw the line between adventure/action-rpg (Zelda, Diablo, etc.) with traditional RPG based on the reliance of in-game character skills vs player skills.
In a traditional RPG, a character with sufficient stats are bound to succeed more often, whereas in an action game it really depends on the skill of the player.
It has been established that this is a standard pattern for most image processing services to prevent abuse though...
I completely understand that it might not be for you, but in business school we were taught that engagement metrics is key to growth, and account creation is a good indicator of engagement.
Te Reo is often considered a taonga due to its value in the heritage and identity of the Māori people of New Zealand.
Te Reo names are often gifted by Iwis or individuals with sufficient Mana. As a Tangata Whenua Inia, I was strongly recommended to avoid using Te Reo names in business due to cultural reasons.
I'm from New Zealand myself, I understand the cultural context here. I grew up using the word Kākāpō as the common word for referring to the actual bird. If I was the author, and somebody takes offense from my usage of the word Kākāpō (the word used in English as well as Māori), I would politely ignore their concern. Mana, just as in World of Warcraft as in real life, is of little concern to me.
And getting precious over a word is ridiculous, it seemed to be a common theme growing up in NZ, there's a general apathy until there's some perceived benefit and then suddenly it's about race and culture.
Even if they copied OP's code, depending on the FOSS license it might not be illegal.
As someone who grew up in India, this practice is actually quite common and not exactly frowned up. When you have multiple products that perform similar functions, whoever can sell them the best will gain market dominance.
OP did not pursue the monetization path chosen by his competitor and lost out only on potential income, this might be a good lesson in entrepreneurship and IP management.
Agile does not really works. It sometimes works, exceptionally, usually the more you try to do the by the book agile the worst it gets. Every single time they make agile reform, everything stats to suck and everything turns into ritualized micro management.
I'm all for criticizing agile etc if it doesn't work, but this is such a generic complaint.
What's "by the book" agile? Scrum? The things in the manifesto? Something that some rando Scrummaster said?
And who is micromanaging? Both the Agile Manifesto and Scrum are about "self-organizing" teams. If someone is micromanaging, how is that self-organizing?
It is generic, because it is the most common result of agile.
> What's "by the book" agile? Scrum? The things in the manifesto?
Definitely scrum.
> And who is micromanaging? Both the Agile Manifesto and Scrum are about "self-organizing" teams. If someone is micromanaging, how is that self-organizing?
Every single detail and aspect of your work is determined by someone or something else. You have zero individual autonomy, zero individual responsibility. And zero option to do something good or bad. "Self-organizing" just means that scrum master or coach or whoever is creating set of rules that dictate pretty much every aspect of work.
Yeah, it is not one person telling you how to do things. It is that every aspect of work is decided by someone else or some committee. When you have one person telling you how to do things you at least can adjust to them and negotiate some space with them.
> "Self-organizing" just means that scrum master or coach or whoever is creating set of rules that dictate pretty much every aspect of work.
See, this is already not "by the book" Scrum.
The team decides those things in a retrospective, and as long as they are releasing in a reasonable timely manner, it's alright.
If someone is being unreasonable and putting their foot down too much, then it's a management issue that doesn't have anything to do with Scrum. Either the person is a dictator, or they don't have authority and there's no management to put an end to it.
Scrum also doesn't work when the team is burning in a building on fire, but we don't blame Scrum for that.
I'm all for shitting on it, but those problems have been happening in companies for millenia. Scrum won't fix them, you gotta fix each separate problem by itself.
Three of the original signers of the Agile Manifesto are also the main people involved with creating XP[1][2][3].
The Agile Manifesto was just a bunch of people who were already doing XP, Scrum or some other lightweight process getting together and writing down the similarities between what they were doing. It's a blanket term invented to describe a variety of different processes, not an actual process.
What if the requirements are super clear but they change? When do you find out and what happens then? I've personally never had a project where the requirements were 100% clear and stayed exactly the same. Even when writing a v2 of an existing project from the ground up things tended to be unclear and subject to change.
The point is to use what ever works best for your team, not blindly follow some process that may or may not necessarily work for you.
Just as product requirements can change, so can the way we work. Just like there is not one singular product that solves everybody’s needs, there isn’t necessarily one process that does that either.
Sounds like you need a process that can be flexible, able to respond to change, some might say… agile ;-)
I kid, but I think the early proponents of Scrum and similar were trying to achieve a loose framework to do exactly what you’re talking about. The modern incarnations of these can be horrific, but the original intent was always to empower teams to make their own process. Ahh well.
Like so many good ideas (democracy, constitutions), you only really know how well they function once people are actively trying to subvert them. Scrum et.al. have failed in the face of corporatocracy. I honestly don’t know if decentralised structures (i.e. teams empowered to run themselves), can ever survive in large corporates. Which is a pity. Cities grow, but companies die. You have to jump off the dying colossus to find the new company that hasn’t yet succumbed.
> What if the requirements are super clear but they change?
You need to communicate with stakeholders then, to change requirements, explain mistakes, set new goals, and reprioritize tasks. Agile (SCRUM/Kanban/etc.) are designed with frequently changing requirements in mind. In SCRUM, this is done at sprint review/sprint planning stage. In Kanban, it's continuous process.
Well then requirements were not 'super clear', they were simply incorrect and it doesn't matter in which way. A very bad start of any project, since beginning you are already putting out flames left and right
The usage of generative AI has significantly lowered the barrier to entry for the creative industry, leading to an influx of AI generated products that are easily consumable and can be used to generate revenue.
Until the platforms begin to regulate AI art, which I don't see why they would, we can expect to see more of them in the near future.