Get live statistics and analysis of Steve the Beaver's profile on X / Twitter

"after 11 technical interviews" "your work has been accepted into our codebase" interviews are getting out of hand

the worst part about being self-made is having to learn tennis at 30 instead of 8

I was confused when the new intern said my name 10 times in the span of a 2 minute conversation, then I saw this on his desk:

average YC startup offer

software friend who pivoted to hardware sent me this

"wtfff mom i can't believe i got a 60k offer"

That's literally morse code and it's saying "·-·· · - / -- · / --- ··- -" "Let me out"

"How was the trip to SF?"

as an electrical engineer, i decided to try the software thing but guys where are the integrals? is it this "int" thing?

Top Gun was 80s propaganda to make young men aspire to become naval aviators but just end up working shitty jobs in the navy. It worked. Iron Man was 2000s propaganda to make young men aspire to become "genius, playboy, philanthropist," engineers but just end up working shitty javascript jobs. It also worked.

a big green company that makes GPUs has its own internal branch of VSCode for chip design do with that what you will

is it normal that our cracked gen-z intern whispers “weapons free” every single time he opens Vim? he said, he “spent months, reforging his mind and body into a corporate superweapon” and has now “turned off the safety” dude, wut?

Computer architecture is 50% memory and 50% compute. If you want to be a hardware engineer or a better software engineer read this

"that guy's salary is so many inches long 🙀"

with only a software background you basically need to start over. 1. Digital electronics - you need to understand what a flop is - boolean logic and k-maps - metastability - memory - finite state machines - timing diagrams (setup/hold, propagation delay) - synchronous vs asynchronous design - combinational vs sequential logic - clock domains and clock domain crossing Resources: - "Digital Design and Computer Architecture" by Harris & Harris - nandland basics 2. Verilog / Hardware Description Languages - modules, ports, signals - continuous assignment vs procedural assignment - blocking vs non-blocking assignment - sensitivity lists - RTL coding discipline (synthesizable subset) - testbenches and simulation - structural vs behavioral descriptions Resources: - "FPGA Prototyping by Verilog Examples" by Pong Chu - nandland Verilog tutorials - HDLBits (online practice problems) 3. Computer architecture - datapaths and control paths - registers, ALUs, multiplexers - pipelines and hazards - microcoded vs hardwired control - instruction sets and decoding - caches and memory hierarchies - buses and interconnects Resources: - "Computer Organization and Design" by Patterson & Hennessy - "Computer Architecture: A Quantitative Approach" by Hennessy & Patterson 4. FPGA architecture - LUTs, flip-flops, carry chains - block RAM and distributed RAM - DSP slices and multipliers - clocking resources (MMCMs, PLLs) - IO blocks and SERDES - resource utilization and constraints Resources: - Vendor user guides (Xilinx) - nandland FPGA - FPGA4Fun tutorials 5. Toolchain & workflow - synthesis -> place & route -> bitstream - constraint files (timing, pin mapping, clock definitions) - timing closure and static timing analysis - simulation before synthesis - debugging with waveform viewers and ILAs 6. System design - finite state machine design methodology - streaming vs memory-mapped architectures - interfacing with peripherals (UART, SPI, I2C, Ethernet) - DMA and buffering - soft CPUs (MicroBlaze, Nios II, RISC-V) - system buses (AXI, AHB, Wishbone) Resources: - Xilinx AXI IP examples in Vivado 7. Hardware/software co-design - partitioning work between FPGA logic and embedded CPU - hardware accelerators for software bottlenecks - co-simulation and HW/SW debug - real-time constraints Resources: - Zynq SoC tutorials (Xilinx) - “Designing Embedded Systems with FPGA” by Peter Athanas et al. 8. Mindset shift - hardware is parallel, not sequential - time is in cycles - resources are physical

openai is building its own chips and youre still trying to learn CUDA pick up an fpga and learn

"after 11 technical interviews" "your work has been accepted into our codebase" interviews are getting out of hand

I was confused when the new intern said my name 10 times in the span of a 2 minute conversation, then I saw this on his desk:

average YC startup offer

software friend who pivoted to hardware sent me this

the worst part about being self-made is having to learn tennis at 30 instead of 8

Embedded interview question Topic: power You have a 3.3 V input rail but your system operates at 1.2 V. What can you do?

as an electrical engineer, i decided to try the software thing but guys where are the integrals? is it this "int" thing?

didn't even mention the 1 year probation period

is it normal that our cracked gen-z intern whispers “weapons free” every single time he opens Vim? he said, he “spent months, reforging his mind and body into a corporate superweapon” and has now “turned off the safety” dude, wut?

"How was the trip to SF?"

That's literally morse code and it's saying "·-·· · - / -- · / --- ··- -" "Let me out"

Top Gun was 80s propaganda to make young men aspire to become naval aviators but just end up working shitty jobs in the navy. It worked. Iron Man was 2000s propaganda to make young men aspire to become "genius, playboy, philanthropist," engineers but just end up working shitty javascript jobs. It also worked.

Drop out of CS for EE right now there are infinite flavors of EEs after university there are only three flavors of SWEs: - react todo list app devs (frontend) - crud api devs (backend)

you could literally be making $700k out of college in FPGA design but you thought a 70k javascript job in SF had better prospects

"wtfff mom i can't believe i got a 60k offer"

Don't learn VHDL. If you were taught VHDL at university instead of Verilog, please comment the university name so everyone knows to not send their kids there. name and shame.