I wanted to share one of his pieces with a friend, so I sent the URL in a text message, and my friend (a network technician) responded with "Uh, is that link safe?" The title of the piece was "Free Public WiFi" which makes it look even more suspicious, haha... https://computer.rip/2023-07-29-Free-Public-WiFi.html
We already have structure + style + logic in the same file, now we want to add cloud provisioning and cloud configuration? At what point is it too much?
Software built with nitric ends up with considerably less cloud related code in the application. The bulk of it is split into the provider, enabling separation of concerns.
For example, instead of AWS client libraries, environment variables for ARNs, etc. existing in the code you instead have 1 line defining a resource using the SDK. That other code is separated into the provider, enabling testing in isolation and separation.
Related: At the beginning of my career I jumped around from startup to startup doing hardware, firmware, mobile, web dev, blockchain, Alexa/Google Home, and then started consulting. Then my client pool dried up during the pandemic. When I started at my current job 3 years ago, I decided I will stay put for a while and resist the urge to look for something "better". I wanted to take on more responsibility and learn what it is like to build software and maintain it for years to come. There are some valuable lessons I learned from doing that. The world runs on the backbone of people who are willing to stay put.
I haven’t had a raise in two years. In fact some of my benefits have been reduced, so I’m making less than when I got hired.
Next week I start a role with a 20% pay bump. Staying is only justified if your company actually reacts to the realities of the world and the job market.
Yeah, as a "stayer" I've learned every few years the company will give everyone a 10% pay raises just to catch back up. I hate switching jobs so I don't want to leave, but companies haven't figured that out.
It isn't hard - inflation is a known % every years, your average raise needs to exceeded that - once someone has experience they are only worth a cost of living raise, but juniors moving up to senior should be getting large raises every year to reflect their growth. Yet HR/management never looks at inflation before figuring out raises even though not matching inflation is how you fall behind and lost people with experience.
Of course companies have not yet learned to value experience. I'm not sure what will teach them that.
the fed typically aims for 2% inflation because if they aim for 0% inflation, the economy may experiencr deflation. if you get stuck in a deflationary spiral, it's very hard to get out
also since 2% is the typical target, they have a little room to lower rates and stimulate the economy, such as what happened in covid
In my 26 years of experience I can say that's the only way to advance in this industry. Programmers are just cogs in the machine no matter their skill level. A lesson I wish I learned much earlier. I grew up with a mid-western "loyalty" mindset, and it cost me many years of fair pay.
It doesn’t though. I’ve left entire knowledge bases and bulletproof tools behind and haven’t looked back. Constant maintenance is a sign of shitty design. A hallmark of craftsmanship is leaving a supportable low maintenance environment in your wake - most people’s jobs exist in a world of shitty products and the maintenance environment around them. Linus Torvalds or Ray Eames could live wherever the fuck they wanted and their impact to the “backbone” of the world would still be immeasurable.
> Constant maintenance is a sign of shitty design. A hallmark of craftsmanship is leaving a supportable low maintenance environment in your wake
This rings true to me; I am no amazing programmer but things I have built (which managers complained took a bit too long) have just chugged along; I have almost never received a call about something broke badly or had major rollbacks etc. My longest record is a program I built 19 years ago which is still in use.
I had a role developing systems of increasing complexity of hardware, software, and interfaces and my mantra / threshold for development was always “no phone calls”. I sought to make a project robust enough to support like any other by on-site and field staff and direct my attention to the next challenge.
19 years is incredible! Congratulations on a job well done for nearly a quarter century!
At the top of every source file I work on is a copyright. I maintain a program where some of those files say copyright 2014, and I created those files the first time. It's a weird feeling sitting in a single codebase that long. Satisfying but also I can't help but wonder if there are other things I could have been doing instead.
It's never too late to change tracks; I worked with a guy who spent 20 years doing Java, he shifted to consultancy building web applications. I also worked with a guy who spent 25 years of his career as a manager at a bank, but who said fuck it and went self-employed writing CSS and advocating for accessibility.
It's never too late for a change of career if you want it.
I've been a consultant for about half my career and had runs of 8 years and 4 years (where I am now, so at least 4). Sticking around is harder, because there's a adrenaline rush of getting up to speed and knocking off the low hanging fruit, not to mention the salary bump. But sticking around is more rewarding in terms of long term impact, imo.
Does IOS count? In that case people have been compromised without clicking anything and just getting an invisible text message is enough. Browsers have exploits with sandbox escapes. Any link to a file that is automatically downloaded and opened in an application (office doc or PDF for example) can exploit vulnerabilities in the underlying application and allow for anything including remote code execution.
I like the general idea. Does it require/use apple silicon? How does performance differ between non-apple vs apple silicon?
The claim that it is 100% on your device is the only reason I would choose to use this over cloud based models. However, with the announcement of “Apple AI” your claim is basically the same only you’re asking users to trust you over Apple.
I'm not sure this would be useful to me, because I don't switch between various projects that would benefit from different tab groups, but sounds like it could be useful! Good luck.
if it's a percentage based cut then it's predetermined in a sense. leadership is just doing this as a blood sacrifice to the animal spirits of the market.
> "It's like driving on a gravel road versus driving on a freeway," de Heer said. "It's more efficient, it doesn't heat up as much, and it allows for higher speeds so that the electrons can move faster."
Does it allow for higher speeds? I thought resistance increases the number of collisions the electrons make with the molecules in the material, heating up the material, does it actually change the "speed of electricity"? If anything, I would think it might actually increase, similar to water in a smaller pipe (see current formula below). Either way, I don't know if this (possible) change in speed is in any way significant when it comes to computing.
I = NeAVd
Where Ne is the number of free/conduction electrons per unit volume,
A is the cross sectional area of the wire, and
Vd is is the drift velocity.
Latency is an issue even inside a transistor itself, something known as propagation delay. When you have a bunch of logic gates chained together the propagation delay increases and the chance for a race condition occurring also increases. The propagation delay of a logic gate is one of the limiting factors of the speed of a circuit.
Transistor gates act as capacitors in a way. This capacitance increases the delay between switching on/off. [1]
To lower this delay, we can shorten the transistor gate. We've hit a wall with how small we can shorten this length, and it is exceedingly difficult to make smaller gates without running into quantum effects.
Higher electron mobility means that the delay inside the gate is reduced, allowing faster circuits.
[1]http://ece-research.unm.edu/jimp/vlsi/slides/chap4_1.html
Switching speed of MOS systems strongly dependent [on]:
Parasitic capacitances associated with the MOS transistor.
Interconnect capacitance of "wires".
Resistance of transistors and wires.
I don't know if increasing the speed of electricity has real implications for small circuits; I guess it could make a nearly factor of 2 difference for long copper wires, but we use fiber for long connections anyway, and speed of light in glass is higher than speed of electricity in copper.
This is nothing new, this one has been on the market since 2007 https://www.adhocelectronics.com/Remodel-Press-Release/ though the new one seems more unnecessarily complicated. Just get the energy from the switch motion...
