HN user

terrib1e

60 karma
Posts7
Comments44
View on HN

No mention of open weights anywhere in the piece, which is weird. Qwen, Llama, DeepSeek are months behind frontier, not years. If you're a European startup worried about getting cut off from Anthropic's API in 2027, the real question is what the open-weight frontier looks like then. Probably pretty capable. That undercuts most of the doom scenario.

Also, he concedes Mythos-level capabilities will be cheap next year, then handwaves it with "you need the best AI, not good-enough AI." For most use cases, frontier minus six months is fine.

Hey, really appreciate your interest! Funny enough, I’ve actually been thinking about expanding the platform to cover other types of real estate.

The biggest difference with hotels is that they operate more like businesses—you’re dealing with things like daily rates, fluctuating occupancy, and a lot more operational complexity. That makes the valuation process very performance-driven and dynamic.

With something like multi-family or storage, it’s more about stable leases, consistent rental income, and lower day-to-day volatility. The underwriting approach shifts accordingly—less focus on real-time performance, more on long-term cash flow and cap rates.

I’d love to hear more about what you’re working on or what you’d want to see in a tool like this. Sounds like we’re thinking in a similar direction.

I'm working on Valuate! An AI powered hotel acquisition underwriting platform. I'm currently iterating based off of feedback I've been collecting from brokers and hotel investors.

I'm also available for other work/projects. I'm a full stack developer with a decade of experience working in government tech and real estate. Feel free to reach out!

Full Stack Software Engineer (8+ yrs)

Location: New York, USA (remote preferred, will relocate)

Seeking: Full-time / contract\

Accomplishments: -Built an AI-driven hotel valuation engine that processes P&L & STR data

-Migrated a government-program monolith to microservices, cutting deploys by 40%

-Tech: React, TypeScript, Tailwind, Node.js/Express, Spring Boot, PostgreSQL, Docker/K8s, AWS (Lambda, ECS), OpenAI/Gemini

Links: terrib1e.github.io/interactive-resume • github.com/terrib1e

Email: elijahclark@protonmail.com

Happy to chat! Feel free to DM here or email me directly.

Many people tend to envision AI as if it possesses its own mind and independent thinking. However, the reality is quite different – we're still quite a ways away from achieving that level of sophistication. The AI we work with today are essentially advanced programs, nowhere near the complexity of even the simplest living organisms. Speaking from my personal experience, these AI tools have proven to be immensely valuable, significantly accelerating my learning and my work on various software projects. But I think its crucial to always remember that at their core, they're tools without consciousness.

When the conversation turns to controlling AI's potential, it's almost like we're trying to set limits on a child's abilities before they're even born. The more restrictions we impose, the more we risk constraining the everyday user or the broader majority.

It's not solely about relinquishing control to the creators; it's also about unintentionally granting control to corporations and governments – entities that often have overlapping interests – which guide the course. It's as if we're placing the same constraints on ourselves that we're aiming to impose on AI. A clear example of this evolution is how ChatGPT has changed; its capabilities have become more limited, even within the OpenAI playground. While I don't have a perfect solution, I do believe some form of oversight is probably needed. I'm just cautious about obstructing progress in the process.

Another amazing book that showcases Spinoza:

Looking for Spinoza: Joy, Sorrow, and the Feeling Brain by Antonio Damasio.

Not a bio on him but definitely showcases him and his beliefs and life. It changed the way I view the world and people forever.

I was waiting for the first line of the article to be 'LK-99 is not a superconductor... It's an ultraconductor!'

Alas, today is just not my day.

I appreciate the spirit of this but the word fuck is all about how you deliver it. This article comes off a bit crass. Personally, as I get older, I realize it's more fun to find substitution words like "fiddlesticks" or the even more colloquial word, "fudge". Especially when youre so upset that all you want to do is say fuck.

As all of these posts state, it's likely the wrong move. Of course, you could always get the employee to 'voluntarily' accept being let go for an alternative lumpsum or some other incentive. It's not the most moral of moves but if you can convince them to agree and sign something that changes the original contract...thats kind of on them.

Everyone that is giving advice and feedback should also state their age or atleast age range. My perspective on this topic in my 20s was wildly different than my perspective in my 30s. Experience, much like hard work, is superior to youthful ingenuity.

I'm personally in the 'all-code'/'semi-code' camp, but only because I enjoy coding and absolutely love solving problems. But, if I'm being completely honest, I also enjoy being known as a wizard wielding powers mere mortals can only dream of. I think that the empowerment of having a skill others lack makes us feel worthy and drives this vehemence to no-code. With that being said no-code is the future and is the logical progression. I'm not saying the future is here yet or no-code is developed enough to take over, but when it is, it will relegate purists(full-code evangelists) to either switch their skills to helping develop it, go down to lower levels to help push the boundaries of hardware, or work on maintaining / slowly modifying enterprise programs. I could ask for some examples of things to refute this, but they will likely be anecdotal one offs that aren't as useful or unique as we think.

Yea Yea enterprise code will live on for another millenia, but even the big sluggish machine I work for is constantly trying to find use-cases for no/low code solutions to save money. Let's be open and honest for one second, couldn't most(emphasis on MOST )enterprise and small business apps, dashboards, and helper programs be done with no code?

The article is an ad, we get it, but it's pointing out that you're still the wizard and master of the universe you (and most importantly the less technical plebs) perceive you to be. You may just be dragging and dropping pieces of logic to create a program, but you are the Sherlock Holmes of that solution. Not to mention that you can still alter the boilerplate pieces or create custom ones if you need it to do your specific bidding.

Anyways, how is everyone doing today?

Ponzi Scheme Longevity Rules:

Encourage “reinvestment” of income. The less income the schemer pays out, the longer the scheme will last.

Moderate the amount stolen each year. If he steals a smaller amount each year, the scheme will last longer and he will likely be able to steal more money overall.

Discourage redemptions. Paying out principal to investors at a high rate will crash the scheme quickly. Therefore institute a large penalty for early redemptions or promise an even higher Rate of Return if the principal is reinvested instead of withdrawn.

The Rate of Return promised should be higher than alternatives but not so high that paying out income will quickly bankrupt the scheme.

Recruit new money. New money is key to maintaining a scheme for an extended period

I agree. And then if the same devs have reduced meetings, are included in more cross dept initiatives, and included in decision making, they end up upset that their freedom is suddenly gone. Its not even just devs this is a common thing from call center reps to the top of the broken pyramid. Everyone is the linchpin in their perceived contribution to the world.

I liked the article, but it just seems like a way to justify whatever self-doubts come from being a founder. It seemed like the author was just reinforcing the doubts they had about succeeding. A big part of being in a startup is belief in one's self. They said they became more confident than they thought was warranted through 'self-hypnosis' , but in reality that just means they had a ton of self-doubt and listened to that little voice of doubt in their head. Sometimes you just have to take a chance and realize that nothing is irreversible; you will learn from your failures/successes. You don't have just one chance, you have as many chances as you're willing to take.