Yucel Evrimer 🇪🇺💙

2.6K posts

Yucel Evrimer 🇪🇺💙

Yucel Evrimer 🇪🇺💙

@youeee

@[email protected]

Joined Mart 2008
509 Following194 Followers
Walking Marky
Walking Marky@CitizenUddin·
Ealing Broadway "Why are you filming my car"? "Why do you think"? "Why are you filming my car" "Because you are parked on white zig zag lines". "But I'm disabled". Tell that to the police.
English
16
10
115
32.2K
Yucel Evrimer 🇪🇺💙 retweeted
Andrew Ng
Andrew Ng@AndrewYNg·
Even though I’m a much better Python than JavaScript developer, with AI assistance, I’ve been writing a lot of JavaScript code recently. AI-assisted coding, including vibe coding, is making specific programming languages less important, even though learning one is still helpful to make sure you understand the key concepts. This is helping many developers write code in languages we’re not familiar with, which lets us get code working in many more contexts! My background is in machine learning engineering and back-end development, but AI-assisted coding is making it easy for me to build front-end systems (the part of a website or app that users interact with) using JavaScript (JS) or TypeScript (TS), languages that I am weak in. Generative AI is making syntax less important, so we can all simultaneously be Python, JS, TS, C++, Java, and even Cobol developers. Perhaps one day, instead of being “Python developers" or “C++ developers,” many more of us will just be “developers”! But understanding the concepts behind different languages is still important. That’s why learning at least one language like Python still offers a great foundation for prompting LLMs to generate code in Python and other languages. If you move from one programming language to another that carries out similar tasks but with different syntax — say, from JS to TS, or C++ to Java, or Rust to Go — once you’ve learned the first set of concepts, you’ll know a lot of the concepts needed to prompt an LLM to code in the second language. (Although TensorFlow and PyTorch are not programming languages, learning the concepts of deep learning behind TensorFlow will also make it much easier to get an LLM to write PyTorch code for you, and vice versa!) In addition, you’ll be able to understand much of the generated code (perhaps with a little LLM assistance). Different programming languages reflect different views of how to organize computation, and understanding the concepts is still important. For example, someone who does not understand arrays, dictionaries, caches, and memory will be less effective at getting an LLM to write code in most languages. Similarly, a Python developer who moves toward doing more front-end programming with JS would benefit from learning the concepts behind front-end systems. For example, if you want an LLM to build a front end using the React framework, it will benefit you to understand how React breaks front ends into reusable UI components, and how it updates the DOM data structure that determines what web pages look like. This lets you prompt the LLM much more precisely, and helps you understand how to fix issues if something goes wrong. Similarly, if you want an LLM to help you write code in CUDA or ROCm, it helps to understand how GPUs organize compute and memory. Just as people who are fluent in multiple human languages can communicate more easily with other people, LLMs are making it easier for developers to build systems in multiple contexts. If you haven’t already done so, I encourage you to try having an LLM write some code in a language you’d like to learn but perhaps haven’t yet gotten around to, and see if it helps you get some new applications to work. [Original text: deeplearning.ai/the-batch/issu… ]
English
129
455
3.3K
265.1K
David Whitney
David Whitney@david_whitney·
ItsHappening.gif "The Unbearable Weight of Architecture" New talk for 2025 - let me know if you want it at your conference 🖤
David Whitney tweet media
English
3
0
18
599
Walking Marky
Walking Marky@CitizenUddin·
The Mall, Ealing Broadway 07/11/2024 I had previously raised this with @EalingCouncil only to be told "nothing to do with us". So now I will try HSE instead. Its quite incredible, due to the complete incompetence of the council to deal with these serious safety issues, the danger the public faces everyday in Ealing.
Ealing, London 🇬🇧 English
24
8
113
38.6K
James Benamor
James Benamor@JamesBenamor·
I just remembered “Levelling Up”. Did that finish? Are we levelled up now?
English
1
0
1
301
Yucel Evrimer 🇪🇺💙 retweeted
David Whitney
David Whitney@david_whitney·
@cainux Had to zoom out to fit it in
David Whitney tweet media
English
2
1
5
241
Yucel Evrimer 🇪🇺💙
@muriminyaga @kellabyte Is this not something from @unclebobmartin ? I guess it really depends on what the code is doing. If it's very complex code the. You may want comments or at least a reference to some material. We are looking at using architectural decision records
English
1
0
1
74
john murimi
john murimi@muriminyaga·
@kellabyte I worked for some company where PRs were rejected if they had comments. Reason, code should be self-documenting
English
3
1
27
1.9K
Kelly Sommers
Kelly Sommers@kellabyte·
It’s absolutely shocking how many companies source code I’ve seen that have zero comments in their code bases.
English
44
6
169
34.4K
Walking Marky
Walking Marky@CitizenUddin·
I wasn't overly keen on doing this tbh. But cyclist and pedestrian's deserve better than being constantly ignored by our cabinet member for Active Travel in Ealing, @deirdrecostigan I can't speak for others, but I have had enough. The time for talking has ended. It's now time for action.
English
12
6
58
9.9K
CycleGaz™
CycleGaz™@cyclegaz·
Great to get out in the lanes this morning.
CycleGaz™ tweet media
English
5
0
57
3.5K
Yucel Evrimer 🇪🇺💙
@ijrussell Oddly enough I've been thinking of vt220 terminals recently. Wondering in my crazy mind if I could integrate it into some form of chat gpt terminal....
English
0
0
0
48
David Whitney
David Whitney@david_whitney·
Incredible watching the number of people in the replies here be pro-finger-amputation because of some anti-regulation purist position.
Daniel Vassallo@dvassallo

