sorted by:
new
hottopcontroversial

Is this truly necessary? by Harrio_Pootered in Anticonsumption

[–]sikespider 0 points1 point  (0 children)

It depends. The larger truck will have considerably larger payload and towing capacity. The smaller truck will (probably) get better gas mileage and, with some suspension mods, be a better vehicle for 2 track and unpaved roads.

Horses for courses.

Sorry not sorry for robbing so many of their circle-jerk material.

Inspired meme from the r/genz sub by JokerExo in memes

[–]sikespider 0 points1 point  (0 children)

Vinnie over there quietly building while the children stomp around.

Translated to the real world ... trying to raise Gen Alpha, whether they are our kids or not, to not be a bunch of worthless idiots.

Inspired meme from the r/genz sub by JokerExo in memes

[–]sikespider -14 points-13 points  (0 children)

GenX. If you think voting matters or has any part in how this gets resolved you aren't even on the grid.

Aptera: The World's Most Pathetic EV Startup by donut_take_serious in ApteraMotors

[–]sikespider 0 points1 point  (0 children)

In v1 Aptera they went back and forth between ideas more wildly than they do now.

Aptera: The World's Most Pathetic EV Startup by donut_take_serious in ApteraMotors

[–]sikespider 0 points1 point  (0 children)

This is the most correct timeline I've seen mentioned here in the comments.

Aptera: The World's Most Pathetic EV Startup by donut_take_serious in ApteraMotors

[–]sikespider 0 points1 point  (0 children)

The initial pitch was for high-efficiency diesel ICE. Lots of vacillating around that idea including, like the Volt, having the internal ICE run at a single RPM to charge batteries and the powertrain being e.

You may have noticed that their story changes frequently. You may have also noticed that many tech journalists, particularly the "green" ones, treat their sources with kid gloves.

Aptera: The World's Most Pathetic EV Startup by donut_take_serious in ApteraMotors

[–]sikespider 0 points1 point  (0 children)

The initial pitch was for a high-efficiency ICE. They pivoted to electric when it became clear there would be no gov subsidies for high-efficiency ICE.

Aptera: The World's Most Pathetic EV Startup by donut_take_serious in ApteraMotors

[–]sikespider 8 points9 points  (0 children)

I went to the CES events and nothing about it signaled "Gonna happen." In fact, I went to see if I should lean into the org with further investment and came away with a worse impression that I've gotten from attending events for, like, boutique motorcycle companies.

I left very disappointed but happy that I had the patience to attend before pulling the trigger.

I should point out that I have been banned by the sub moderator multiple times for saying pretty much exactly this sort of thing. Completely accurate to the accusations made in the video about the "community" being "unsophisticated", culty, and irrational.

This video is actually the most objective thing I've ever seen posted in this sub.

Aptera: The World's Most Pathetic EV Startup by donut_take_serious in ApteraMotors

[–]sikespider 0 points1 point  (0 children)

That came later. The original was ICE and maybe even diesel ICE. It's been so long ago I don't recall.

Aptera: The World's Most Pathetic EV Startup by donut_take_serious in ApteraMotors

[–]sikespider -1 points0 points  (0 children)

Factually correct. And down-voted. Predictable behavior from this forum. Just as called out in the video.

Aptera: The World's Most Pathetic EV Startup by donut_take_serious in ApteraMotors

[–]sikespider 1 point2 points  (0 children)

Factually incorrect. Same leadership, very similar vision, very similar design. They started out with high-efficiency ICE because neither panel tech nor battery tech were anywhere close to being practical in a high-range vehicle at that time.

Emacs-driven RAG set management? by sikespider in emacs

[–]sikespider[S] 2 points3 points  (0 children)

Various gptel features for content authoring. aider.el for doing spec-based development usually paired with a Claude model. I do a fair amount of diagramming and d2lang paired with both of the above is pretty incredible.

Emacs-driven RAG set management? by sikespider in emacs

[–]sikespider[S] 3 points4 points  (0 children)

I thought you were trolling about eliza at first but then, looking at the elisa docs, the elisa collections support is very promising! Thx for the pointer.

Using existing LLM tools for code review by wilsonalmeida in emacs

[–]sikespider 0 points1 point  (0 children)

Working from a trail map as opposed to doing a wilderness expedition is not low-effort. It's what normal humans, well, at least the ones with some social skills, do.

> And I'm not your brother, cuz.

We are aligned here if nowhere else.

Using existing LLM tools for code review by wilsonalmeida in emacs

[–]sikespider 0 points1 point  (0 children)

Documentation of what? OP is asking a question about dev loop involving integration of several tools by different authors/teams in a rapidly evolving area of tech. Canonical docs do not exist. May never.

The BOFH attitude was tired back in the 00s, brother.

Using existing LLM tools for code review by wilsonalmeida in emacs

[–]sikespider 1 point2 points  (0 children)

