Hi, I'm a full-stack engineer with around 3 years of experience. Past projects include being a team lead for a NextJS/.NET application on Kubernetes for a leading company in the Sports industry, where I oversaw all phases of the development from planning to delivery. Currently working as a team lead for application modernization projects at Deloitte. Standard tasks include code migration from COBOL to Java, communication with the Product Team and the clients, interface implementation and delivery management for large scale projects.
Willing to learn and adapt and open to any opportunities, but would like to work on B2C products with a user-centric focus!
Hi, I'm a Software Developer with a passion for cutting-edge technology, I have experience in working with Kubernetes, NextJS, and JavaScript to build and deploy scalable and reliable applications. Currently, I am involved in the migration of legacy mainframe applications from Cobol to cloud-native Java. I'd be interested in switching to a more coding focused role. Feel free to reach out!
At the moment I'm looking for fully remote positions because of personal reason that are forcing me to relocate.
I am familiar with this situation and agree it is a problem. But this is a deterministic, well known, algorithm rather than AI, isn't it? I would also say that this falls under bias rather than misalignment. I think bias is a much, much more realistic problem area than misalignment.
This is exactly what I'm talking about in the other response to your previous comment. The joke goes "AI ceases to be AI when we start to understand how it works".
But it doesn't matter if you call the software that kills us all "conscious AI that was misaligned" or if it was "deterministic code that had a bug" - the underlying problem that we're all dead remains the same. We're just arguing about labels instead of issues.
The AI that kills us all (if this happens) will very likely be a simple, deterministic algorithm that ran on A LOT of data.
Constructive criticisms are welcome.
If someone doesn't want to login it's fine.
If someone doesn't want to login and explains the reason behind it and what could be a proper solution then that comment is helpful and worth discussing.
ChatGPT has no ads because it's a free tech demo (see GPT-3, DALLE-2). It's almost sure that as soon as it gets out of the demo there will be a pricing model.
Google is free and has to pay for its costs. The question on how to make a Google with no ads has already been answered by kagi.com
It depends on the players, but for how the game is structured you still have a good chance of "winning" (finishing alive with in a draw) even if you're way underpowered, as long as you're friendly and provide some value
It's also bad form to resign even if you have no hope and will be finished off in the next few turns, because it will inevitably favour one of your opponents not to have to worry about you at all.
Yes, and it's totally kosher to say "if you stab me on this turn I will order 'all units hold' until the end of the game" - equivalent to resigning.
But it's not OK to irrevocably commit to that decision, by, say, leaving the room and driving home.
I think this is true even in groups that take quite a liberal approach to gamesmanship and what might be cheating in other games: intentionally submitting illegal orders, peeking at other players' orders, etc. I don't know how to reconcile this logically other than by saying the game only works when all players are trying to win. Some would go further and say the game only works when most or all players are trying for a solo victory, since if you can be certain several players are happy with a 3 or 4-way draw that will always be the outcome.
The first part of my write up slightly explains it but the point is that HN is the top 1%. In my current company we have 10 developers, most of them without a technical degree. They know how to do what they've been doing for the past 10 years but (as with most small companies here in Italy) people don't know what best practices are used in the industry, what a pipeline is or what a dry-run is (I learned about it today myself!).
What happened is that no one knew how to react and I was probably the best suited for it, we don't really have seniority in office.
That said when I deleted the videos I immediately told my boss. He was kind of scared but his reaction was mostly "Well, now we have to re-upload them immediately, find a way. The people that uploaded them once won't be doing it twice". I was basically left on my own to find a solution (which I luckily did).
Please note that I'm in no way blaming my company or accusing it of something, this is the standard knowledge base and way of dealing with things in many places, contrary to what working in big tech or reading HN might make you believe!
Thanks for the explanation, that makes a lot of sense!
> "HN is the top 1%" + "this is the standard knowledge base and way of dealing with things in many places, contrary to what working in big tech or reading HN might make you believe!"
I'm in fact from Spain and now live in Japan, and I believe the practices in Spain would be as bad as Italy, and in Japan they are def worse (great at hardware, horrible at software), so I do understand a lot of what you are saying. FWIW, in Spain I've seen whole dev teams composed only of interns!
> "we landed a big contract for one of the biggest gym companies in Italy, the UK and South Africa" + "we don't really have seniority in office"
Maybe now that seems like you have the budget it's a good time to go to management and suggest to hire some senior devs who can mentor the rest into learning best practices? You can sell it like a reinvestment in the company to management if they want to take it as pure profit. If Italy is like Spain, many devs won't really even want to learn these things, but some will and then those will become seniors at some point.
I'm sorry if it came off like that. The mistake in this case was completely mine (bad code and bad testing). The detour on the other two companies was mostly because this way of deleting/recovering stuff should've probably been avoided in the first place, other than that I'm absolutely not blaming anyone else!
Don't worry about all that - there isn't a developer worth their salt that hasn't made a mistake.
But I'd consider having this blog post and HN post retracted purely for future internet checks. It isn't a reflection on you, and your honesty is fantastic. But there is a lot to be said about using a pseudonym when it comes this close to your employers
Remote: Yes
Willing to relocate: No
Technologies: Typescript, Javascript, Node.js, HTML, CSS, React, NextJS, RESTful APIs, Java, .NET, SASS, Kubernetes, Python, Docker, Git
Résumé/CV: blog.thevinter.com/cv
Email: nikita.brancatisano@gmail.com
LinkedIn: www.linkedin.com/in/nikita-brancatisano
Website: blog.thevinter.com
Hi, I'm a full-stack engineer with around 3 years of experience. Past projects include being a team lead for a NextJS/.NET application on Kubernetes for a leading company in the Sports industry, where I oversaw all phases of the development from planning to delivery. Currently working as a team lead for application modernization projects at Deloitte. Standard tasks include code migration from COBOL to Java, communication with the Product Team and the clients, interface implementation and delivery management for large scale projects.
Willing to learn and adapt and open to any opportunities, but would like to work on B2C products with a user-centric focus!