828 karma · joined May 8, 2008
Website: http://codedemigod.com Email: alaa@codedemigod.com
Side projects:
- https://moneytracker.codedemigod.com/ - https://aussieshopper.codedemigod.com/
At one business I was a part of where that experiment was tried, it failed badly. In reality, people were being switched around on projects and the "owner" was changing every few months. The end result was quite messy, both in terms of technical debt and politics(about who's the final decision maker).
Remote: Yes(open to hybrid)
Willing to relocate: For the right role
Technologies: Python/Django, Javascript/React, Javascript/Vue, PostgreSQL, AWS
Résumé/CV: https://codedemigod.com/about/
Email: alaa@codedemigod.com
I am an experienced full stack software developer with 15+ years of experience across the board dealing with dozens of languages and frameworks. Most of my recent work involves working within the Python ecosystem with Django as the framework of choice for web development. My experience includes working directly with customers and managing small teams to launch products and services. I also enjoy working with Linux servers and production infrastructure.
edit: I should probably add more context as some commenters didn't understand. The DDOS attack is likely coming from compromised IoT devices. Most, if not all, of the big ones in the last few years(decades?) were that. Unless all the devices are located within a specific country and non are within the US then I think it is silly to use that term to imply that this is some sort of war from across the border. The reporting is fine for what they know so far, the submitted title is not.
But, having been in a somewhat similar situation, I can tell you that some companies and teams are just dysfunctional and "cliquey". It has nothing to do with anything rational or logical or something you did or didn't do, it's just broken beyond repair. My guess would also be that they have had a number of people come and go probably due to the same reasons.
That manager also sounds like they shouldn't be managing at all. Besides that silly metric(did they also specify how many lines of code they want per day? ridiculous), it would've been more useful if they explain why your changes were turned down at least. There might be a good reason that you're not aware of. A sane manager would choose to guide you to make sure your valuable contributions benefit the business and align with any strategy as opposed to talking to you like a child and going "do it because I said so". Your teammates may have been having a bad week or feel threatened but I blame your manager. They should know better.
I recommend you plan your exit as nothing good will come out of you staying.
I've seen this a few times and I find it distasteful.
On the other hand, I've had some interactions with customer service reps that made me wish a chatbot was available. Like asking for a medical appointment.
In a small market with a handful of competitors or non at all in some cases, what are you going to do exactly? It will be the same elsewhere. The large corporations know this and will obviously take advantage of the situation unless forced via regulation(in AU).
I do notice a small movement where people had to stop paying for a service and after a while realized that their life didn't change for the worse and so started re-prioritizing their needs and wants and thinking before spending. Like the typical daily $8 cup of coffee. That doesn't work for essential services like healthcare of course.
Whether that cost cutting is beneficial for the business in the long term is another question. Context is Australia.
The problem is getting the decision makers to care. And/or changing the process to at least consider quality as an important factor even if velocity is preferred(and featuritis has taken over).
Story time. In one gig I had, a couple of weeks into it I discovered that AWS keys to the production data in the S3 buckets were being exposed on the client side(an SPA). Those keys would give you access to the data for all the clients on that platform. So I figured I'd do "the right thing" and told my manager(the CTO) who said something along the lines of "yeah that sounds serious" and asked me to talk to the CEO who wrote that code. At this point, I was still expecting that I might be wrong or at least being told that it was written in a rush or something and thank me for pointing it out. The CEO just dismissed it as being "temporary production keys" and closed down the conversation. Suffice it to say that I was not the CEO's favorite person moving forward.
I am pragmatic about it though so I still run Ubuntu for some things but it's no longer my first recommendation.
It's a beast in terms of complexity, in my opinion. But the vendor only supports running it on specific configurations.
There are a few brands out there but the Philips ones seemed better than the others and the prices were not as insane. I just disliked their marketing and buzzword filled content but otherwise they seem OK. Oh and you should know a lot of their stuff now are internet connected(disabling it will make you lose some functions but otherwise the device still works) and have touch buttons and screens etc. It's unfortunate but this seems to be where every device is heading.
I do agree with you that this seems overly complex. You can pretty much do it yourself if you'd like to take on a project. A fan and a constantly wet rag has the same function but is not as compact.
That part made me laugh and reflects my experience when I was working on "enterprise development" teams.
I'm curious about having this run on a VPS as opposed to a local VM. What does that provide you? I understand having the VM completely disconnected from your local network etc but is there anything besides that? I ask because mentioning the cost here seemed like one of the important points but that cost wasn't necessary for the experiment itself.
The businesses fired the staff and pocketed the difference. The result? Growth, at least on paper, as you're saying. Previously they were paying for 10 people and now they're paying for 2 so more profit yay! Of course this is a short term gain which might result in long term pain. That last part remains to be seen.
For a while, it felt like I'm in a minority when I was saying that it can be a useful tool for certain things but it's not the magic that the sales guys are saying it is. Instead, all the hype and the "get rid of your programmers" messaging made it into this provocative issue.
HN was not immune to this phenomenon with certain HN accounts playing an active part in this. LLMs are/were supposed to be an iteration of machine learning/AI tools in general, instead they became a religion.
Working to the point of making yourself sick should not be seen as a mark of pride, it is a sign that something is broken. Not necessarily the individual, maybe the system the individual is in.
[1] Medicine may be one example of an industry with poor work-life balance for some, specifically specialists. But job security there is unmatched and compensation is eye-watering.
The market rates were going up(and inflation going up more), people would ask their employers for an increase in compensation and get denied with broken promises. They'd wait to see if those promises go anywhere and then realize it's not going to happen so decide to change employers(and their employers act shocked).
Similarly, employment conditions were deteriorating and burn out spreading. People would ask their employers for a change in conditions such as hiring more staff and get denied with broken promises. They'd wait and well, see above.
On the other side of the spectrum, there were some with over 10 years of experience at the same place and lacked the knowledge of anything outside their employer's bubble. Their manager changed or redundancies started or something triggers and now they have to look elsewhere with their "loyalty" meaning nothing except being a detriment.
And if I may offer some more advice, it sounds like you need a technical co-founder as you're describing multiple roles and skills.
They all insisted that it was essential to have a CI/CD process but didn't even know what the "CD" part even did. Apparently you just "git push" and the code magically gets on the server. There are many ways to do deployments and a CI/CD process isn't always suitable and can have many forms, in my opinion, but I was happy to discuss any and all. But it's difficult to do that without the basics. As you said, before I was commissioned the platform had no documentation, was crumbling under tech debt and failing constantly so something like getting on the server to at least figure out what's going on was essential.
Finding a simple GUI is not going to be easy because everyone has a different definition of what "simple" means. It also depends on what you mean by "review" and "manage". There were a few web UIs for LXD containers and they were ported or used for Incus containers. Some are still maintained and active.
I personally prefer the command line and find it easier and simpler than using graphical interfaces so don't have a recommendation. When the number of containers and servers becomes large enough to warrant anything else, then that's when automation starts.
I would suggest you organize your thoughts and write down the list of what you think you need and then either pay for a consult with a senior developer or chat with a trusted technical person.
From your posts, it sounds like you need more than one role and/or the services of an agency. If money is the issue and you think you have a good idea, then I suggest you seek funding.
To me, there's a big difference between saying that migration projects can now be assisted with some AI tooling and saying that it is cheap and to just get Claude to do it.
Maybe I am out of touch but the former is realistic and the latter is just magical hand-waving.