IMHO, yes. It's an attempt at remote code execution. If I don't like windows, should I add a if else clause that deletes the home directory if the code is running on windows?
1,483 karma · joined March 2, 2016
Eg "Your only senior developer knows the entire code. He just asked for a 200% raise or he leaves."
- Pay
- Fire and hire 2 juniors
- Give equity
I chose give equity and it was "wrong" because they turned out to be a "bad founder". How would I even know that? I hired them in the first place right? And 200% of what? Do I have money to pay them? Am I a startup that is able to pay them or is paying going to risk the entire company?
PS: the "right" answer was "hire 2 junior developers" btw
I feel like this is a really detached piece on the realities of work and capitalism. Did a decade of prosperity in software industry made people forget what work is?
In capitalism (I mean in a job) you are paid to build what others want you to build. You are selling your time and effort. Either that or you build your own thing and monetize it. If "rent wasn't an issue" most people would paint, dance make art, explore, play, create. But for most people, rent, food and healthcare are the issue...
Pick them from wild areas
I'm gonna dispute this. We're currently profitable, and to do so our growth is just "good" (80-100% yoy). We're also raising a smaller amount because we want to return to profitable as soon as possible, and repeat the cycle. Being profitable hasn't been a big selling point in our discussions.
Either our growth is not high enough, or our round is not big enough, as they are so used to seeing ridiculously inflated projections from the last decade.
Furthermore being profitable also removes a lot of leverage from investors. That might make them shy away from a discussion because they know they can't twist out arm as easily.
I agree tho, I wouldn't want to build our company any other way than being profitable. Just saying that being profitable is not something investors seem to like as much as we thought.
Add to that the declining experience of email with so much marketing and trash landing in the inbox (and sometimes Gmail categorizing important emails as "Updates")
That's why grace periods for these situations are important.
Who uses SMS? This might be a cultural difference, but in Europe they are still used a lot. And would you be ok if your utility company cut your electricity bill just with an email warning? Or being asked to appear to court by email?
It was a wake up moment for me about keeping billing in shape, but also made me understand that a cloud provider is as good as their support and communications when things go south. Like an automated SMS would be great before you destroy my entire work. But because they are so cheap, they probably can't do that for every 100$/month account.
I've had similar issues with AWS, but they will have much friendlier grace periods.
Most of the solutions with 2 way sync I see work great in simple rest and hobby "Todo app" projects. Start adding permissions and evolving business logic, migrations, growing product and such, and I can't see how they can hold up for very long.
Electric gives you the sync for reads with their "views", but all writes still happen normally through your existing api / rest / rpc. That also makes it a really nice tool to adopt in existing projects.
No redundancy, no backstop. If any of the stitches gets cut, the entire piece can unravel completely.
We're so used to redundancy, but sometimes you just need to get things done, and it's ok if it's all a deck of cards.
About HDR on phones, I think they are the blight of photography. No more shadows and highlights. I find they are good at capturing family moments, but not as a creative tool.
I've found that brief high C02 levels are very good for activation, and to get out of a lethargic state. I don't know if a mix of cortisol and vasoconstriction and dive reflex triggered by the CO2, but I feel like it's a tool I have on my toolbox whenever I need to so something difficult or that requires a lot of will power.
It's not for everyone tho, because many people can't get past the initial urge to breathe, and would probably freak out with the first involuntary contraction.
Because I have a feeling they want to find an "environmental cause" only if it's not the one that is the driving engine of the economy.
edit: Also their decision to make it just one way sync makes a LOT of sense. Write access brings a lot of scary cases, so by making it only read sync eases some of my anxieties. I can still use Rest / RPC for updating the data
Spoken word is one of the most primitive and human ways of communicating information. Written word appeared as a replacement to spoken word, because there was no other capable medium of information. Now we have mediums capable of doing so, why not use them instead.
Also you're somehow implying that because I'm doing the dishes I'm paying less attention? I think that's a really big assumption, and will probably vary a lot from person to person.
This month I spent many hours listening to lectures on youtube about geopolitics on the Asian continent from the naval war college. Sure I could have read it, but nevertheless I got curious about a topic, engaged in it, and "followed the rabbit holes"
I think there is a case to be made that we need to be more active in information seeking, rather than just being fed what the algorithm suggests you - on that topic Technology connections recently made a really good exposition of that issue -- https://youtu.be/QEJpZjg8GuA -- But it should not be about the method of ingesting information, but the quality and the intent of it.
The EU is realizing that one of their major trade partner, who they trusted with critically important goods and services, might pull the rug under their feet.
Not to mention that the EU in itself is already a huge achievement in terms of free trade agreements between EU countries.
I use ORM query interfaces 80% of the time, and for performance critical queries I can use direct SQL. But the query sanitization, smart preloading and performance checks, schema management and migration tools they often provide, and type checks / hints are really nice features of ORMs.
Furthermore, ORMs are ESPECIALLY useful in teams where you have more junior devs who need these guardrails.
I think the issue here is trying to reinvent a new ORM.
So far, everyone that elected to use GPT did much worse. They did not know what to ask, how to ask, and did not "collaborate" with the AI. So far my opinion is if you have a good interview process, you can clearly see who are the good candidates with or without ai.
There's no hard rules in software engineering, and all best practices should be put into context. You don't know what monsters lurked in the old code base. So yes in some cases (but not often) re-write is a good / only choice.
Also, if this is the cohort of people joining the DOGE initiative, I'm even more afraid that I was before.
There is a big sample bias here. The community of hackers is generally intelligent and curious. The laws in place were not necessarily made with them in mind, but for people who will take homeopathic remedies, use energy crystals.
Maybe if you're smart enough to avoid detection and navigate the legal hurdles, that is the acid test (heh) for the competences and diligence these things require...