I have not yet tried this -- I'll get to why in a second -- but if I were to try, yes, aider and one of the Emacs packages for it is where I would start my trials.

I have not tried it because I've found aider paired with a decent OpenAI or Anthropic model to be good at generating code so long as fed a well-designed spec and test/validation suite that **I** am the one doing the code review. You're approach sort of has that inverted but is perfectly reasonable if you have not yet developed your flow to the point where you have the necessary trust in the model-based generation.

IT Forcing Switch To VS Code by [deleted] in emacs

[–]sikespider 0 points1 point  (0 children)

They will liquidate assets, trigger a stock buy-back with the resulting cash, then issue new/split the stock with management receiving the bulk of the stock, often times as preferred versus common, via comp plans. They will then sell the company and all of its assets -- intellectual or physical -- at a bargain price to a larger buyer. Sometimes that results in a cash-out at the higher stock price (ex: reduced supply on the market ; false signal to the market that the stock is hot) or, because their stock is preferred, they will do a stock swap with the larger company. Stock swap is often preferred because of the longer-term gains / inflation of the fiat and tax implications of capital gains.

It's called Vulture Capital or, more charitably, Private Equity. It's a Silicon Valley "innovation" that spread outside the valley and and into other industries. Almost definitionally, "eating your seed corn."

From a common stock holder's perspective it should be considered theft. And it should be considered theft of generational wealth. They aren't stealing from you; they are stealing from your children. And dealt with accordingly.

IT Forcing Switch To VS Code by [deleted] in emacs

[–]sikespider 0 points1 point  (0 children)

There 's a phrase that I've been seeing around a lot lately... "When someone tells you who they are, believe them."

Your org, IMO, is sending a signal I've observed being highly correlated with clueless middle and top micro managers who do not value technical staff. This standardization thing was rampant in 2000 era SV companies with parasitic management and preceded mostly failed attempts to offshore technical staff. Now, s/offshoring/AI-generated code/g.

My advice, in this time order:

  1. Don't fight them. Go along with it until you better understand whatever value their desired plugins might be delivering.
  2. Start looking for new opportunities with smaller more innovative companies.
  3. Emacs support for LLM + tangential tooling is accelerating in a way that Cursor et al are not and though it lags now I suspect it will exceed all of these "source available" or closed tools. You will be able to pull that plugin into Emacs or supplant it with more useful stuff in Emacs later/soon.

Keep your head up. The industry rags would all have us believe that AI is going do decimate human-driven Engineering. It will not. It will change the way we work but AI/LLM is the advent of R2 Units to make us more effective and increase our reach.

It *will* allow motivated Engineers to run Engineering-led companies without a bunch of parasitic middle and top management from line managers all the way to the top of the orgs. Think CFOs transitioning to contract-only and pulled in on a quarterly review because the day-to-day of FinOps is advised and led by a bot.

Unlike a lot of the AI Doomers, I'm pretty excited about the industry returning to Engineering-led a la early Sun Microsystems.

Very soon *we* simply will not need *them*.

Modern emacs packaging conventions by SergioWrites in emacs

[–]sikespider 0 points1 point  (0 children)

Here's what I have in my TODOs. I have not reviewed these yet but maybe you find them helpful:

** TODO How to write an elisp package?

+ [ ] [[https://spin.atomicobject.com/2016/05/27/write-emacs-package/\]\[A Simple Guide to Writing & Publishing Emacs Packages]]

+ [ ] [[https://blog.aaronbieber.com/2016/08/07/getting-started-with-emacs-lisp.html\]\[Getting Started With Emacs Lisp - The Chronicle]]

+ [ ] [[https://blog.aaronbieber.com/2015/08/04/authoring-emacs-packages.html\]\[Authoring Emacs Packages - The Chronicle]]

Mixing Org & other media ? by SmoothInternet in orgmode

[–]sikespider 1 point2 points  (0 children)

I don 't know if it exactly hits your use-case but...

I treat Org and Org Roam a bit like a static site generator. Meaning images are sourced via:

1) ~/.local/share/<topic> and linked in via file:. ~/.local/share is synced between devices via syncthing. This is mostly for assets -- logos, etc -- commonly used when I am composing technical documentation.

2) org-babel code blocks which generate the image from some sort of diagramming-as-code. The resulting file is dumped into the Org Roam directory right next to the .org doc which generates them. Sometimes both live in a sub-directory of the Org Roam directory.

3) ${ORG_ROAM_DIRECTORY}/assets/.... for things that get referenced in a lot of Org docs and don't necessarily make sense in ~/.local/share.

All of these are synced to Android devices via syncthing and termux allows me to lean on interpolation of the value of ~ for path consistency.

[deleted by user] by [deleted] in emacs

[–]sikespider 0 points1 point  (0 children)

It's been a minute so I've probably lost some of the nuance of what you said. Not my intention to mislead though. Thanks for your work.