There's been big drama about this technology recently. Back in 1999, a man named Steve Gass invented a system that sensed flesh and allowed the blade to stop and retract before it could cut into hands and fingers. This wasn't some gimmick. It actually worked. 40,000 people in the US alone end up in the ER because of table saw injuries. When a human makes contact with a 2lb blade spinning at 5000rpm, the outcome is never a couple of stitches and a bandaid. This is when you go to hospital with your fingers in a zip bag and beg doctors to reattach them. Or when the blade goes between your fingers and bifurcates your hand in two. Nasty catastrophic injuries. Gass' invention fixed this. The brake worked fast enough to prevent almost all these bad injuries. What could be a major catastrophe turns into a small scratch and a $150 brake and blade replacement. And it was commercially viable too. The tech worked with any regular metal blade, and the brake mechanism could be made for under $100. The brake was just a consumable item that could be replaced quickly with no tools. Initially Gass tried to license this technology to all the major saw manufacturers. But they all turned him down. The speculation is that manufacturers couldn't afford to put this on their low end saws because of the added cost of the brake and the need to make the saw sturdy enough to support the energy absorbed from the brake. Some low end saws retail for $150-$300, so even though the brake was cheap, it would have made that product segment unviable. And if manufacturers chose to put the brake only on their higher end models, they were afraid they'd open themselves up for lawsuits if they possessed the safety technology and intentionally omitted it on the cheaper models. So they didn't want anything to do with this. Then Gass went to the government and lobbied for regulators to compel the use of this technology. But back then there was no appetite for that kind of intervention and Gass got a lot of bad PR for trying to impose this on the public. So Gass decided to go with the free market approach, and started a company called SawStop which made table saws using this technology. And he proved that a lot of people were willing to pay an extra $200 to save their fingers. Who knew? In time, the other manufactures lost almost all market share to SawStop for the medium to high end saws. Almost any new saw sold in the US over $800 was a SawStop. And miraculously, the manufactures had a change of heart! Now they wanted this technology. So a few of them began developing their own versions. Almost none managed to bring anything to market, but at one point Bosch developed a similar technology called Reaxx and started selling these saws in the US. But SawStop sued them for infringing on their patent. In the end, the court ruled that Bosch couldn't sell these saws in the US, and this ticked consumers off because they said this was further proof that SawStop was more interested in money than safety. But shortly after SawStop won that lawsuit, they changed their mind. They gave Bosch a free license to use their technology. But Bosch still didn't bring back their Reaxx products. Some say that Bosch never managed to implement a reliable solution and they realized their solution would be compared to SawStop's and it would harm their brand if it didn't work as well. Fast forward to today, 25 years after Gass invented this system. The political situation is very different, and now it's looking very likely that SawStop technology will be mandated for all new table saws sold in the US. SawStop still have a patent for this technology until 2033, and if this regulation passes the other manufactures would theoretically have to pay license fees for every saw they sell in the US. But in a shocking move, SawStop said that if the regulation passes, it will release the patent for free to the public. The US public safety commission, prepared for a fight, was baffled by this news. When the news sunk in, they concluded that at this point there are no more barriers for any other company to match SawStop safety. This means that SawStop will give their rivals permission to use their technology. It doesn't mean that it will sell the parts to them, but they are not going to sue anyone who tries to make their own version. They are basically giving up their monopoly on this technology. But the manufactures are still unanimously opposed to this regulation (except SawStop of course). They claim that this will put them out of business and that cheap affordable saws are going to be a thing of the past. The cheapest SawStop table saw costs $899, while most manufactures sell saws under $300. Since they're not selling any high end saws anymore (SawStop took all of their business), the low end is what's making them money at the moment, and now this regulation will force them out of the market completely. If this regulation passes, we're likely not going to see saws on the market for under $700 anymore. And this will be a real obstacle for people looking to get started in woodworking, carpentry, and other construction trades that need to buy table saws. The regulation will also likely incentivize manufacturers to recall all the old saws, and that would make it hard for consumers to find cheap used saws without this safety feature. (This already happened with Craftsman's radial arm saws in the early 2000s.) But what about the saved fingers? 400,000 catastrophic injuries and amputations over the next 10 years could be saved if this regulation passes. That seems substantial. This feels like progress. This is what an advanced society does. The end consumer will ultimately pay for it, but would you want the cabinet maker of your next kitchen remodel risk fingers and permanent catastrophic injury just to save a $100 part? Hell no!

English
2
2
10
1.3K
Yucel Evrimer 🇪🇺💙
@CBikeLondon Ah darn... The world is strange. It's actually someone who should know better. However most lollipop people are probably not in the 20% tax bracket even....
English
0
0
0
16
CBikeLondon
CBikeLondon@CBikeLondon·
I've just realised I think a car I reported for having parked on the white zigzags of a pedestrian crossing outside a school actually belongs to the 'lollipop' lady 🤯
English
2
1
4
641