roguas

You have to add a lot of scaffolding to postgres to make it semi-immutable. datomic just is, wanna know previous user email, just go back and see. Out of the box, without thinking about it.

Why would they be unprofitable? They have a range of steps before that. Heck there are github repos that let you use youtube as free(terabytes) storage, by encoding data as noisy video. I think first step before "bankrupcy" would be to remove all videos that have 0 views in 24 months (which is most of their library).

Well, yeah but your definition is also kinda recursive "mature" sector is a regulated sector. Well restaurant schtick to me is way more mature if we stick to original vibe.

The thing is most regulation is happening where people actually get hurt. Hey, I am not super pro regulation person, but in comment above, I just tried to disprove something that seemed false. I am not going steelman pro-regulation arguments any more :)

Show me example of a thing that would prove it. EU has tons of regulation on cars(most of manufacturers are EU based) - ask any car manufacturer how easy it is to get a car sold in EU(not saying that tons of regulation is good or that difficulty of producing is good, but it is an example that goes well against your argument).

Every reasonable. Maybe I am wrong, but tco usually means no more stacktraces?

I have been on this rollercoaster of reading with ya. I'm mid 30s, 10+ yoe. When you start swe you can live under illusion your job is coding, its really not. You are building tech behind a business, depending on the business that range 10-95%.

You do not want to be coder. They will get wiped, I recon, at least in 10-20 year span. (I remember some dude on twitter was flexing a week ago, he got a quote from dev for 5k and he did "the app" in 3 evenings using chatgpt. That is all great, but it's also why we work on contracts. We mostly expand and maintain what is already there. Building new things for every new caveat is not a way to tackle serious complexity. I have seen companies that are writing an aws lambda for every small subproblem, they do it mostly cause they lack decent engineers to tackle domain complexity)

You want to be engineer working on a product, that means engaging in understanding customers, engaging in understand product/business etc. I think this is safe space to be for a long time.

Now, for a quite some time a path to this led through coding. You would join a product as junior/mid developer and senior devs will throw at you stuff that they don't want to be bothered with. You would gradually gain more knowledge and insight and eventually become one.

Near future. I think the first thing that might come up is a flow(github terms used) like this one: write an issue > click the pull request that pops up after 5 minutes (ai generated) > write a review of possible mistakes > another commit pops up (ai generated) > do the last fix manually (just some renaming etc) > approve pull request.

The above is my best effort speculation, seeing capabilities of ai things nowadays. Will this contract or expand the pool of jobs is hard to say - safer to bet on neither.

Some anxiety about this is good, but also I think that people anxious often are the first to adapt properly. Problems will hurt more oblivious people who often hand wave stuff till dawn.

depending on the max tokens, I think you can pretty easily fine-tune a model to return answers with actions required then wrap your prompt app to react to those, paste answers and "reask/reprompt" the same question...

similar stuff is being research under "langchains" term

Yeah and owner would have to have SWE on payroll to continue having it working. It's why people migrated to a more general, albeit sometimes also more confusing apps/platforms.

Right now? It made a splash but who uses ai for building their software this very moment? Nobody knows how the industry will land on this. Adoption will take time - it's not gonna be a year.

I remember after ruby on rails first demo, next day people had their websites up in ror. Here we will see, but it will be a bigger shift.

Even in the gaming industry. Typically you have people developing an engine, common frameworks... tools that downstream work to lower branches - now I can just type to chatgpt rather than go through requesting/reviewing, see quicker where I mis-designed my "framework" etc... I am afraid it's gonna be not great for junior engs all together.

Every org has varying level of engineers. This technology will make cheap grind, well cheap. We see the progression. With the speed of changes it seems we should all be worried. (as why does it matter despite being last we fell a year after)

Yes, this is also why senior engs get payed so well. Actually if you are junior dev you basically cost money, imo. However a lot of companies hire those in hopes they will make their career and stay longer - especially startups do that, as they can slide on the company culture hook way more. Also they need them as senior engs require equivalents of "secretary" to handle less import things.

I don't mean to sound mean, senior devs are also secretaries of their cto and so on.

We didn't have good notion of global social network at the time - facebook was first, kinda, so they took it all. Facebook still gonna prevail, but over time it festered a lot of specialized competition from twitter, reddit, linkedin, discord.

They did that to me themselves. They have festered the "hiring industrial complex" to outcompete for talent. Now this whole thing has to stay alive. They have to fire. Maybe the news about it will be enough, cause we also plan on hiring back.

In my estimation he is not. I "remember" office for good and bad, for most of the time even when I communicated with folks next door/nearby i would still fallback to chat. Water cooler talks is what I miss actually, but if you meetup couple of times a year - you get the feel of those people. Also now that people got so used to streaming more, its often much easier to pair more effectively (if one person drives some stuff, the other person can do other checks etc.)

I do not think 10-15% degradation is underestimated.

> Most of the challenge is understanding the internal technologies and figuring out who to talk to to get stuff done.

This is something interesting that often is skipped due to "sterile" nature of system design questions(solve puzzle). 90% of system design problems are tightly connected with how your org works internally. Can you depend on particular team or is it better to provide requested functionality internally. This is very often neglected but this moves or breaks stuffs.

Imagine you have to build a complete traffic system architecture for the city that will start settling in a year? It will likely be ongoing thing for you, you will observe how street layout works and adjust, build new streets, make city highway from point A to point B etc. but over time. Doing this apriori is going to go horribly bad.

does kotlin offer anything more than less-boilerplate-than-java?

Very rarely being first counts imo. If you are building something novel in parallel there is a good chance you will have enough of difference.

Examples: other search engines, social networks, 3d games still exist. For many folks a different graphic on your homepage can be differentiator enough. (If you ever wonder why A/B, SEO, copywriting, design/ux is important)

Yes, I run small customer oriented project, having meetings with people who spend couple of bucks is kinda ridiculous(to both, I think only super chatty people who like to was time would come), but I noticed discord is super powerful - people often share ideas or problems since its very effortless. (Also very rarely when I am not on discord other people jump in with explanations&help "this is not how you do it... you should ...")

Exactly! Ask me to prepurchase some amount of resources (say $20 upfront) + limit my capabilities early-on until first invoice.

Every org has slow-as-molasses, badly designed, illogical components. It is about ratio.

Time will tell. I don't think Musk/twitter's case will set any precedent. He is too much of a character to provide broad meaningful insights into industry. Also he has accumulated a list of failures which are rarely mentioned.

Great, here comes another depression thread :) Hold tight loosers, let's stick together through this hard time.

