10+ years experience building large eCommerce sites, PIM systems and have leadership skills for running Engineering teams. Currently CTO, would love to have a similar role, Management or Lead /Founding Engineer.
Open to learn Golang, HTMX, Rust next to the stack above.
Uhm, same goes for job posts with degrees. There are A LOT of fake job postings right now. Im coming across postings that are open for six hours and people never repond.
You should do more research. EVs use less lubrication but they still have to use bearings you know.. and those dry ones wear out way faster then their ICE counterparts which are constantly lubricated.
Maintenance of bearings was a thing from the mid century up until the 80s when automakers starting putting out parts that had a service lifetime that exceeded the service lifetime of the vehicle. When is the last time you had your ICE vehicle in to get bearings repacked or replaced? Outside of actual damage (collision, premature part failure), these parts are typically replaced as a maintenance only in performance or enthusiasts vehicles now.
Also, many bearings in an ICE vehicle use special high-pressure, long-life, “tacky” lubricants that stick and do not usually mix with engine oil or transmission fluid. The bearings on the wheel hub most definitely do not but that’s also a part that both EVs and ICE vehicles have in common (which is also the easiest bearing to replace).
Do you have a credible source for B? Because it isn't necessarily true. As for the parts that are there, they fail more often (see TUV reliability index), they are less servicable and they require specialized people to fix them. Just wait until you get out of your warranty period.
BS article, lots of frameing; You have to look at the full picture, doesnt make sense to just zoom in on one part of the equation. E.g. doesn't take into account the energy that you have to invest to charge your car (as the charge gets higher, the amount of energy needed to keep filling rises as well), Solar panels are NOT free, EVs need to charge more and it would be fair to include extra miles that are made to find a charger that actually works (It is said only 25% works) let alone higher costs due to higher failure rates (see the German TUV reliability index).
I will happily keep driving my diesel. The people I know will only keep driving their EV until people have to start paying roadtax for them.
It is said wrong then. I drive my EV all ov er Europe and most chargers work most of the time. In three years of driving I encountered three broken stations that were shown as functional in the app.
I can relate to some aspects. After more than 10 years in IT (Also mid 30s), I sometimes I have the feeling I've seen it all. Another framework, another paradigm.. getting more of those "Oh wait that new thing you seemed to have invented is 99% similar to this old tech from years ago but its now made hipster".
I find myself scanning through news headlines, trying to up my dopamine while doomscrolling YT, but ultimately.. sometimes after I do.. I feel both TMI and empty at the same time. The world seems to have gone crazy with a constant tug-of-war on every single subject known to man. It's extremely tireing, and it makes you want to escape ( to a cabin) indeed.
I thankfully never read news and I didn’t even know about the recent Israeli occupation until like a week after the attacks started. My life is much better for it, you should try it
I was seriously thinking about using HTMX myself, but I'm kinda scared it's developer pool seems too small to hire devs from.
I'm used to proprietary frameworks, in my case I worked with intershop which uses isml. (this is comparible to something like thymeleaf). In recent years we tried to move away from this approach and go to the angular front end Stack because it's easier to hire a dedicated frontend developer than it is to hire a specialized fullstacker. Stuff can get complex when you're using something like htmx and developers don't want to fight spaghetti monsters. You don't want you backend guys to be the bottleneck, e.g. when FE just creates HTML and the backend has to tie it all together.
My question is; has HTMX thought about the pitfalls like this, and how do you counter it?
> I'm kinda scared it's developer pool seems too small to hire devs from
It is very straightforward to pick up. Unless you hire code camp devs who only ever learned React, no actual CS topics, anybody should be productive within at most a week.
While true this is divorce from organization’s hiring practices. I have to fill out a form to request someone and htmx won’t be on it. You will get someone who only know react and will stomp their feet as to why can’t we use react. A lot of bootcamp programmers are cert jockeys who don’t care or know about development, not that they can’t learn.
For the sake of your organization, get them to add a fill in the blank on that form. Picking a tech stack based on the options on an HR form is a sure way to end up using ancient tech. HR is failing you.
That's not entirely correct. It takes a day to pick up and a week to master :-). Well, it does take a little longer to learn all the nuances. Also, I've used this pattern in my personal apps (and for one app at work) and sometimes I felt that I needed to use a front end lib for a page, but after thinking about it I learned that I still didn't need a front end lib as hypermedia covered my needs.
I do agree there are times that a traditional front end lib might be needed but it is much rarer than we think.
ah, thanks! This looks to satisfy a similar use-case to LiveView which I already have access to in my current stack but it's always good to know about other options
> Stuff can get complex when you're using something like htmx
Interesting to hear that after a mention of Angular. Different ideas of complexity I guess - frameworks like it give you structure but complexity is still there, and probably orders of magnitude higher.
Ultimately you want FE devs that know the web stack well - JS, CSS, HTML, browser APIs. They will be able to pick the best tools & frameworks for the job. Something like HTMx is trivial to pick up.
Just behind react and ahead of vue, svelte & angular. So the future looks promising in that regard (although I do expect it to drop back after the initial excitement dies down).
htmx is pretty simple, most web developers can pick it up in a day or so. It does require a mental shift for both developers as well as PM/architects in how development is done, because it pushes the organization more towards a full-stack paradigm, with developers owning whole features rather than "front end" and "back end". We have a book, free online, you can read, that will help with this:
In addition to the docs (https://htmx.org/docs, which should take about an hour to read) we also have a bunch of essays on both philosophical & practical issues around htmx & hypermedia in general:
htmx tries to be "scaleable" in that there are very few base ideas to the library and you can use only a few of them to implement useful behavior (e.g. lazy loading, to pull a section of a page out of the critical first-paint path, is two attributes: https://htmx.org/examples/lazy-load) but then it provides enough hooks and deeper features (e.g. events, event filters, etc.) that as you get deeper into it you can accomplish what you want.
finally, with respect to spaghetti code, this is a perennial danger in all software development. My admittedly limited experience with SPA libraries has not convinced me that they prevent spaghetti. w/htmx you want to focus your efforts on the back end and take advantage of whatever tools your server-side environment offers to properly factor your application. Because htmx allows you to pick any server side technology (SPAs put pressure on you to adopt JavaScript/TypeScript on the back-end, since you already have a large application written in them for the front-end) you have many more options & paradigms available for organizing the bulk of your application logic.
addendum: I should mention that i try to outline when htmx is a good choice for an application here:
It's more about their back end skills as you would be hiring a back end dev who can do a little front end. No need to worry about having HTMX on their resume, just something like <Whatever back end language you like> and JavaScript. And most developers that are web developers qualify for that.
I've not used it in a team environment. I'm used to working with an FE developer or team. The last time I did js, jquery was the new hotness. For me on a personal project, I tried react and svelte. Both we monsters for building a site that needed some js elements and interaction. I was able to get htmx working quickly and I've only had a couple of snags.
One neat benefit is that I am now able to unit test (well, unit integration) my views with a headless browser because my UI is served by my backend and not a separate service that has to run with all the yarn and npm bs.
TL;DR: I'm a backend person who struggled to pick up react over a weekend but picked up htmx in an hour. Your FE devs will have no problems with htmx.
They will have to become familiar with your system's templates syntax and how to work in the backend to organize their partials and components and may even have to decide how that should all be structured.
To what Ive seen online is that Teslas have problems, but they are different to ICE cars. One of the problems that I think will play a mayor role is bearings. In ICE engines these are lubricated by engine oil which is replaced on service intervals, but with E-Cars regular bearings are used within electrical motors. Gonna make a weird comparison here, but I see the same in Robot vacuums; the grease in the (plastic) gearboxes is flung to the outsides of the casing where it dries up over time, so even though they are using plastics that negate a lot of the friction issues you get in dry gearboxes, they start to wear out faster. I think we should really start to investigate how we can make these components servicable, even if that means we have to go back to oil as a lubricant. Whats the point in going electric if we have to start throwing them away just like we do with consumer electronics because they are not servicable?
Motor oil isn't used in lubricating axle bearings or the gearbox. Those latter two are, in modern cars anyway, lubricated for "life". If Teslas, again no idea if that's the case, failed to design those components to not require regular maintenance, and then fails to define proper service intervalls, it is purely on Tesla and not the fact that we talk about EVs. Because EVs from brands with a dense service network (which is a significant revebue driver, no idea how a company can miss that) performba lot better than Tesla in the TÜV report.
> Those latter two are, in modern cars anyway, lubricated for "life".
I don't believe there is a modern gearbox where the manufacturer of said gearbox says it never needs oil changes. The vehicle manufacturer might say that, but not the gearbox manufacturer.
Case in point - my 2021 Wrangler has a ZF 8 speed auto that Jeep says never needs an oil change. ZF says it needs an oil and filter change every 100,00km.
"Life" is open for discussion and definition. Going with ZF, the 8 speed is a great gearbox, saves the gearbox. Going with Jeep gets you a warranty replacement.
By the way, it is still possible Jeep modified the gearbox in some way, most OEMs do.
Java Spring Boot and C++ , but flexible to switch!
So, heres something different; I'm currently a CTO of a Startup but we're facing some challenges onboarding a second investor. Therefore we're looking for (temporary) jobs at other startups so we can gap a small period until we get another round of funding. Looking to be hired for a NON commercial tariff. NOT trying to be a recruiter, NOT wanting to be an outsourcer or consulting company. Only contact me if seriously interested.
