If you recieve any recruiter inbound, I would take their meeting and then let them know your goal of getting placed at whatever type of role youre looking for.
344 karma · joined February 3, 2020
Social stuff: https://www.linkedin.com/in/daniel-wasserlauf-b12681101/
Email: daniel.wasserlauf@gmail.com
If you recieve any recruiter inbound, I would take their meeting and then let them know your goal of getting placed at whatever type of role youre looking for.
Because truly the answer boils down to "it depends" and many people will take it many different ways and not be "wrong". Publishing anonymously is a good choice, publishing publically and complying with a removal order is a good choice, not publishing is a good choice.
"Good" here being somewhat sound in that it likely wont cause the person publishing a huge life changing issue.
So yes, I think they will be able to turn a profit by charging more for the experience. Which is a humanless car.
Specifically, having agent implementation drift from the Spec.
I understand wanting to get things out ASAP. but two weeks is not the end of the world to wait as a consumer of professional software packages.
EDIT: I should actually click the link, not just read the title. Rip.
"I love that AI has taken all the creative and art jobs, so that we humans can work in the coal mines."
---
Obviously its nice that a person can make a movie or movie prototype on their own, with their own setup without needing a million dollars. But like you could also get a video camera and some friends and make a one room movie that tells a compelling story. At the end of the day, the audience wants a compelling story, and when I feel it comes from AI. I just... can't be compelled. Maybe I am out of touch.
However I have a pressing question, why should anyone trust this. I understand the process of self talk with claude can be useful for your own understanding. But this is a published result and is only really good when you've distilled it. Ideally you did real testing on it for validation.
The feeling I get from reading these articles, is "Well maybe this is true, but I don't know if I can trust it, so should I go and read a textbook?" If the goal is to distill learning here into something digestible for the reader. Then you as the author should provide proof that the statements are correct for me as the reader. I can't really tell from what's written here if you did that or not. If its just a bunch of generated articles which were useful for you in making, but for me as a reader I don't know if I get any value from them.
A common retort to this idea, is "Why should we trust anything a person says, people can be wrong too." However we typically would look for "proof of work" which AI really sidesteps here
If you are moonlighting durign the batch or after the batch and taking a job in the same industry, of course there are major concerns for your current founded company. Its extremely messy. In that specific situation you would need to be clear about your hours of work, separate computers, and a whole host of problems for the legal answer.
You potentially could be found personally liable as well if you are a founder of the company and putting your company at undue and known legal risk by taking another job in a related field which can have a claim over the company's IP.
EG if I start passing in Linkedin pages what is your expectation of the result that people would see per profile.
EDIT:
Congrats on the launch seriously hard work, just wanting to understand your scraping stance more. I've worked with a lot of tools on this, didn't mean for my initial comment to be adversarial.
---
> When we released the Claude Code Plugin for EventSourcingDB at Easter, we proudly listed everything it did not need: no SDK, no MCP configuration, not even a Docker container.
---
Is building on very unstable, stochastically so, ground. SDK, scripts, etc... are reliable.
Inside their docs, https://docs.eventsourcingdb.io/getting-started/running-even... it reads more like I would expect. So I think this initial line is meant to really be a marketing term for readers.
I understand the ergonomics and niceties of having the "AI OF THE DAY" work well with your database provider. But the framing initially in this article through me the wrong way.
Database providers are meant to be stable reliable infrastructure which rarely have issues. AI is generative and makes mistakes sometimes. Leaning into AI usage for Databases is nice, since there is a lot of information which needs to be synthesized. But having an AI literally do it all, is not really a pattern I see working in the future.
The general argument against modern internet / smartphone usage I really resonate with is algorithmic content. Specifically ones that are not simple filters a user can control. Like "Most viewed past week" Its a huge dark pattern to have content shown to a user because they watched a prior video 2 standard deviations from their norm and the next video shown is "closely related" in a graph theory sense. Mainly because it creates these silos of content for people to continuously watch content, and not see things that are outside of their local "graph" of data unless explictly shown it.
Like are you prompting like:
--- I need code that does X,Y, and Z. Write it so that the Roslyn compiler on this machine can compile and the code passes the repo's styling and formatting requirements. ---
Or something else.
1. AI will get better, and at a price point that makes sense for businesses to operate on.
2. "Managers" (non-technical users) will be as good at using AI as "frontend engineers" (technical users) or make something of comparable quality.
3. All or most technical problems can be solved by AI.
I think the title and take for this type of doom thinking is not really productive. AI is really just a tool which does some unit of work, it cannot on its own "find gold". Some people are better at using it than others, and there is a reason why the largest AI companies have continued to hire YOY for more top talent and employees.
Some jobs will be replaced, or have their expectations changed extensively. But the idea its going to take all knowledge workers jobs, is a path that needs a lot of things to go wrong for it to occur.
Specifically, even if a county hired all those officers and did what you suggest if there is no purpose other than recording all this information. I believe it would be a constitutional violation. A person has the right to reasonable privacy outside of their home. License plates can and should be recorded when there is a relevant purpose to it. Such as toll collection, or a scoped traffic watch done by a police officer or a traffic camera. The dragnet collection of data for "maybe its useful" or "we don't know when it will be useful, but it might" has generally been struck down when brought to the supreme court.
For Flock's case, they don't operate as far as I know as ticket issuing traffic cameras which have a much tighter level of control of how they operate. IE: Traffic cameras have clear signs near them notifying the drivers of their usage, in some states the issuing of the citation cannot be considered criminal (Civil issuance) and must not capture faces of drivers.
Separately, I hope the author of this project is able recognize how this project might be able to grow sustainably. Its a hard thing to know that you won't be able to work on something forever, and either building a community who wants to maintain a core project or having some company pay to maintain it could be a good idea. Linus isn't going to be around forever, but I expect that linux will outlive him by a good margin.
Open source models are not as good as claude, or GPT. But they don't need to be to fulfill useful small tasks. I think its worth considering using claude from your work to help you setup a local harness and model and then use that.
To me it feels a bit more fulfilling.
If you end up getting some spam or whatever, you can make people login in the future. But I would just wait for that to be a problem TBH. Your user experience is really nice now.
So a simple valuation would be something like Current Cash + Assets + Expected Future cash - (Expenses + Risk)