To a degree. Interop is useful, but you can getby with most of things without it. Long term you will learn interop as it's often times easier to write small piece of code to take java lib, rather than trusting in community wrappers.

Roof over your head. Seriously? In Europe if keep it modest you can keep a roof over your head by working in supermarket. I don't think this should be your aim honestly.

I would not say that clojure/haskell/elixir can be picked up in 1-3 months in most environments. I do agree that you should highlight broader engineering experience and keep langs/techs as merely a proof of some competence in those.

If the job mentions the technology and most clojure/haskell/elixir dev jobs do then well unless they state "looking for experienced person willing to learn" in description I would not bother them. (at least with my complete lack of experience in tech). Similarly as I would not apply to "weird-tech-i-merely-heard consultant". Also think there should be consistency on the job titles/descriptions on the side of job posters.

They weren't interested as they might have had a better candidate. That is typically the reason. It is not about you not passing a metaphorical "bar" at least that is the case for senior positions.

I have been recruiting quite a lot and at the end of the cycle you go through making difficult choices. Often times you get 2 good candidates and only one spot. So you compare them and pick a better one. The dismissed candidate can be picked next year due to lack of better candidates.

Unless it has been clearly stated in the reply that you seemed to be below their expectation of a senior candidate. And even then... a lot can change over the year and if you feel like you are better you have every right to reapply. Most companies will inform you of reapply policy terms if your are outside of it.

People in US seem so freaked about it. I don't think many people in EU would care that you have a gap. Great you will join in as fresh. Further I think you can just write "working on personal endeavors"... which you will. Many people have gaps on startups that failed and now there is even no website to show, no?

If you develop serious conditions during 30s, you're going to enjoy them longer. I think the aim overall should be balanced life oriented towards future. If whatever I am doing now seems unsustainable it's not gonna be sustainable in a year (I will just learn how to ignore it).

There is probably some fallacy to explain this. My intuition tells me that if you have meaningless job (or you feel as if) you tend to make big deal out of small decisions, assert your territory of control/reign etc.

This leads to what you described. I guess it also offers an easy cop out for them if the button will be placed in the worst possible way. "Since Jerry was also on the call and I always thought he has final say."

I don't feel it was intentended attack on OP's part. It seems he was pointing out that even a workaround for this seems crazy. Despite not really addressing the original problem, but only providing some relief - which still is pretty welcome.

Being a generalist is a meta specialization of sorts. Some people are good at assembly of pieces - almost every CTO/Architect I have admired would be considered a generalist. Such person can obtain enough knowledge to have input and be productive and doing it across concerns is pretty epic skill.

Preferably engineers I like working with are T shaped. So they are generalists to a degree they can fill in but they have their own domain where their expertise is gathered. Its way easier for me to say "its just like the ... X" and if people have some rough understanding of X we can move on. If they don't we gonna have a week of explaining/understanding whats X.