I disagree. I don't know what day it is, have to check and I dont want to run this computation even if I knew without checking. Likely this is preference thingy, you prefer precise, I prefer convenient.
I dont think AGI is required. But multimodality for sure and some piece to plan/execute actions. Prompting techniques now, would land you clear tasks, validations and such, given some objective "replace table leg". A unit to process this would be required.
Generally, yes, but I also think the fn1,fn2,fn3 can happen independently (which is why its powerful). So items of collection may be at different steps.
Hm, when you are solo coder doing a product, discord is super valuable. You get to interface with your customers in casual way + you get a bit of free knowledge/quirks base. Also if something is wrong with cloud provider, I can broadcast easily etc. All those functions can be ramped up separately, but the goal for me is to code and deliver on a product. As everything it has tradeoffs, but I wouldn't make snap judgements that discord is just a lazy excuse. Its a great tool for comms with low friction.
I think you are taking a too strong stance on interpretation of those stories by holy books. What stood out to me is the case of Islam twisting Abraham story. Perhaps they were not trying to shame jewish version, but were displeased with depiction of god as "playing games" and chose to present him as "wise observer that intervenes". Just wanted to provide an extra look, but if you have some more proof/info on that interpretation (I am not knowledgeable on the subject) I would love to hear.
Change company. Honestly. If you go as far as to forbid your partners in crime (workers sigh..) to explore new uncharted territory at all - well ya know someone will/might just win by not doing that.
At a point of sacrifice I would put breaks and evaluate utility and future of relationship. If we have reached a place where I am expected to be on negative return, hm it requires some roadmap.
I am from eastern europe, my dad was vice principal in high school. I would pay good money today to smell again that dusty computer lab room filled with good'ol 386 and mario sounds.
Well since you use clojure, you probably know that to have small codebase, people often pick clojure. Going from point A to point Z quickly is rarely a goal for startups, going through A.. B... C... quickly, is the goal. I am still looking through all this, but a thought of having to bet on some java api + hope and pray it will jump over all unknown hoops, hm.
Comparisons to twitter are unfair, twitter is not really technical gem or is it? It's pretty impressive to build it with 3 ppl in 3 months, but hmm also seems feasible using other tech, given all blueprints are out there.
When you put metrics on something. You see its limits... then you push them. Every industry does that till they find sky is the limit but its actually about balance.
Not really. Any large city has this problems, even cities that excel in public transport like Tokyo. The commute might still be upwards of 40-50 minutes unless you live near tech hub of the city which typically is super expensive and also risky as often there are several hubs in one large cities and now you have to move places to regain comfort.
At the same time it makes it shitty for regular folks working remote and like a normal person having bad periods from time to time. There will be way less understanding towards... You are trying to do the right thing, but the dial if turned too tight might blend wrong people.
Weird set of choices.
So clojure and elixir can be your hooks into fp community. To a degree they are similar in being dynamic fp langs with macro capabilities.
Python and node are more like "common dev platforms" these days.
I would first establish if I am looking for job market utility (both elixir and clojure offer great utility, but job market is more problematic). Yet if you are looking to learn and expand your dev horizons elixir or clojure are great options (I do clojure so a bit biased towards it).
If you have startup and no docs + complicated product -> discord is super easy first step. It also has a nice loop: if you see a question over and over, move it to faq, if its still repeated perhaps add better labeling/hints to your forms, if it still persists, damn maybe rethink your offering/product(or accept CS as vital part).
In the end I don't want to deal with meta stuff. I want a nice seamless product period. Discord while awkward is a good first thing that you should absolutely have - you can bootstrap it in 10 mins. (Depending on your customers ofcourse, if you are selling insurance to old folks, for obvious reasons it's not good)
I think you can. It is a separate "crime". You would get 2 cases one for fair use (which if you are quoting, commenting, reviewing, generally repurposing content and it is in fact fair) and second case for license/terms breach and/or illegally obtaining this piece of work(for example if you stolen it from bookstore).
I have not read Graeber's book in full, but his umbrella statements seemed off putting(childish). If you can operate a company with good outcomes on half the staff by all means go do that. It will be extremely easy to compete.
I think his blind spot is that some people are doing exploratory work that has 10% chance to be impactful. With enough bad luck this person can work 10 years without meaningful results and even when the results come, you will be happy for 3-4 months before drowning again. Still if you skip it all together you will have a company that will fall out of relevance in 3-5 years due to lack of progress.
Basically he fails to see novel progress is really rare and assumes the optic of worker, but manager's optics is: 10% is fine, I am just gonna hire 10 people, pay them well and have meaningful progress every year.
Crypto was not designed to bypass state but to provide transparency and stability to currency/money. Say you are in Venezuela where your money is constantly devalued and your political power is diminished, every option that you have to survive that doesn't harm people directly should not be considered in high horse moral terms.
How same could be said? React makes calls to json api typically - both sides are very inspectable. Given that you have to resort to session for state, things can get messy on the data layer (a poison pill for stateless rest json api)
> people who own stuff have the power to take money from people who don't.
People who have invested capital, hedged risks, setup maintenance, did marketing etc.
Now we can agree that housing is very specific branch of economy where if you have upper hand(capital) you can be dealing cards to those who don't. There are ways to address that without the canvas of grand narratives(extracting labour etc).
I think 5h of work is a ton in SWE.
IF you can focus, isolate important work and put hard 5 hours... kid you are going places. If not, you will not be going places while putting 10 hours, I think.
Humans differ. If the information is not controversial most often accept it and move on. If the information is controversial most handwave, but a large group further checks and if they arrive different conclusions they start to get active on replacing incorrect info.
Agreed. I also think on avarege you are injecting much more personal data when using LLMs (from which ads can have crazy levels of profiliing). Just because we do not see ads now, doesnt mean they won't appear one day.
We decided for fun to do a small project in htmx (we had to pick something, one person opted strongly). Yeah, I was cringing and still am. I fully support frontend/backend split status quo.
For stuff that is uncomplicated I much prefer svelte as it still keeps the wall between frontend/backend but let's you do a lot of "yolo frontend" that is shortlived and gets fixed. I run small startup on the side" svelte fe + clojure be. It works great as I have different acceptance for crap in frontend (if I can fix something with style="", I do and I don't care). I often hotfix a lot of stuff in front where I can and just deploy to return later and find better solution that involves some changes in backend.
I can't imagine that for moving a button I would have to do deployment dance for whole app that in my case has 3 components(where one is distributed and requires strict backwards compat).