Podcasts about google code

Plus Can AI Generate Your Next Meal? Like this? Get AIDAILY, delivered to your inbox, every weekday. Subscribe to our newsletter at https://aidaily.us OpenAI Unveils ChatGPT's Enhanced AI Search Tool OpenAI has introduced a new AI search tool for ChatGPT, allowing users to access real-time web information with cited sources. This update, part of the ChatGPT Plus plan, integrates various search features, like product recommendations and news links, alongside ChatGPT's conversational abilities.  AI Writes Over 25% of Google Code, Reshaping Software Engineering Google CEO Sundar Pichai revealed that AI now generates over 25% of Google's code, supervised by human engineers. This shift aligns with a growing industry trend where developers use AI to speed up workflows and enhance code quality. As demand for AI skills rises, engineers face pressure to adapt, integrating AI expertise and oversight into their roles. AI Recipe Generators Can Elevate Your Meal Planning AI recipe generators like Mr. Cook, ChefGPT, and DishGen offer innovative solutions for meal planning, turning pantry ingredients into diverse recipes. Users can manage preferences, reduce food waste, and find recipes suited to dietary needs, easing the cooking process and adding creativity to meals. What if AI Is Actually Good for Hollywood? AI-driven visual effects are reshaping Hollywood, enabling complex de-aging, dubbing, and reshoot avoidance. Innovations like Metaphysic's AI for face-rendering let filmmakers, including Robert Zemeckis in Here, digitally de-age actors like Tom Hanks, saving costs and preserving realism. AI's creative potential intrigues filmmakers, though industry fears persist, including job losses and ethical dilemmas around likeness usage. AI Tool for Hair Makeovers Could Save You Hundreds AI apps like Facetune let users try new hairstyles and colors virtually before heading to the salon. Offering features like color selection and haircuts, the app helps users visualize their ideal look and avoid costly mistakes. Though not perfect, Facetune provides a fun, affordable alternative to traditional consultations. AI in Hiring to Surge by 2025, Raising Bias Concerns A recent Resume Builder survey found that 70% of companies plan to use AI in hiring by 2025, with 82% already screening résumés and 40% using AI to communicate with candidates. AI also helps evaluate skills, onboard employees, and screen social media. However, with 21% of companies rejecting candidates “without human review,” concerns about bias are growing, as experts urge limiting AI's role in nuanced hiring stages.

Do you prefer multistory episodes, single story episodes, or a mix? Let us know! In this episode of Discover Daily, we explore Reddit's remarkable journey to profitability, marking its first profitable quarter since going public with $348.4 million in revenue and a 47% increase in daily active users. The platform's success is bolstered by strategic AI partnerships with OpenAI and Google, transforming Reddit into a valuable data source for AI model training while creating new revenue streams through licensing deals worth $203 million.Meta challenges Google's podcast generation dominance with NotebookLlama, an open-source alternative that transforms text documents into AI-generated podcasts. While the system offers impressive customization options and flexibility, it currently faces limitations in audio quality and speech overlap, highlighting the ongoing competition in AI-powered content creation tools.The episode culminates with an in-depth look at Google's revelation that AI now generates over 25% of its new code, signaling a fundamental shift in software development practices. This milestone showcases how AI is transforming the tech industry, with the company's internal AI model, Goose, leveraging 25 years of engineering expertise to boost developer productivity while maintaining human oversight for quality and security.Perplexity is the fastest and most powerful way to search the web. Perplexity crawls the web and curates the most relevant and up-to-date sources (from academic papers to Reddit threads) to create the perfect response to any question or topic you're interested in. Take the world's knowledge with you anywhere. Available on iOS and Android Join our growing Discord community for the latest updates and exclusive content. Follow us on: Instagram Threads X (Twitter) YouTube Linkedin

More from The Lunduke Journal: https://lunduke.com/ This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit lunduke.substack.com/subscribe

Andreas Ekstrom là diễn giả TED Talk có kinh nghiệm diễn thuyết ở tại 30 quốc gia khác nhau. Anh được vinh dự nhận giải thưởng “Diễn giả của năm” tại Thụy Điển vào năm 2019. Andreas Ekstrom cũng là tác giả của 9 tựa sách nổi tiếng, trong đó có “The Google Code”, viết về cách mà gã khổng lồ Google thay đổi cách hoạt động của xã hội. Đồng thời, anh còn được biết đến là nhà nghiên cứu về tương lai của công nghệ.   Trong tập mới nhất của The Quốc Khánh Show, host Quốc Khánh vinh hạnh được trò chuyện cùng khách mời Andreas Esktrom về những điều mà chúng ta đang lầm tưởng về công nghệ, cũng như hướng đi đúng đắn cho doanh nghiệp trong thời đại AI.   Mời các bạn cùng lắng nghe!   Andreas Ekstrom has been a TED speaker, with close to two million viewers, has won several awards, has spoken in just over 30 countries, and has been translated into over 30 languages. He won the Swedish ”Speaker of the Year” award in 2019. He has written nine books, including “The Google Code”, Andreas looked at the search giant and what it means for society. Also, he is a digital futurist.   In the new episode of The Quoc Khanh Show, host Quoc Khanh is pleased to have a talk with Andreas Ekstrom about the misunderstanding in using AI, as well as, the right direction for business to grow in the AI revolution.   00:00 - Mở đầu, Giới thiệu khách mời Andreas Ekstrom 02:56 - Vai trò của chuyên gia nghiên cứu về tương lai của kỹ thuật số 03:45 - Cuộc cách mạng trí tuệ nhân tạo ở hiện tại 04:42 - Câu chuyện con người và công nghệ hỗ trợ lẫn nhau 06:58 - Khi lợi nhuận không còn là mục tiêu cuối cùng của doanh nghiệp! 08:32 - Đừng xem AI như một phép màu 11:52 - The Google Code 13:51 - Một xã hội không tham nhũng có tồn tại? 16:43 - Coming Up 17:08 - Đạo đức đằng sau kết quả tìm kiếm trên Google 22:02 - Chúng ta nên sử dụng mạng xã hội như thế nào? 22:51 - Lãnh đạo doanh nghiệp cần chuẩn bị tâm thế như thế nào trong kỷ nguyên số? 25:52 - Điều tốt nhất mà chủ doanh nghiệp có thể làm là cho nhân sự đủ thời gian để trải nghiệm công nghệ 27:08 - Đâu là những mối đe dọa lớn nhất mà chúng ta sẽ phải đối mặt trong năm 2023? 32:39 - Cơ hội kinh doanh trong kỷ nguyên số 37:40 - Coming Up 38:08 - Điều gì sẽ sớm xảy ra trong tương lai? 41:52 - Bài học từ những “ông lớn”  46:16 - Dự đoán điên rồ về tương lai của kỷ nguyên số 48:09 - Điều gì sẽ xảy ra nếu ta không tận dụng công nghệ đúng cách? 49:09 - Trách nhiệm giáo dục cộng đồng về ý thức sử dụng mạng xã hội 51:11 - Tầm nhìn đúng đắn về AI 52:44 - Chào kết    Dẫn chuyện - Host | Quốc Khánh Kịch bản - Scriptwriting | Quốc Khánh, Mai Trang Biên Tập – Editor | Bách Hợp  Truyền thông - Social |  Cẩm Vân  Sản Xuất -  Producer | Anneliese Mai Nguyen  Trợ lý Sản Xuất - Producer Assistant | Ngọc Huân  Quay Phim - Cameraman | Khanh Trần, Thanh Quang, Nhật Trường, Hải Long  Âm Thanh - Sound | Khanh Trần  Hậu Kì – Post Production | Thanh Quang Thiết kế - Design | Nghi Nghi  Makeup Artist - Trang Điểm | Ngọc Nga   #vietsuccess #TQKS #Google #AI #digital #futurist #congnghe #businessmodel

Today we hit on some big news topics! Google invests in former OpenAI employees, ChatGPT is rolling out the paid version and Google is having a very important livestream even on Wednesday! ChatGPT Plus information here: https://openai.com/blog/chatgpt-plus/

We discuss Google Code Red in response to ChatGPT! This is the full take! Is this an overreaction or an appropriate response by Google?

Ryan and Ben discuss Google's big news and how AI could be used in the medical field

Salutare și bine că te-am regăsit la o nouă ediție de Upgrade 100 Podcasts! Are la bază emisiunea Upgrade 100 Like Talks care se întâmplă în fiecare luni la Radio Guerrilla, de la ora 19:00. Această ediție are două părți și e împărțită după cum urmează: 1. Prima parte a fost alocată de Marian Hurducaș - moderator și host - unei retrospective de IQ Digital Summit Brașov pentru să săptămâna trecută echipa Upgrade 100 a pus literalmente în scenă a treia partea cu public am poveștii IQ Digital care a început anul trecut, pe vremea asta, într-un studio TV; pun pariu că ai cam uitat că acum un an încă mai aveam reguli stricte pandemice. Radu Puchiu, colegul din Upgrade 100, moderator Digitalination și expert e-guvernare a fost în studio și alături de Marian a făcut un review al ideilor care merită date mai departe după ce au fost expuse de către speakerii Andreas Ekstrom, jurnalist tech și autor de carte, dau ca referință The Google Code, Iulian Stanciu, președinte executiv eMag, Sergiu Manea, CEO BCR și Achilleas Kanaris, CEO Vodafone România, Matthew Griffin, futurologul care vrea vrea să și repare viitorul nu doar să-l prezică, primarul Brașovului, Allen Coliban, Sabin Sărmaș, președintele comisiei de IT & C din Camera Deputaților și, au mai fost pe scenă Ionuț Țața, antreprenor și consultant în inovare alături de 5 alți antreprenori locali care fac segmentul de business brașovean să se învârtă. 2. A doua parte a fost rezervată noii noastre sărbători naționale: Black Friday! Din primele date pare că românii au fost mult mai cumpătați anul ăsta cu achizițiile față de anii precendenți. Raluca Radu, country manager Answear.ro, s-a alăturat discuției din studio și a explicat cum au arată cifrele din acest an de Black Friday chiar din mijlocul evenimentelor. Upgrade 100 Like Talks care se întâmplă în fiecare luni la Radio Guerrilla, de la ora 19:00.

Cary Duke talks about simple strategies to make your business more visible on Google. Cary's website is adstrategies.co and he can also be reached on Linkedin www.linkedin.com/in/caryduke/ Don't forget to check out: www.allofmyassets.com www.allofmyassets.com/freedomscore www.weeklywealthpodcast.com and email david@parallelfinancial.com with any questions

Watch the live stream: Watch on YouTube About the show Sponsored by: Microsoft for Startups Founders Hub. Special guest: Thomas Gaigher, creator/maintainer pypyr taskrunner Michael #1: March Package Madness via Chris May Start with 16 packages They battle it out 2-on-2 in elimination rounds Voting is once a week So go vote! Brian #2: nbpreview “A terminal viewer for Jupyter notebooks. It's like cat for ipynb files.” Some cool features pretty colors by default piping strips formatting, so you can pass it to grep or other post processing automatic paging syntax highlighting line numbers and wrapping work nicely markdown rendering images converted to block, character, or dots (braille) dataframe rendering clickable links Thomas #3: pyfakefs A fake file system! It intercepts all calls that involve the filesystem in Python - e.g open(), shutil, or pathlib.Path. This is completely transparent - your functional code does not know or need to know that under the hood it's been disconnected from the actual filesystem. The nice thing about this is that you don't have to go patching open using mock_open - which works fine, but gets annoying quickly for more complex test scenarios. E.g Doing a mkdir -p before a file write to ensure parent dirs exist. What it looks like without a fake filesystem: in_bytes = b"""[table] foo = "bar" # String """ # read with patch('pypyr.toml.open', mock_open(read_data=in_bytes)) as mocked_open: payload = toml.read_file('arb/path.in') # write with io.BytesIO() as out_bytes: with patch('pypyr.toml.open', mock_open()) as mock_output: mock_output.return_value.write.side_effect = out_bytes.write toml.write_file('arb/out.toml', payload) out_str = out_bytes.getvalue().decode() mock_output.assert_called_once_with('arb/out.toml', 'wb') assert out_str == """[table] foo = "bar" """ If you've ever tried to patch/mock out pathlib, you'll know the pain! Also, no more annoying test clean-up routines or tempfile - as soon as the fake filesystem goes out of scope, it's gone, no clean-up required. Not a flash in the pan - long history: originally developed by Mike Bland at Google back in 2006. Open sourced in 2011 on Google Code. Moved to Github and nowadays maintained by John McGehee. This has been especially useful for pypyr, because as a task-runner or automation tool pypyr deals with wrangling config files on disk a LOT (reading, generating, editing, token replacing, globs, different encodings), so this makes testing so much easier. Especially to keep on hitting the 100% test coverage bar! Works great with pytest with the provided fs fixture. Just add the fs fixture to a test, and all code under test will use the fake filesystem. Dynamically switch between Linux, MacOs & Windows filesystems. Set up paths/files in your fake filesystem as part of test setup with some neat helper functions. Very responsive maintainers - I had a PR merged in less than half a day. Shoutout to mrbean-bremen. Docs here: http://jmcgeheeiv.github.io/pyfakefs/release/ Github here: https://github.com/jmcgeheeiv/pyfakefs Real world example: @patch('pypyr.config.config.default_encoding', new='utf-16') def test_json_pass_with_encoding(fs): """Relative path to json should succeed with encoding.""" # arrange in_path = './tests/testfiles/test.json' fs.create_file(in_path, contents="""{ "key1": "value1", "key2": "value2", "key3": "value3" } """, encoding='utf-16') # act context = pypyr.parser.jsonfile.get_parsed_context([in_path]) # assert assert context == { "key1": "value1", "key2": "value2", "key3": "value3" } def test_json_parse_not_mapping_at_root(fs): """Not mapping at root level raises.""" # arrange in_path = './tests/testfiles/singleliteral.json' fs.create_file(in_path, contents='123') # act with pytest.raises(TypeError) as err_info: pypyr.parser.jsonfile.get_parsed_context([in_path]) # assert assert str(err_info.value) == ( "json input should describe an object at the top " "level. You should have something liken" "{n"key1":"value1",n"key2":"value2"n}n" "at the json top-level, not an [array] or literal.") Michael #4: strenum A Python Enum that inherits from str. To complement enum.IntEnum in the standard library. Supports python 3.6+. Example usage: class HttpMethod(StrEnum): GET = auto() POST = auto() PUT = auto() DELETE = auto() assert HttpMethod.GET == "GET" Use wherever you can use strings, basically: ## You can use StrEnum values just like strings: import urllib.request req = urllib.request.Request('https://www.python.org/', method=HttpMethod.HEAD) with urllib.request.urlopen(req) as response: html = response.read() Can auto-translate casing with LowercaseStrEnum and UppercaseStrEnum. Brian #5: Code Review Guidelines for Data Science Teams Tim Hopper Great guidelines for any team What is code review for? correctness, familiarity, design feedback, mutual learning, regression protection NOT opportunities for reviewer to impose their idiosyncrasies dev to push correctness responsibility to reviewers demands for perfection Opening a PR informative commit messages consider change in context of project keep them short write a description that helps reviewer include tests with new code Reviewing Wait for CI before starting I would also add “wait at least 10 min or so, requester might be adding comments” Stay positive, constructive, helpful Clarify when a comment is minor or not essential for merging, preface with “nit:” for example If a PR is too large, ask for it to be broken into smaller ones What to look for does it look like it works is new code in the right place unnecessary complexity tests Thomas #6: Shell Power is so over. Leave the turtles in the late 80ies. Partly inspired by/continuation of last week's episode's mention of running subprocesses from Python. Article by Itamar Turner-Trauring Please Stop Writing Shell Scripts https://pythonspeed.com/articles/shell-scripts/ Aims mostly at bash, but I'll happily include bourne, zsh etc. under the same dictum If nothing else, solid listing of common pitfalls/gotchas with bash and their remedies, which is educational enough in and of itself already. TLDR; Error handling in shell is hard, but also surprising if you're not particularly steeped in the ways of the shell. Error resumes next, unset vars don't raise errors, piping & sub shells errs thrown away If you really-eally HAVE to shell, you prob want this boilerplate on top (aka unofficial bash strict mode: #!/bin/bash set -euo pipefail IFS=$'nt' This will, -e: fail immediately on error -u: fail on Unset vars -o pipefail: raise immediately when piping IFS: set Internal Field Separator to newline | tab, rather than space | newline | tab. Prevents surprises when iterating over strings with spaces in them Itamar lists common counter-arguments from shell script die-hards: It's always there! But so is the runtime of whatever you're actually coding in, and in the case of a build CI server. . .almost by definition. Git gud! (I'm paraphrasing) Shell-check (linting for bash, basically) The article is short & sweet - mercifully so in these days of padded content. The rest is going to be me musing out loud, so don't blame the OG author. So expanding on this, I think there're a couple of things going on here: If anything, the author is going a bit soft on your average shell script. If you're just calling a couple of commands in a row, okay, fine. But the moment you start worrying about retrying on failure, parsing some values into or out of some json, conditional branching - which, if you are writing any sort of automation script that interacts with other systems, you WILL be doing - shell scripts are an unproductive malarial nightmare. Much the same point applies to Makefile. It's an amazing tool, but it's also misused for things it was never really meant to do. You end up with Makefiles that call shell scripts that call Makefiles. . . Given that coding involves automating stuff, amazingly often the actual automation of the development process itself is deprioritized & unbudgeted. Sort of like the shoemaker's kid not having shoes. Partly because when management has to choose between shiny new features and automation, shiny new features win every time. Partly because techies will just "quickly" do a thing in shell to solve the immediate problem… Which then becomes part of the firmament like a dead dinosaur that fossilises and more and more inscrutable layers accrete on top of the original "simple" script. Partly because coders would rather get on with clever but marginal micro-optimisations and arguing over important stuff like spaces vs tabs, rather than do the drudge work of automating the development/deployment workflow. There's the glimmering of a point in there somewhere: when you have to choose between shiny new features & more backoffice automation, shiny new features probably win. Your competitiveness in the marketplace might well depend on this. BUT, we shouldn't allow the false idea that shell scripts are "quicker" or "lighter touch" to sneak in there alongside the brutal commercial reality of trade-offs on available budget & time. If you have to automate quickly, it's more sensible to use a task-runner or just your actual programming language. If you're in python already, you're in luck, python's GREAT for this. Don't confuse excellent cli programs like git , curl , awscli, sed or awk with a shell script. These are executables, you don't need the shell to invoke these. Aside from these empirical factors, a couple of psychological factors also. Dealing with hairy shell scripts is almost a Technocratic rite of passage - coupled with imposter syndrome, it's easy to be intimidated by the Shell Bros who're steeped in the arcana of bash. It's the tech equivalent of "back in my day, we didn't even have ", as if this is a justification for things being more difficult than they need to be ever thereafter. This isn't Elden Ring, the extra difficulty doesn't make it more fun. You're trying to get business critical work done, reliably & quickly, so you can get on with those new shiny features that actually pay the bills. Extras Michael: A changing of the guard Firefox → Vivaldi (here's a little more info on the state of Firefox/Mozilla financially) (threat team is particularly troubling) Google email/drive/etc → Zoho @gmail.com to @customdomain.com Google search → DuckDuckGo BTW Calendar apps/integrations and email clients are trouble Joke: A missed opportunity - and cybersecurity

Foundations of Amateur Radio On the 6th of June, 2004, two Brazilian amateurs Roland, PY4ZBZ and Arnaldo, PY4BL made a historic contact on 40m. The distance was not particularly significant, only 70 km, but the mode was. Using 2.1 kHz bandwidth, so it could fit within an amateur radio SSB transmission, they used software created by Swiss amateur Francesco, HB9TLK to make the very first HamDream exchange. This technological advancement represents the birth of what we now call HamDRM and Digital SSTV and how it came about is an adventure that needs documenting, since what we have is written in a combination of Portuguese, German and English, cobbled together from broken websites, archives, source code, commit comments and lost links. To provide some context, there is a broadcast radio mode called DRM, or Digital Radio Mondiale. At this point I should mention that this has absolutely nothing to do with Digital Rights Management with the catchy acronym of, you guessed it, DRM. As you might expect, this acronym clash is unhelpful, to say the least, when you're trying to find information about this radio mode. Digital Radio Mondiale, or DRM, essentially defines a digital standard for radio broadcast transmissions. It can handle multiple audio streams as well as file exchange and is used by broadcasters across the globe. Mondiale, in case you're curious means worldwide in French, seems my high school language lessons have finally been put to good use, my French teacher in the Netherlands will be thrilled. DRM is more efficient than AM and FM and as an open standard, it's gaining popularity. The first broadcast using this mode took place on the 16th of June 2003, during the World Radiocommunication Conference in Geneva. An open source implementation of this mode is called Dream. The source code is available online and is capable of being compiled for Windows, MacOS and Linux. Dream was originally written by Volker Fischer and Alexander Kurpiers. The Dream project started in June of 2001 and today it has many contributors. The DRM standard uses different bandwidths depending on which mode is used. The narrowest DRM mode uses 4.5 kHz, but modes using 100 kHz exist. By comparison, a typical analogue amateur radio uses 2.7 kHz for SSB. Using the source of Dream, Francesco built a modified version, called it HamDream and let it loose on the world. It was used for that very first 70 km contact between Roland and Arnaldo. Several versions of HamDream existed. The first QSO used 2.1 kHz and the last version of HamDream used 2.5 kHz bandwidth. To fit digital audio inside that narrow bandwidth it used different audio compression techniques, called a CODEC, namely LPC10 and SPEEX. According to Francesco, HamDream is the basis for all current amateur radio 2.5 kHz HamDRM programs. He goes on to say that it's outdated and the source and executables were removed from the net. Personally I think that's a shame, since it represents part of the history of our community and I think that putting the source online in a place like GitHub would be beneficial to the hobby. The 2.5 kHz HamDRM mode is implemented in several places. QSSTV, EasyPal and WinDRM to name a few. No doubt it's elsewhere. Of those three, only QSSTV survives. The source code for EasyPal, written by Erik VK4AES, now SK, was lost, apparently when the computer on which it lived was sold by his estate. Ironic really, since EasyPal was written because Erik lost a previous application due to a lightning strike nearby and was forced to write a new application from scratch. WinDRM appears even more elusive. There's a repository on the now archived Google Code site. There are derivatives that appear to use a version of WinDRM, but details are hard to find. An archive I have shows a commit by Francesco, HB9TLK from 2008. I've yet to learn how this relates to the overall picture. In parallel, in 2005, a few enterprising students made a MATLAB implementation of DRM. Called Diorama and written by Andreas Dittrich and Torsten Schorr it forms the basis of a Linux open source HamDRM receiver written by Ties, PA0MBO, chosen because it had a better performance in marginal conditions than Dream did. It's called RXAMADRM. Ties also wrote an open source transmitter, cunningly called TXAMADRM. It was based on the source code of Dream, specifically v1.12b. If at this point your head is exploding, I wouldn't blame you. Let's recap. There's an open broadcast standard called DRM. An open source, cross platform tool called Dream, in active development, implements that standard. A special, now discontinued, version of Dream was created called HamDream. It used less bandwidth than DRM and forms the basis of a standard that we now call HamDRM, which underpins Digital SSTV. HamDream forms the basis of the discontinued products, EasyPal and WinDRM, and lives on in TRXAMADRM and QSSTV, both Linux open source. In amateur radio terms HamDRM is one of the ways we can efficiently exchange digital information across long distances. At this point you might wonder why it matters? For starters, this is part of our history of amateur radio. The HamDRM mode is poorly documented, if at all. It forms the basis of several modes in use today and writing your own software is made all the more challenging because much of the design and development of this mode has been lost. What's more, HamDRM is an example of "modern radio". It uses the same fundamental techniques used by the 4G and 5G mobile phone network, as well as modern Wi-Fi. Losing this is a massive step backwards for amateur radio. This article alone represents a week of research by two people, thank you Randall VK6WR, and I won't be surprised to learn that it contains errors and omissions. It shouldn't have to be this hard to discover how a mode works, what is used to make it tick and how to write new software to implement a new application. Gotta love open source. Speaking of which. If you have source code copies of HamDream or WinDRM, I'd love to hear from you. cq@vk6flab.com is my address. If you have documentation on the design of the HamDRM mode, I'll owe you a beer, or a glass of milk, your choice. I'm Onno VK6FLAB

I tell my experience what I did and what I faced in this competition must watch if you are taking part in it..

Saumya Singh is a Mentor at Google Code in, IIT Kharagpur, and interned at companies like coding blocks, girlscript, etc. She also won the Smart India Hackathon 2019 and has contributed in open source foundations like Girlscript Summer of Code and Red hat. In this episode of BITS Cast, she shares how she learned to code, what challenges she faced, her journey so far as a developer, how she won the Smart India Hackathon, how she contributes to the open source community through Girlscript Summer of Code and Red Hat. She shares tips for how to win hackathons like she did, what mentality should you have when going into a hackathon and more! She talks about how she is passionate about helping underprivileged of India get access to the opportunities that she and all of us are able to get. A Correction here : I said Startup India Hackathon instead of Smart India Hackathon by mistake, sorry for that! ✨ Tags ✨ - bits cast - bitscast - ishan sharma - smart india hackathon,how to teach yourself coding,learn to code,computer science,how to teach yourself programming,how i learned to code,how to learn to code,how to learn to code fast,how to learn programming,google code in,what is google code in,girlscript foundation,girlscript summer of code,how to learn coding,how to learn to program,how to learn programming for beginners,how to learn coding for beginners,how to learn to code for beginners,bitscast - How She Learned to Code & Became Mentor @Google Code In & WON SIH 2019 w/ Saumya Singh | BITS Cast - saumya singh - smart india hackathon 2019 - girlscript summer of code - open source contribution - open source contributor - open source contributor Red hat - iit kharagpur

Google shuttered its source code hosting service Google Code in 2015. Like Facebook, Twitter, and most other major technology companies, Google primarily shifted to a similar service called GitHub to host its own open source projects. Microsoft followed suit and closed its CodePlex service in 2017. It acquired GitHub the next year.

In this podcast we look at innovations in networking security such as TLS1.3 and DNS over HTTPS (DoH). Our Guest is Logan Velvindron; an engineer from Afrinic. Loganaden Velvindron is an open source software developer and IETF participant, as well as the founder and core team member of CyberStorm.mu, a cybersecurity group operating from Mauritius, a small island in the Indian Ocean. Logan and CyberStorm.mu work to improve Linux and open source software through participation in hackathons, including the IETF Hackathons. They also train next-generation Mauritian hackers by organizing boot camps for high school students who have successfully participated in Google Code-in. Useful links: Cyberstorm initiative: https://cyberstorm.mu/ https://ietf.org https://slashdot.org

The Internet Trends Report.  Craig discusses some of the interesting things that you will discover in reading through this report.   What's up with Android users doing updates and patches.  Craig tells you about a study that showed 90% of Android users do not update or patch their devices -- 90%  WOW!! What Browser are you using?  Craig explains why Chrome is probably not your best choice if you are worried about privacy and security he tells you his choice for browsers. Whats the matter with checking your phone everytime it beeps?  Listen in as Craig talks about a study that indicates that interruptions from our smartphone are affecting our brain chemistry. Owning cryptocurrency Can affect your employment. Craig explains why the Federal Government is taking a long look at those who own Cryptocurrencies and have a security clearance for their jobs. Autophagy and intermittent fasting.  Craig discusses a study by Nobel Prize winner Jason Phung and his research and how intermittent fasting has changed Craigs life. Craig is putting up a new membership site (Yes, it is free you just have to sign up)  On it will have all his special reports that he puts out and you will be the first to get them. These and more tech tips, news, and updates visit - CraigPeterson.com --- Transcript: Below is a rush transcript of this segment, it might contain errors. Airing date: 06/09/2018 Don't Use Android, Switch Browsers, and Smartphone Intrruptions Craig Peterson: [00:00:00] Hi everybody, Craig Peterson here, With a fan going on me as it is a little hot today. So, I apologize for some of the background noise and I'm a little clogged up also, just allergic to something. Just this time of year. We're going to be talking today about a couple of things to do with cryptocurrency. We're going to get into addiction and I wanted to get to last week as well as Autophagy thing. This guy Dr. Jason Phung won a Nobel Prize a couple of years ago and I've got to tell you what he found has already changed my life, so I'll tell you about that as far as my health goes. And it was really quite surprising to me. Goodbye Chrome. When you talk about why, we've got at least one guy who is leaving chrome and where he's moving to. Smartphones, they are impacting our brain chemistry. Cannon, Oh my gosh. Remember the Cannon EOS, Well, they stopped making them in 2010 and they just ran out of inventory. So, that's it that's the end of an 80-year history of film cameras for Canon. Wow. And, I want to get to Mary Meeker. She's just amazing. She's got her new internet trends report out. I just printed it up. I printed four pages per sheet. This thing is huge it's hundreds of pages long. Almost 300 or I think little over 300 pages. So, we'll talk about what she's seeing for trends in the Internet and of course a whole lot more stick around. Here we go. [00:01:49] On the front lines and ahead of the trends in business and consumer technology speaking with the top minds and creators behind the products and ideas that help to drive our everyday lives. [00:01:59] Dean Kamen is joining us now. He's the inventor of the Segway and the founder of us first Steve Forbes appreciate what you can do with Forbes magazine for all these years. It's one of my first go to places you can't talk right now with the guys and gals. Siri right now by the director of technology we're joined right now by the CEO of E-bates Kevin Johnson on air for more than 15 years. Over 20 million downloads [00:02:27] This is tech talk with Craig Peterson.  [00:02:32] All right let's get going. Not a whole lot of time. It's hard trying to squeeze this into half an hour, it has been crazy. OK, so everybody should now have their Log-ins for my membership site everyone who asked who is having problems with this whole router update. This whole FBI thing. If you haven't received it let me know. But we were busy this week making sure we gave free account to the listeners who were having troubles who wanted to know more about the routers what models are affected maybe what they should do. We're going to be putting more of that together over the next week. Expect us to come out with something about. OK so now you can reboot is a router for two weeks now. So, what should you replace it with. And by the way you should have rebooted it twice if you do it once per week which is a minimum recommended by the FBI. So, we're putting together something I'm going to try and do a little probably not a Facebook Live, just so many of you guys just aren't listening aren't on Facebook because of frankly good reasons. So, we're probably going to do webinars or we'll do it similar to the last web before we had and kind of go through what your options are what you should do if your business how you can move away from these cheap home routers you don't want to use them now. [00:04:03] It's just amazing to me that people are still doing it. So, if you still have questions about this or anything frankly you can always text me 8 5 5 3 8 5 fifty five fifty three to get a hold of me. Well, let's get into Mary Meeker's report. She comes out with this Internet trend report every year and the market pays major attention to her. Kleiner Perkins is the company that she works for. And they've got a lot of very cool data in this it just came out the end of May in fact May 30th. So, she is looking at the trends overall of course growth is continuing but is continuing to slow. Now I'm looking at the stats here comparing smartphone unit shipments Android, iOS, and other and year to year growth. And basically, we have leveled out here with about one and a half billion smartphones a year. Now think about that if you're a business person or even if you're running the local soccer teams Web site you've got to seriously consider what people are watching what they're looking at. And another statistic that's in here is that now more than 50 percent of the Internet users are using these smartphone devices.  [00:05:23] It's just incredible. So, this year we had 7 percent growth versus 12 percent growth last year and our global Internet users we are now more than 50 per cent saturated. In other words, 50 more than 50 percent of every person worldwide has access to the Internet. Now that's a pretty big number. What that means is from a growth standpoint maintaining growth is going to be difficult, but growth still does remain solid. We've got more innovation more competition frankly, you can find all of this report I got it posted a link to it anyways up on my Web site at CraigPeterson.com, WI-FI adoption online payment. This thing goes on and on. She's done a great job here looking to better experience for consumers and video music. The news feeds it is just amazing. So something you should look at if you are an Internet marketer if you are doing anything Internet frankly so have a look at that. Mary Meeker. OK so let's talk about some of these devices. Let's talk about the Android smart devices because here's some statistics that I thought were probably happening and now it's getting confirmed. Yes indeed. Android devices turned out and this is a great article on cyber scoop by Patrick O'Neill. [00:06:59] Turns out, no one is updating their Android devices, and what have I said about Android for a long time. One is they are more susceptible to hacking than iOS is for quite a number of reasons. The hardware in Android is not as good as the hardware you're going to find in an iPhone. But in addition to that, the biggest problem people have with Android devices is keeping them up to date, most of the manufacturers and remember we're not just talking about the guys that make the phone. We're talking about the companies that are using the phone and are distributing them that are selling them to end users because each one of these carriers is going to have some changes at least to the software in those devices. So, what it's time for a new update when Google comes out with a new version of Android. It might not ever, ever, be available for your Android device. So, when you go back to the standard recommendation of patch early and patch often. You can do it even if you want to. OK. Duel security just came out with the stats here. They released a study about a week ago that found that 90 per cent, nine zero percent of over 10 million Android devices across the U.S. and Western Europe are running outdated versions of Android, 90 percent. And remember New versions of Android aren't just giving you some new features. They aren't just making things cooler, looking nicer. Right. With all those wonderful new little icons and logos and things. No, they are closing security holes, 90 percent of devices not patched up to date is a significant gap. So, you take my advice if you can afford an iPhone you're wrong because if you can afford an android device you can afford an iPhone. [00:09:11] Now you don't have to buy the latest, greatest iPhone right. This iPhone 10 that cost a thousand or more dollars depending on what you get on it. You don't have to get that device. All you have to do is get maybe an iPhone 6S. For instance, there are still for sale 6 s plus maybe. Still for sale and now they're cheap. They're about the same price as an Android phone. Many of the carriers if you up your contract with them they will just go ahead and flat out give you one of these older phones and the iPhone's are easy, peasy, to keep up to date. Apple puts out security patches for the iPhone for years. And years. Unlike many of the Android devices and so, the updates you get an android often they're kind of haphazard, if you even get them at all and attackers are taking advantage of this. We've got new malware brand new malware popping up that preys on old Android software and hardware. OK. So, Apple is dolling out patches to the App Store. There just isn't the same thing for Google Play and that's because there isn't just one Android phone. There are more than 1000 models. Compare that to Apple that only has to deal with a few dozen. And you can begin to understand why Apple can keep their software patched up and Google cannot, remember this isn't really Google's problem. This is really a problem of the carriers and the phone manufacturers not taking the Google updates and being able to get them out to you.  [00:11:00] OK, now Duo also found that computers are often left behind and Wes's operating systems 74 percent of Macs and 85 percent of Chrome OS machines are not running the latest software. And that's a travesty. Now it's not so bad necessarily with Apple because even if you're not running the latest operating system they provide security patches for the last couple of operating systems, OK, so it's not too, too, bad. But when we’re talking about Google's chromos it's a bit of a problem. It's really weird too when you look at the ChromeOS from Google which is on these inexpensive typically inexpensive laptops. These machines auto update on every restart. So, it's really weird but chromos is widely hair hailed frankly as one of the most secure really computing environments out there today. So, some of these stats may not tell the whole story but again if you can make sure you ditch your Android device and ditch it quick and get yourself an iPhone or an iPad. Don't worry about the latest model. You don't need it to stay up to date. You need something recent. If you can afford an iPhone 7 or 8 or 10 go for it. But if all you can afford is that six that are still supported I would I would not get anything older than a 6S which is kind of Apple does this half and half right. They do a six and then come out sometime later with a success then they'll do just the seven then the seven-S OK, so try and get the second half of the six that's S series whether it be the big one or the small one.  [00:12:54] All right so let's talk about Chrome Google Chrome. You know I've been on Google earlier for Android now and again remember it's not so much Google it's the people that are using the Android software that are making the phones that are selling you the phones etcetera. Right. So, we're not going to just completely blame Google for this one.  [00:13:16] So or not I'm not trying to be nasty about it but here is the bottom line. We know Google has been really big over the years on monitoring everything that we have to say right. You know that it's pretty straightforward. I think pretty much everybody knows that. Right. I'm not crazy here. Google's business is keeping an eye on you and your business right. OK so we're on the same page here. If you are using google chrome and heck I use Google Chrome right. A lot of people do because there are great plugins for it works well. It's relatively fast. Well you know I don't. Are you sick of hearing about data privacy, now. But listen here, in the U.S. there's very little you can do about these big businesses keeping tabs on you. The big business is watching where you're going online what you're buying what you're interested in right. So, they can bring up this ad or that ad. This is a real problem. So how much information do you want to give Google. I was just looking today, at my information that Google holds. You can go in you can customize it you can say I don't want to track where I'm going. Where all my searches are, but there's a lot of options and I advise you to do that you should go in. You should customize your security settings. But the bottom line is they are going to record stuff whether you want them to or not. Now if you live in California you have some options, if you live in Europe you have some options, because of the laws that are there.  [00:15:08] The rest of us have to look at this seriously and try and figure out what the right way to go is. We've got Cambridge Analytica the personal data of more than 50 million Americans are in their hand. The Obama campaign the personal information of over 1 billion people in their hands. We've watched companies shut down their European branches because of Europe's data privacy regulations. We've seen companies block Europeans from even gaining access to their Web sites. And when you look at the number of breaches that have happened over the last few years it's just going to make your head spin. So, what can you do. Well we've talked about a couple of things before. Duck Duck Go. That's my default search engine. And you just go to my Web site. CraigPeterson.com you can look it up right there. There's a search function right on there. But Duck Duck Go, doesn't keep any information on you. We have the founder of Epic. On our show here. Couple of years back and that's a browser epic browser dot com and it doesn't keep any information on you. But it is based on the Google Code. But they've gone in and they've removed some of those functions. Google has been there to track you. So, what should be the default browser for you. And it's a question only you can answer. You know I use Chrome for some things I use safari on my Mac for other things use Firefox frequently on my devices as well including on my smartphone.  [00:16:56] I use Firefox, but Chrome has 60 percent of the browser market and Firefox has about 10. Now Firefox has a whole new version of their browser out there now. It is designed to be fast and it's designed to be secure from a. I'm not going to let people steal your information standpoint right. So basically. You want to ditch the browser that supporting a company that uses the data it's gathered about you to sell advertisements right as well as allowing companies to track your movements online. Because just how much privacy do you really think Google is going to give you. Now Firefox's parent company that's Mozilla. It's a nonprofit. They, in fact, I would say they're a little how what's the right word there. They're kind of crazy about some of the security and whether or not they should use this version of open source software open source software or not use it. Right. But they're saying over at Mozilla that the Firefox browser the new one is designed with privacy and convenience. In fact, they say right on the site that Firefox proves that privacy and convenience don't have to be mutually exclusive. And you know I agree, about that with them frankly. So, I agree that you shouldn't be sharing all of this data. I agree you shouldn't be using Chrome, in many cases right. I love having a fast browser and out of the box. Firefox has privacy turned on with Google Chrome you have to go in you have to know what you're doing and you have to configure it.  [00:18:53] So, let's just leave it at that. OK. They've got this do not track tag that's available in Firefox now. Not every site is going to honor that. But they really are trying to get privacy and get it out to you. The end user. OK so let's move on to the next. We don't have much time here. We only have about five minutes left. I want to remind you that if you're still questioning your router and what you should be doing, I am going to be doing a webinar for you. So, you have to keep an eye out if you want to know about that. If you have any questions about your router it particularly if your business and you wonder if there is an alternative that isn't going to break the bank reach out to me I'm putting this stuff together it takes a little while. Hopefully within the next week I'll have that out and available and we'll be able to chat in the online space in a live webinar. Answer your questions. But until then you can just text me 8 5 5 3 8 5 fifty-five fifty-three we'll get you the information we've been for people that qualify that are trying to figure out what to do but haven't been able to will even send you. We'll create and send you your own log-in to my membership site for free so that you can get all of that information. So, we'll do that for you.  [00:20:26] But you got to reach out 8 5 5 3 8 5 55 53.  [00:20:31] Interesting study that came out and it was talking about constant interruptions from alerts and messages on your smartphone. And what's been interesting about this is they've been going further than just how long does it take you to get back into that train of thought. Have you noticed that when you get interrupted by anyone or anything it can take quite a while to get back to the original train of thought. I know with me when on trying to figure out something and I am sitting there working in particular. I'm trying to program or I'm trying to write something I have the stream of consciousness and someone interrupts me. I've lost a minimum of ten minutes sometimes more than half an hour to try and get back into that flow again interrupting me. To me is extremely painful. I just really hate it. So, when I saw this study I thought wow now this is interesting. Very, very, interesting. This is from CBS local affiliates an affiliate down in Philadelphia but they're talking about this whole thing Dr. Scott B. He's a psychologist over at Cleveland Clinic. He says there's this phenomenon they call switch cost that when there's an interruption we switch away from the task that we were at and then we have to come on back. We think it interrupts our efficiency with our brains by 40 percent. He says our nose is always getting off the grindstone. Then we have to reorient. Ourselves. And they're saying that when you do get that interrupt people get little surges of stress hormone, cortisol, which we've heard of before it causes the heart rate to jump.  [00:22:14] Some people get sweaty hands and muscles can get tight. So, bottom line they're advising. Put that phone away. Right. If you're getting the interruptions I have mine on silent-mode most of the time I don't even know it's going off right. I check, I poll every once in a while when I need a little bit of a break. I check and see are there any messages any phone calls I have to return. So, he goes on to say initially when you start trying to stay away from technology or confine it you'll be a little uncomfortable. You'll have that fear of missing out or a little anxiety that something is getting past you. But with practice he says your brain can get used to it. So, break the habit. You don't have to carry that phone around with you all of the time. You don't have to be constantly checking. There are some symptoms to this. If you wake up in the morning the first thing you do is get on your phone. You've got a problem. If the last thing you do at night before you go to sleep is check your phone. You've got a problem. It really interesting article you find up on my Web site. And there have been many other articles that are similar to that.  [00:23:25] You have to disconnect. Read a book even watch a little bit of TV. I promise I talk about Krypto we've only got about a minute left. We had two different things one if you have a security clearance, you might want to listen to this, because at this point they're saying that owning a cryptocurrency could cause you a problem if you're trying to get a security clearance and I can see why. Absolutely see why. And man, I wish we had time to do this. Maybe we should do kind of a whole show on this, but this guy won the Nobel Prize back and I think it was 2016. Dr. Jason Phung and he was talking about Autophagy where cells repair themselves in your body. Know what stops them from repairing themselves. Eating. So, what's interesting is if you know me you know I've been doing intermittent fasting. So, what Basically what he found and won a Nobel Prize for is if you do intermittent fasting you will be healthier. Really interesting article you'll find it at Craig Peterson dot com. There's a ton of information I've read five books on this so far just fascinating and personally I can say it works. Have any questions. Text me 8 5 5 3 8 5 55 53. Make sure we answer you and visit me online as well. Craig Peterson dot com have a great weekend. We'll be talking again soon. Bye-Bye. --- Related articles: That Russian malware that infected over 500,000 devices is even worse than we thought US: Crypto Could Pose a Problem for Candidates Seeking Security Clearances The FBI calls Chinese spies in the US a ‘whole of society threat’ — here’s how to protect yourself HIPAA Security Rule Requires Physical Security of Equipment IBM bans the use of removable storage by employees 5G Wireless Service Is Coming, And So Are Health Concerns Over The Towers That Support It No one is updating their Android devices, new data shows Bye, Chrome: Why I’m switching to Firefox and you should too Constant Interruptions From Smartphone Can Impact Brain Chemistry, Scientists Say Canon shutters 80-year history of film cameras How to renew your body: Fasting and autophagy   Here’s Mary Meeker’s essential 2018 Internet Trends report More stories and tech updates at: www.craigpeterson.com Don't miss an episode from Craig. Subscribe and give us a rating: www.craigpeterson.com/itunes Message Input: Message #techtalk Follow me on Twitter for the latest in tech at: www.twitter.com/craigpeterson For questions, call or text: 855-385-5553

Google SVP Philipp Schindler talks with Recode's Kara Swisher about YouTube's original programming initiative and how the company compares it to Netflix's and Amazon's. Schindler says the key differentiator is YouTube's existing fanbase, which spends more than 50 percent of its time watching video on mobile devices. He also discusses some "megatrends" in technology, including machine learning and new types of devices like wearables, which he says are coming together into an "age of smart assistants." Schindler argues that virtual reality and augmented reality are incredibly important technologies for the future of video and that Google's role is to democratize access to VR and AR. Learn more about your ad choices. Visit podcastchoices.com/adchoices

Google CEO Sundar Pichai talks with The Verge's Walt Mossberg about why Google thinks it can beat Apple, Amazon and Microsoft to make artificial intelligence easier and more helpful for every consumer. He says Google wants to offer smarter privacy controls, so that users might save certain types of conversations forever and wipe others off the record. Plus: Pichai adds that the company is investing more into its flagship Nexus devices for the Android operating system, but will not make its own smartphone without an OEM partner. Learn more about your ad choices. Visit podcastchoices.com/adchoices

In this episode we discuss Apple's battery replacement policy, printing latte art, automatic bug repairs, dependent page layouts, AppMesh's SalesMesh tool, Benioff's thoughts on regulators, issues with deploying list views, whether Slack would be a good acquisition for Salesforce, and promote the idea for a Dreamforce Cash Cab. Bidding farewell to Google CodeApple will replace your battery once it hits 80 percent healthAutomatic bug repairDependent page layouts (IdeaExchange)SalesMesh 3.0 now allows sales reps to team up outside of SalesforceMarc Benioff: 'This is no new tech bubble'Salesforce1 Platform Lightning Process Builder Feature DemoIdea of the Week: Dreamforce Cash Cab!

This week Dave and Gunnar talk about First round of Thunderdome, product design success and failure, RHEL 7.1, urban dashboards, and the Cumulative Threat. Gunnar is horrified by Google’s audio history on him. Are you? Dave sticks his keyboard in dishwasher Fighting Unicorns are going to the FRC World Championship! Security Thunderdome results!  Vote for round two now! Raspberry Pi 2 is out and it will run Windows 10? Susceptible to intense flashes of light Almost related: Dave files a Raspbian bug Jet Blue and Virgin America are Offering In-Flight College Classes HotelsByDay Lets Travelers Book Daytime Hotel Rooms For Less Than Overnight Stays D&G This Week in Soylent Packaging: KFC Bringing Edible Coffee Cups To UK HT Uzoma Nwosu: SQRL Uber pledges to enlist 1 million female drivers by 2020 D&G Movie Plot Kit of the Week: Scientists store data inside DNA that could last MILLIONS of years Washington lawmakers want computer science to count as foreign language New “Happiness Monitor” Continuously Measures Your Mood, Reports It to Your Boss See a pic of the monitoring device here! Different kind of happiness monitor: STD Dongle D&G This Week in Vendor Abandonment: Google to close Google Code open source project hosting RHEL 7.1 is out! RHEL for Real Time RHEL Atomic MLS containers? D&G Mailbag letter from Šimon Lukašík: Check out OpenSCAP Compliance Center! Roadmap and project definition presentation Demo video by Šimon Signal 2.0 is out! History of the Urban Dashboard The cumulative cyber threat. DNI is all about it. Cutting Room Floor FIRST web page viewed by “FIRST” browser via c.1965 modem and terminal See esp the bookmark usage at 9:21 Domino Etch-a-Sketch makes Gunnar nervous BATTLESHOTS. It’s like Battleship, but with liquor Brides Throwing Cats NUKEMAP We Give Thanks Uzoma Nwosu for the SQRL pointer! Šimon Lukašík for the Mailbag letter and for all your great SCAP work!

Taichi Nakashima さんと、AWS破産, DigitalOcean, CoreOS, RSSリーダー、村上春樹などについて話しました。 Show Notes "Amazon から電話がかかってきて個人の AWS が不正利用されてたとかですごい額の請求が来てた。" Developers, Check Your Amazon Bills For Bitcoin Miners - ReadWrite Best Practices for Managing AWS Access Keys - Amazon Web Services Multi-Factor Authentication DigitalOcean (Referral) Linode (Referral) Automated Builds - Docker Documentation mirakui/retrobot Updates & Patches - CoreOS Monitor Infrastructure Performance - Datadog Docker Performance | Datadog google/cadvisor Google Open Source Blog: Bidding farewell to Google Code How GitHub Conquered Google, Microsoft, and Everyone Else | WIRED はてなブックマークは「RSSリーダー」の開発に取り組んでいきます 村上さんのところ／村上春樹 期間限定公式サイト 書斎より　机の上の光景 - 村上さんのところ 食卓日記をお願いします - 村上さんのところ Another Case against Smart Speed / Silent Removal

Unsupported Operation 84 Misc Not really “new”, but I rediscovered the fact that since Git 1.8.2, that submodules now support following a branch rather than a fixed commit SHA1 - this actually makes them somewhat usable.JDK8 Build 91 available - Sadly, this didn't fix my method handle issue. Atlassian JIRA 6 was released - teases with Bamboo 5 updates Yourkit Profiler 2013 EAP launched, personal licences only US$99 until June 4, 2013.Spring 4 announced, indicates support for JSE8 and Groovy 2 as the first class language, pushing Groovy 2 bigtime.Action Launcher Pro 1.7 for Android was released - best launcher ever. Adds support for icon packs and just makes it that bit more... awesome.Big changes for Redline Smalltalk - now scans classpath for .st files, so works nicely with artifacts/jar files etc. etc.Google Code removes file downloads Maven - Spotlight Plugin of the Week maven-shade-plugin Apache Apache Maven 3.1-alpha-1 available for testing/voting. Release Notes.Maven ShadePlugin, version 2,1 supporting the above 3.1 releaseOpen Web Beans 1.2Apache Ant 1.9.1Apache Wicket 6.8Commons-Logging 1.1.3 (please still remove it from your archives)Subversion 1.8-rc2JSPWiki incubating 2.9.1 Clojure MD did a short clojure-maven-plugin history presentation at the 2nd Auckland Clojure Meetup, this seems to have awaked the bug reporters...Released 1.3.16 and then followed up with 1.3.17 of the clojure-maven-plugin Scala Scala 2.10.2-RC1 now availabledispatch 0.10.1 released, HTTP client libraryScala on Android - new book from Lean Pub, being written by Geoffroy Couprie (@gcouprie) Groovy Groovy 2.1 showcased and goes type checking madGroovy 2.1 type checking extensions for SQL inside a string discussedCedric shows Groovy type checking printf type and number of params Docs for type checking extensions released by CedricGaelyk 2.0 released

In this episode, we talk to Martin Geisler, a long time contributor to the Mercurial project. If you cannot see the audio controls, your browser does not support the audio element. Use the link below to download the mp3 manually. Link to mp3Martin is a software developer since 15 years, focusing mainly on Python. I met him at a conference some years back where I talked about Git-SVN, and he talked about Mercurial, and we got to have some really interesting discussions on Git vs Mercurial, some of which we were able to recreate for recording this episode.Links and resources from the show:Martin's homepage (redirects to his Google+ account at the time of writing)The two frameworks Martin mentioned for Python development:Pyramid SQL Alchemy Mercurial Steve Losh's Git Koans Steve Losh explaining the diff between Mercurial and GitCodePlex announced Mercurial support Bitbucket announced Git support Google Code announces Git support Announcing Kiln Harmony Facebook's discussion on the Git mailing list Mercurial/Git integration with HgGit JavaHG Mercurial's Command Server Mercurial Phases Mercurial Changeset Evolution Some other useful things we didn't talk about:Hints for would-be Mercurial power users Revision sets and file sets (built-in query languages that let you select revisions and files)Mercurial for Git usersFinally, new users might find a minimal ~/.hgrc file with my favorite extensions useful:[ui]username = Your Name [extensions]# Color output and show progress bars in your terminalcolor =progress =# Pipe output into a pagerpager =# Enable 'hg rebase' and 'hg pull --rebase'rebase =# Enable 'hg histedit', like 'git rebase -i'histedit =# Enable 'hg record', like 'git add -i; git commit'record =[pager]# Set $PAGER or specify the pager to use here: pager = less -FRX Listen to the episode on YouTube

Enregistre le 4 aout 2011 News Java 7 Le bug des compilations de loop dans HotSpot http://www.lucidimagination.com/blog/2011/07/28/dont-use-java-7-for-anything/ http://www.infoq.com/news/2011/08/java7-hotspot Kotlin Site web Kotlin http://confluence.jetbrains.net/display/Kotlin/Kotlin Stephen Colebourne http://www.jroller.com/scolebourne/entry/reversed_type_declarations et http://www.jroller.com/scolebourne/entry/kotlin_and_the_search_for Les motivations derriere Kotlin http://blog.jetbrains.com/kotlin/2011/08/why-jetbrains-needs-kotlin/ Cast-IT Cast-IT http://www.cast-it.fr Mix-IT http://www.mix-it.fr/ Devoxx Les oeufs de Paques de Devoxx http://www.devoxx.com/display/DV11/Home Google Le blog d’un ancien de Google http://rethrick.com/#waving-goodbye Le BileBlog http://www.bileblog.org Google+ http://plus.google.com Google Code et Git http://www.blog-nouvelles-technologies.fr/archives/5344/google-code-annonce-son-support-a-git/ JBoss AS 7 http://www.jboss.org/as7.html Nabaztag est mort, vive Nabaztag ! Arrêt des serveurs suite à la mise en liquidation judiciaire de Mindscape qui ne pouvait plus payer son prestataire http://blog.karotz.com/?p=5224 http://blog.karotz.com/?p=5284 Le lapin reprendra t’il vie avec la communauté ? http://nabaztag.forumactif.fr Les mains dans le cambouis Sites “statiques” Awestruct http://awestruct.org Jekyll https://github.com/mojombo/jekyll/wiki Sass http://sass-lang.com/ Markdown http://daringfireball.net/projects/markdown/ W3Schools http://www.w3schools.com/ Les protocoles de serialization Google Protocol Buffer http://code.google.com/p/protobuf/ Apache Avro http://avro.apache.org/ MessagePack http://msgpack.org/ JSON http://fr.wikipedia.org/wiki/JavaScript_Object_Notation BSON http://bsonspec.org/ Apache Thrift http://thrift.apache.org/ JBoss Marshalling http://www.jboss.org/jbossmarshalling Comparaison http://www.igvita.com/2011/08/01/protocol-buffers-avro-thrift-messagepack/ Outils de l’épisode BalsamiQ http://balsamiq.com/ Gliffy http://www.gliffy.com/ Dia http://projects.gnome.org/dia/ OmniGraffle http://www.omnigroup.com/products/omnigraffle/ Conferences JUG Summer camp le 16 septembre à la Rochelle http://sites.google.com/site/jugsummercamp/ OpenWorldForum 22 et 23 septembre à Paris http://www.openworldforum.org/ JavaOne 2011 du 2 au 6 octobre à San Francisco http://www.oracle.com/javaone/index.html Riviera Dev les 20 et 21 octobre à Sophia Antipolis http://rivieradev.fr/ Devoxx 14 au 18 novembre à Anvers http://www.devoxx.com/display/DV11/Home Nous contacter Contactez-nous via twitter http://twitter.com/lescastcodeurs sur le groupe Google http://groups.google.com/group/lescastcodeurs ou sur le site web http://lescastcodeurs.com/ Flattr-ez nous (dons) sur http://lescastcodeurs.com/

Uutiset: - Ubuntu 10.10 - Ubuntu 11.04 - Fedora 14 - Diaspora - Firefox 4 - OpenOffice.org forkkaantui LibreOfficeksi - Ubuntu Suomella uusi yhteyshenkilö - Google Code-in alkaa taas - DirectX 11 Linuxille, mutta ei WXP:lle - Mandriva Linux forkkaantui Mageia Linuxiksi - Broadcom julkaisee ajurisorsat Panelistit: - Henrik - Ninnnu - Tero

Epizoda 15. „Ruby, pro filosofy to nejlepší” [47 min] Hostem eklektický programátor v Ruby, designér uživatelských rozhraní, školitel Gitu a studovaný filosof Karel Minařík (aka Karmi) a povídali jsme si s ním nejen o Ruby. Karmiho profil a rozcestník Protovis – A graphical toolkit for visualization MongoDB, CouchDB, Redis Karmiho slajdy CouchDB - A Database for the Web Přednáška Spoiling The Youth With Ruby na Euruko 2010 a tady jsou slajdy Autor hudby je Discofield. Stáhnout v MP3 [47 min]

This podcast produced with WYHIWYG (what you hear is what you get).Welcome to Show #119!  This episode's topic: Retro Roundup! The 8-bit TV Computer - 6502 based, Famicom/NES compatible, programmable, on the Maker Shed site...Playpower is promoting the use of the 8-bit TV Computer as an educational game development system!  After having a look at their site, check out this Wired article on what Playpower is up to...Have a look at the Rare and Old Computers blog, where you can see information on production numbers and current sales of rare and old computers!Ancient UNIX?  You bet...how about...First Edition?  Download it at the unix-jun72 Google Code project site, then run it on the awesome SIMH simulation system...If you're a Commodore fan, check out Commodore Free - the freely downloadable magazine!The Woz can help jump-start the computing industry, but...can he dance?  Find out at his website page covering the "Dancing With The Stars" event, and at Woz TV on YouTube! Be sure to send any comments, questions or feedback to retrobits@gmail.com. For online discussions on Retrobits Podcast topics, check out the Retrobits Podcast forum on the PETSCII Forums page! Our Theme Song is "Sweet" from the "Re-Think" album by Galigan. Thanks for listening! - Earl This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 2.5 License. 

Discuss this episode in the Muse community Follow @MuseAppHQ on Twitter Show notes 00:00:00 - Speaker 1: People are drawn to you for your specific skill set that only you can fill. There’s a U-shaped hole in the universe and you’ve created that gravitational pull that people find you. And I think as far as careers go, the more unique you are, the more unsubstitutable you are, the better compensated you will be and the more you enjoy your job, to be honest. 00:00:23 - Speaker 2: Hello and welcome to Meta Muse. Muse is a tool for thought on iPad and Mac. This podcast isn’t about Muse the product, it’s about Muse the company and the small team behind it. I’m Adam Wiggins here with my colleague Mark McGranaghan. 00:00:37 - Speaker 1: Hey Adam. 00:00:38 - Speaker 2: And joined today by Sean Wang, who goes by Swxs. 00:00:41 - Speaker 1: Hey, happy to be here. 00:00:43 - Speaker 2: And Sean, I understand you’re a former competitive tennis player. Tell me about that. 00:00:49 - Speaker 1: It was kind of my high school thing. When I was growing up, my mom trained me on table tennis back home, which is recreationally. 00:00:57 - Speaker 2: Maybe she sensed that you might someday have a career in startups and knew that this would be a critical break room activity. 00:01:04 - Speaker 1: Yeah, actually, actually it does really help in the old days when we had offices, remember those days. Now we had just had like Wii tennis or VR tennis. No, then, you know, when it came to high school, I upgraded to tennis. I was on my tennis school team, high school team, and then when I served in the military, because every Singaporean has to serve 2 years in the army, I represented my battalion at our tennis championships and we actually won, which is fun. Although I was kind of the bench person, so I didn’t actually play, but I was on the team. So I guess to say we won. 00:01:40 - Speaker 2: And you’re the author of a book on career, you run a community that’s going to tie into our topic today, but I’d love to hear about your full background and in particular the work you do on developer experience with Temporal. 00:01:54 - Speaker 1: Sure, I basically got the bit by the finance bug in college because I saw the Asian financial crisis and then the tech slump and I realized that a lot of people in finance seem to be like masters of the universe. They seem to always know what’s going on. And also they seem to be, at least in the hedge fund world, capable of being independent of the economic cycle. In other words, if you see a recession coming, you can actually position yourself to profit from it. Rather than just be tied to the general cycles of the economy. So I set myself a goal of working at a hedge fund, went to college for that. And then finally, after a long sequence of events, arrived at a hedge fund, and then realized I didn’t like it. I didn’t like the people I worked with and for, and I was OK. I was sort of middling in my analyst rankings, but I wasn’t going to be great. And while I was doing my finance stuff, I learned to code and basically every junior finance person that comes up through the ranks these days becomes a self-taught programmer because you have to. 00:02:53 - Speaker 2: Is that sort of like an Excel kind of automation thing or is there something further than that? 00:03:00 - Speaker 1: Do you get into data science, starts with Excel and then VBA Python. And then for me, because I did option pricing, Haskell, because that was the company I worked at Standard Chartered where there was the house language and I just didn’t have a choice. It was only after I left Standard Charter that I had any idea that Haskell was this sort of revered language of functional programmers. Yeah, and so I decided to kind of go in on that. I also read the writing on the wall in terms of public market investing versus private markets. Like it seemed like companies were staying private for longer and more wealth was being created in the private markets, as opposed to the chumps like me in hedge funds trying to trade public stock, where there was comparatively less growth, obviously not no growth, but less growth. So I did a transition at age 30 from finance to tech, and that was a pretty scary one because just starting over at 0 from, you know, my previous career, I sort of strived for 10+ years to get there, to get where I got and then having to start over and not know anything. It was pretty scary. 00:03:59 - Speaker 2: It also sounds like something that maybe in a way takes more courage because it’s not that you didn’t have a career, you actually did have one. You worked hard, you found yourself that place, it’s probably something that Definitely pay the bills and then some I would imagine. So you know it’s one thing when you’re forced out of a career due to changing economic circumstances or age or some other thing and then you have to restart. That’s pretty hard to do, but maybe the decision has sort of been made for you by circumstance. But here you made a much more active choice to say like I don’t think this is where the future is. 00:04:33 - Speaker 1: For me, yeah, it was a very personal choice. Obviously, I think the people that do extremely well still in finance and I keep in touch with some of them. But I am pretty open about what I left on the table. So my first year as a hedge fund analyst, I made 350K and there was a path from that to seven digits, you know, which I would probably be there by now if I had stayed in finance. But I think actually having had a prior career, I think actually reduces that risk, at least because I had a standing offer to go back to my previous bank if I wanted to. So I knew that like, all right, I could give myself a couple of years or so, try this transition out. If it didn’t work out, I could just go back to my old job, which I loved, and I had a lot of fun with. At least just to pay as well as the hedge fund. But yeah, I think it wasn’t that risky. Plus, it actually helps me get a job when I came out the other side of the transition because I did a boot camp in New York, the Full stack Academy, and the first employer that I sat down with was Two Sigma, which is a well known quantitative hedge fund in New York. And they liked my story. They liked that I was a former trader and then I now knew how to code. So they hired me based on that and then continued on to completely disregard my finance side and just only use the tech stuff. But it’s a story you can tell in career change. So the way I talk about it is that you take your used experience and you know you sort of trade it in for $1 credit at the store. And it’s kind of like GameStop in the sense that they kind of rip you off in terms of how much credit they give you, but you get to at least tell a story to get your foot in the door in a more compelling way than a lot of other people who don’t have as much of a good story to tell. You know, I had people who were with me in that boot camp that were former chefs. So that guy actually got a job at Blue Apron. Wasn’t that great, you know, didn’t turn out that well, but like It helps. I think for a lot of career transitioners, that’s kind of the advice I try to give them, like, try to make use of your unfair advantages because the cards will be stacked against you. You’re up against people who have coded since they were like 12 and have CS degrees and stuff. You got to find your way to make it in this industry. And once you get that first job, everything else is relevant, you know. So that’s kind of what I say for that. So I spent some time at Two Sigma and then started really getting active in the New York tech scene, which is a huge part of my story. I attended and spoke at every single meetup in New York and I blogged about JavaScript and React, and that got me notice. So if I reached out and I joined them for a really good 2 years, where I started to build my sort of public profile as a developer advocate and also an engineer on their CLI and the surless node ecosystem there. That led into a job at AWS where I did kind of the same thing, but bigger because AWS Amplify is kind of like their NetLify cologne with more services attached to it. So with DiMODB and with graphfuo, with location services and mobile testing services, a bunch of really good stuff. And then I wrote a blog post about what I thought was missing in the service ecosystem and that eventually led to my job at Temporo because I concluded that Servius was really good at short-lived compute that scales to zero and scales to infinity, but it’s terrible at long running jobs. It’s terrible at asynchronous tasks and the solutions that were available today, namely AW that functions and you know other equivalents out there, weren’t really good. Like they presented too much friction for me to effectively express the kind of business logic that I saw out there that was actually worth so much money. So yeah, just essentially blogging got me the job I have today, which is pretty cool and also helped me transition from a front end career to serveless to a backend focus career now, and it’s been a wild ride. 00:08:17 - Speaker 2: You know, what you described there, the building a public presence and certainly the learning something and then turning around and sharing that is something that we’ve touched on. Actually, I realized we’re kind of inadvertently doing a small miniseries here. We did an episode on building in Public. Our last one here was on sort of personal brand. And so I’m going to go ahead and say that this is 3 of 3 in a series where the career topic helps bring it all together, but yeah, sort of learn something and write about it or share it in that moment when you kind of can see both that you remember what it’s like to not know the thing, but now you know the thing and you can, you know, pass that kind of mental diff on to others is pretty powerful and seems like you got the sort of maximum leverage out of doing exactly that. 00:09:04 - Speaker 1: So I’m known for this essay that I wrote on learning in public, and that’s actually a piece that I wrote as an advice for my fellow boot camp grads when I was asked to go back and give a speech. And it was pretty funny because I think it’s a reflection on the diff between my finance and my tech career. So in finance, everything is zero sum. If you get a trade idea, you should try not to leak it before you’ve established a position and once you’ve established a position, sure, go ahead and pop your bags. But in tech, we share our code. We get up on stage and we share our failures and outage stories. It’s just so fundamentally open because it’s such a blue ocean field. It’s still expanding so much that we don’t actually care that we’re giving up some of our trade secrets because the hope is that other people who receive that benefit will reciprocate in some way or form. But I found that just much more fitting to my natural inclination. But also, I think I found that my career grew much better in a healthier way, in a sense that I wasn’t trying to get one up on my peers. I was working with them and sharing what I know or did not know helped them to teach me or correct me or whatever. And that improved me at my pace of learning. So I always call it Not an act of altruism, you’re not giving back to the community so much as like this is actually, even if you’re totally self-interested, this is legitimately the fastest way to learn, which is to learn in public. 00:10:24 - Speaker 2: And tell me about Timoral. 00:10:26 - Speaker 1: Temporo is an open source workflow engine and I try to categorize this piece of software in relation to other engines, which are effectively custom purpose databases. So if you think about a search engine, you could do full tech search on a database just by yourself, but you probably wouldn’t because search is such a well defined custom problem in the way. That you should probably adopt some custom solution like Elastic Search or Type sensor, whatever else is cool these days on it. And similarly, like an analytics engine, yeah, it’s a form of database, but it’s a very focused database for analytics workloads which are high input and sort of a lot of aggregate reads. And so similarly, I think workflow engines are an underexplored area of custom database that have until now been typically mostly hand rolled. But I think people are finding that there’s just so many opportunities to use these workflows, which is what we call them in a variety of situations. And so just to explain a little bit more about what that means, a workflow is kind of a long running durable function. Imagine if to write a monthly billing subscription, all you had to do was have an infinite loop, charge your credit card and then sleep until the next month, and that’s it. So you don’t have to set a separate cron job, like the cron job is effectively automatically provisioned when you call that API for sleeping to the next period. 00:11:53 - Speaker 2: So Sean, when we were speaking before you mentioned some use cases that kind of made it concrete for me, you know, on the consumer side, you have something like anything delivery oriented or rideshare ordering something from the moment you say, OK, bring this vehicle or package or whatever it is to me, or even something like check out like e-commerce, you know, when you hit that, OK, buy this thing button on Amazon or wherever else you have essentially opened a very long running real world transaction. And it may last days until that package comes to you or even longer if it gets lost or something like that. And so during this whole time, there is a sense that that’s an open activity, but it’s not open in the sense that I have the app open on my phone or that it’s open on my computer. It’s the sense that it’s sort of running and the system needs to keep trying to converge that again. Some completion where the completion is the delivered order or the car shows up or the things imported somehow, and then at that point, you know, then the transaction is completed more and more, I think as we have more and more of these kinds of services on the consumer side at least, maybe we see more and more of these long running asynchronous kind of user interfaces you might call them. 00:13:00 - Speaker 1: Yeah, I think so too. Our CEO was actually at Amazon when they implemented the one click buy button, which is essentially, if you think about it, turning the purchase process from a synchronous process of right, add to shopping cart and then go to shopping cart and then enter your details for checkout to, all right, click this and then register that there’s a purchase intent and let people cancel if they change their minds within the next 30 seconds, if they made a mistake or if they just changed their minds. And after that 32nd timer, can continue to proceed with that order, but you’ve just reduced the number of clicks and you know shopping cart abandonment rates are like 60, 70%. So it’s just better user experience, at least on the surface, obviously, there are other issues with one click check out, which is a ital spies. But that happens to be in the favor of Amazon. But that’s my pitch for a lot of non-technical sort of UX type people. I think there are a lot of user experiences that can be improved by turning sync to async. Another example that I often like to bring up is this script, which is actually a customer of ours. And so this script is an audio editing tool, which takes transcriptions of your audio podcasts and turns it into sort of like an editable Google Doc, where they sync up your audio clips with the words that are on the transcripts and you can just delete words or add words like you would a standard Google Doc. All of that is powered by tempora in the back end because it starts Farm out work that might potentially be long running. The script surprisingly, if you’ve ever tried to throw in like a 3 hour podcast into the script, it actually takes pretty much the same amount of time because they chop up that audio and farm it out to a dozen little API servers. I don’t think I can say what they use, but they do that transcription in parallel and they do a lot of reliability checking behind the scenes to make sure that they got that accurate. I think people take for granted the reliability of these things. But like it’s so common for a custom engineered code to forget some use cases to have some race conditions where you would have some order go through, your system might go down or some things might happen out of sequence because you know computers. And you would lose an order. It would just disappear, vanish, and you would have no idea where it went. And this happened to the scripts, actually, we’re able to quote them because they said this in our case study. And I was just so happy to hear that because I was like, Oh, I’m not the only one. It’s not that I’m a bad engineer, like this is just the way things are, and you need a well organized and architecture system to take that problem away from you because I’m trying to build my app. I’m not trying to solve this weird distributed systems problem. So I’m very grateful that I found this, they found me actually, because of my blog posts, which is another bringing back to the career topic. I joined this company as employee 17 before we made our 1st $1 in revenue, and now we’re a unicorn company and Unicorn here being the startup slang for a private market valuation of at least $1 billion. 00:15:47 - Speaker 1: Yes, sir. I forget that sometimes I have to explain this. To some audiences, but this is not the kind of job that you would go on a job board and go like, right, out of these like 5 very competitive offers, like I would just pick one of them. The job doesn’t exist until you talk to them and you create the job yourself. I named my own job and created my own job because I thought that that’s where I would be most valuable to the company. I think a lot of jobs are like that in the sense that There’s like the 20% of jobs that are listed and then there’s like the 80% of jobs that are like, you know, I just hired my friend who knows this stuff really well. So perhaps that is a good segue into the career topic. I don’t know quite so. 00:16:27 - Speaker 1: Like it’s so fresh to me that I’m still reeling from how this happened because it’s been the best career move I ever made. 00:16:35 - Speaker 2: Yeah, well, we’d love to expand on that story a little bit, but yeah, maybe now is the right time to introduce the topic, which clearly we’ve hinted at, so that’s career. And before we get into a lot of specifics here again, you’ve written this book titled The Coding Career Handbook, and it is focused, I think, on the engineering or developer side, but obviously I think a lot of this is generalizable or we can talk today about something that certainly applies to probably everyone that’s in a design or product or general tech world product development job. But as always, I like to start with a little definition. I’d love to hear what the word career means to both of you. 00:17:14 - Speaker 3: You know, Adam, I should know better by now that whenever we’re doing a podcast on a noun, I should think of my good definition ahead of time. Yeah, I don’t know. I might call a career that course and consequences of your professional endeavors, and the reason I like that is it because it talks about both what you end up doing and the implications that it has for you personally. And to me it also implies something that’s not super linear. Sometimes people think about career and it’s like, OK, I decide 18 and I’m gonna do this and I do it for 40 years, and this is the latter and boom boom boom, and I think the reality of careers is much more diffuse and nonlinear and probilistic now. We can talk about how that is, but that’s how I think about it. 00:17:50 - Speaker 1: And definitely echo the fact that it is nonlinear. I have a more cynical take, which is like the career is the story that you retroactively tell after you do the things that you’ve done and you’re trying to spin a narrative that’s what you intended all along. But I think it’s very much in the vein of Steve Jobs’s Stanford commencement speech when he says like, you can only connect the dots looking backwards and that’s definitely how I have experienced life so far. I definitely think that there are other more air quotes, career oriented people who plan everything out. They have their 20 year roadmap for their lives. Some of them achieve that and many don’t, but their take is valid too. I just don’t particularly subscribe to that. I think in this day and age, the careers are a lot more mobile and random than they may have been in our previous generations. 00:18:40 - Speaker 2: Yeah, for me, I think that word early in my life, I had a negative association with that word that it makes you think of maybe corporate ladder climbers and you know, you sort of like trying to kiss up to the boss in order to like get that next slot, you know, make more money, get the corner office, have a more impressive title, and a lot of it turns into just kind of status ladder games and that sort of thing. And so I felt kind of repelled from even thinking about actively the path of my career. But later on, I think I came to feel, OK, well, that is like a negative version of that. And maybe there’s also this way you described there, Shawna, this is the planned out thing, which is just some fields either demand that because they just require a lot of education being a surgeon, for example, it’s just you kind of have to have that plan and really pursue it. It’s not something you can kind of just dabble in and find. if it suits you. And so I think those of us that like a little bit more of an exploratory path, you know, the tech world where it is much more like an opportunistic and ever changing world, and you just try to adapt and find your place in it. Maybe that suits us all. Yeah, I think for me now, and of course we can also talk about the difference between, you know, being kind of an entrepreneur or founder type versus going to work at companies that already exist, but I do think they share the commonality that It’s a way to think about as a first class concern. We spend typically a third of our lives at work. How am I gonna make sure to spend that time well? And I think again, coming to those of us who are in tech, we’re lucky enough, I mean, I think for a lot of people, a job is really about putting food on the table. It’s filling a very basic need, it’s that almost the lowest rung there on the Maslow’s hierarchy of needs. We’re lucky enough, we’re very employable in a growth industry, and so we have the option to think more in terms of like, oh, I can get several job offers from several good companies and sure I can compare how much money I earn from them, but I can also think move up that hierarchy of needs and think in terms of like what’s the meaning that I want, how do I want to live my life, how do I want to spend my work day, and what’s the impact I want to have with that work and that’s a great privilege to be able to do that. But then I think it’s worthwhile to be a little thoughtful about how you spend that in order to make sure that that retroactive story is the best one it can be. 00:21:00 - Speaker 1: Yeah. I think there’s a lot of fit with personality types as well. So there will be some personality types that crave structure. Tell me what to do and I’ll go do it. Whereas others, they refuse to be told what to do. They need to find it out for themselves. And so the career path for these two different types would be very different. So I think you have to figure out what you are and no shame in either approach really. I will say that career ladders are imposed by companies partially to give you a path to career development, to give you some kind of fair rubric on like, all right, you’ve reached these requirements, you obviously deserve the next level and the next bump in compensation. But then the, I like to call these barbarians, the people who don’t believe in structure, would say, All right, you’re constraining my growth. I could go out there and strike out on my own. And do actual things that matter in business. And if I deserve that in the marketplace, then I’ll get my reward, not some fake artificial internal metric that you made up. So I have empathy with both because ultimately, even if as an entrepreneur, if you’re someone who starts entrepreneuring because you don’t like traditional corporate structures and climbing those ladders, if you hire people, you’re going to have to establish career ladders for them because they want to know how they could grow with you and your company. So can’t really run from it. 00:22:18 - Speaker 2: Yeah, that’s absolutely true. Different people need different amounts of structure and maybe like a rule zero thing here and successfully pursuing your career is self-know. And of course you can’t necessarily know that prescriptively right out the gate, but in your process of having experiences working at companies, taking freelance jobs, doing side projects, you start to learn what works for me, where do I thrive, where am I energized, where do I deliver things that people seem to really like or want to pay me for, where do I struggle, where do I not enjoy the work, where do I feel my energy drained, and then learn from that. And you know, I certainly learned pretty early that I want as little structure imposed as possible. I’m the frontier person that likes just the wide open space where I can go and just find opportunity where it may lie. And then there’s maybe some that like heavy amounts of structure, but I think most are somewhere in between. And I think one that comes to mind, maybe this describes you talking a little bit about not every job opportunity in a company is even publicized, which is what I usually call the entrepreneurship, right, which is that same concept of looking for opportunities, but you can only see when you’re inside the company. You’re there working at a more standard role, but then the company is, especially at a startup where things are changing all the time and you see. Some new need the company has that’s sort of unfulfilled and you know, maybe the top level management or leaders of the company should spot that and like form a new department or something, but that’s also an opportunity for someone who’s at the company, has the context and feels drawn, you know, I’d like to solve this problem and I think there’s a role here. I want to make that my job, and they take the steps to kind of create that structure, create that space for themselves. 00:23:58 - Speaker 1: I’ll be curious to see some research on the success rate of entrepreneurship like that, because a lot of times I see those ideas get shot down and then they leave and then they do the thing anyway, because yeah, it’s not in line with the company management goal or whatever. 00:24:12 - Speaker 2: Yeah, that’s right. I think sometimes being an entrepreneur is someone that really should actually be an entrepreneur and they’re in the wrong place to pursue that opportunity. I like to think sometimes in terms of venues, so you see an opportunity at the company that you’re at, maybe kind of carving out a new role for yourself at that company is a great opportunity, but maybe that actually is a thing that’s not best done there and should be done somewhere else at another company, at your own company. And then of course sometimes there’s the even more dramatic version of that is maybe the thing you want to do isn’t even in your current field, and there you actually want to completely switch fields kind of like you did. So I think we always have to think about the work we’re doing as being inside a nested series of containers and to do great work. We think of that as being something that’s inside ourselves or something maybe individual or maybe this is just my kind of American culture by. the kind of you know individualist perspective which is thinking, OK, the way I’m going to be successful is having great skills, but indeed is the systems you plug into the organizations and being in the right place at the right time, and I think for me part of career is following the opportunities to try to put yourself in the right place at the right time to be able to do something meaningful and have a big impact. 00:25:28 - Speaker 3: Yeah, if I can synthesize and emphasize some of the things I’m hearing here, I think it’s really important to take agency over one’s career, and that’s about, like you said, Adam, understanding oneselves first, and understanding the world and what’s out there and making deliberate decisions about how you’re going to move forward in that world towards achieving whatever ends you want. And I think you got to be aware that you’re probably gonna be facing trade-offs among All the different desiderata of one’s career, you know, the feel, the flexibility, the size of the company, the compensation. And I think importantly, it’s my belief that the world doesn’t owe you a living, and it certainly doesn’t owe you your dream job doing whatever you want, making as much as you want, wherever you want and whatever conditions you want, right? You’re gonna have to go out there and find something that works in the same way that an entrepreneur can’t just do a company that makes whatever. Sells whatever, whatever price and expect the market to accept that. You know, you gotta go out there and find what’s desired, what’s valued, what fits with your interests, what skills you bring, and make a deliberate decision like that. And the zero with mistake that I see people making is not understanding themselves. And the first mistake that I see them making is not taking responsibility for their own career decisions and just kind of sleepwalking into something, which sometimes it works out and sometimes it doesn’t. 00:26:40 - Speaker 1: I have a follow up question, Mark, if you think about the importance of understanding yourself, where are you on in terms of correcting weaknesses versus just betting on strengths? 00:26:50 - Speaker 3: So one of my big personal philosophies is to be honest with oneself, and I think it’s really hard to make yourself something that you’re not to kind of fundamentally change your personal characteristics and personality type, I think, as you described earlier. So I think that kind of stuff. It’s really hard to work against you. You’re gonna be going really uphill. I think there are skills that one can develop, and that’s probably worth doing, but I think you gotta differentiate between those and overall, I would lean towards emphasizing your strengths and finding a field and a job that taps into that, cause again you’re gonna be going uphill your whole career if you’re working against that. 00:27:27 - Speaker 2: I think the path I took for that was not thinking, OK, here’s a weakness, let me see if I can become really great at it, but to first of all be aware of it. Secondly, to perform maybe some basic mitigation, don’t make it be a big blind spot or gap that you just can’t do anything about. So one example might be, I know this comes up a lot for engineering and design types, which is like salary negotiation or negotiations generally around compensation and other things. We like to make things. We don’t like to do deal shenanigans or something, and many people feel very, very uncomfortable doing that sort of thing, and I probably count myself among them. But for me, I think fairly early on I realized that that is an important part of being in business, about having a career. There’s going to be certain critical negotiations and you do need to be able to represent yourself and your interests. And for myself at least, it was worth taking a little time to shore up that weakness so that I wasn’t just either completely awful at it or just that it was a huge blind spot. But in no world is there am I ever going to be a great dealmaker, a great negotiator, you know, the hostage negotiator guy or whatever, what’s that book? 00:28:38 - Speaker 1: Never split the difference. 00:28:40 - Speaker 2: Yeah, that’s the one. But it’s full of advice for every reason I go, it’s hard to imagine myself, you know, doing that or anything like it, but I can know what it looks like to be great at that. I can look for people that I want to be on the TV, you know, I can recognize the value of that skill and think, you know, it’s good to have a business partner or a colleague that has that skill and to respect that skill and hope that they can deploy it. In service of you know our team and then I deploy my skills in service of our team, maybe skills they don’t have. So I see it as like kind of a protecting from a downside rather than long-term investing. And when it comes to investing and learning, it’s your strengths and those things where you start investing and you just see those really quick and high returns on what you’re doing because it’s something you like to do and you’re good at. 00:29:26 - Speaker 1: As a poker player, I kind of call that a leak in your game. Like you should know your strengths and what your sweet spot is, but also if you have any leaks or towels, then you probably should know about it and do the bare minimum to correct for it. You know, you’re not going to be a better player by only plugging leaks in your game, but you’re at least going to maximize on your potential value. So that’s pretty good. One thing I often bring up, which is a wonderful piece of career advice from Julia Evans, which is to write a brag document. And this is something that is useful in negotiation in promo conversations or just in regular annual review conversations, which I think people should do more of, which is essentially don’t expect your manager to know everything you’ve done. You think it’s their job. But they have like 8 other people that they’re managing. They have their own stuff going on. They have your interests at heart. It’s not their top priority of the day, even though they might say it is. It’s for sure in your best interest to represent yourself really well, even though you feel uncomfortable about it. But you’re also not going to represent yourself really well because you can have recency bias in all the human cognitive issues of memory and self-deprecation or being humble. So Julia Evans’s advice is to keep a fresh document that you maintain. Of the things you’ve done and the outcomes, the quotes, the measurable numbers, preferably some, some idea of chronological order that fairly represents the kind of work that you’ve done over the year. And I think that’s a wonderful thing that you can just take to the bank or just bring up because you’ll be asked for these things at the most inconvenient times. There’s official performance reviews, but then it’s actually oftentimes the unofficial vibe checks, I’ll call them. When you’re asked like, Leo, how’s it going? And then you know you’d have like a really crappy answer, but if you came prepared, you’d actually have a really amazing answer and that person will walk away with a much better impression of the things that you’ve done for the company and that’s just positive for you in literally every situation. So my version of this, because I’m too disorganized to keep a rag document is I keep a brag Slack channel. I have a Slack channel to myself where I just pop in stuff as they happen that I would like to brag about in the future, and Slack just keeps a reverse chronological order of things that I can look back on. 00:31:46 - Speaker 2: I love that, and the word brag is actually really interesting because, you know, when I have been in the position of offering career advice to friends or colleagues in the field or whatever, representing yourself well and honestly is something that I think is really important, and it’s one reason I like, for example, having a personal website or some kind of online profile, I guess a resume or CV. Serves some of this purpose, but people don’t tend to update it other than when they’re job hunting and it’s a very particular format and that sort of thing, having some way that you can say kind of here’s who I am, what I’ve accomplished and what I’m about, what I value, what I’m passionate about, what you should know about me if we’re going to work together in some way or I’m going to come work at your company or whatever. And I often find many folks are very uncomfortable about this, and I think there is sometimes a cultural thing. I heard from a few German folks when I moved out here and I basically just wrote a little document that was just, you know, one of these GitHub sort of short scratch pad things where I basically said, hey, I’m looking for companies to work with. This is what I’ve accomplished, this is what I’m good at, this is what I’m not good at, this is my ideal profile of company, and here’s the kinds of problems I can help you with. you think this is interesting, let’s talk. And I shared this with a number of folks, and a few folks expressed surprise and one said, well, you know, I love the American swagger that comes across in this and what does that mean? And they said, well, you know, at least where I grew up and maybe it’s especially with East Germany, it’s very much about don’t ever state your accomplishments or what you think you’re good at. Keep your head down, stay quiet, let the work speak for itself, and that any kind of accounting in that form is a kind of bragging. And even beyond the cultural thing, I think there’s a personality thing. Some folks just don’t feel very comfortable talking about themselves, but I think it’s really hard coming back to Mark’s point about agency and taking responsibility for your career. I think it’s very hard to accomplish what you want to accomplish and get the best possible outcome if someone is not taking an accounting of the things you’re good at and the things you’ve accomplished, and who’s that someone gonna be if it’s not you. 00:33:48 - Speaker 1: Exactly. One way I like to point people out to not brag, to not think about it as bragging, is to essentially show proof of work or essentially show things that you cannot fake. So if you say you’re award winning, show me the award. Is it some made up award or some award that actually matters? If you say you’re a thought leader, well, you automatically disqualified from being a thought leader. This is very common, by the way, a lot of people would say like there’s some kind of thought leader and they don’t show evidence because they don’t have any. But if you do, if you do have substance to back up your claims, and show it, then no one really can dispute with you on what the quality of your accomplishments have done. I think honestly it’s a way to just make it easier for people to get to know you. To shortcut the awkward dance that you do when you meet people for the first time and you don’t really know what they’ve done in your life and how you should be addressing that person. So yeah, I just think basically get over it and do it interesting stuff enough that you’d be comfortable putting it on your resume, because if you’re not comfortable with that also probably show something about the scope of your ambitions and maybe you should push yourself a little bit more. One thing I’ll mention as well, which is another anecdote that I have, because I think you mentioned a little bit about negotiation. Which is another piece of career advice that I had with a friend. So a friend of mine who I’ve been advising because he recently graduated from college and got a job at a well-known tech company, he found out that his coworker was getting twice the equity that he got. He was really pissed. He only started a job for like 34 months and he was like, I don’t know, like. We have to save him amount of experience, like I’m doing more than him at my current job and he’s getting twice the equity and the way the equity systems work in the US like, this is locked in for 4 years. It’s kind of unfair, of course. But I told them, the problem is that you’re getting half the equity of your peers and you’re trying to renegotiate for better equity relative to your peers. I think for you, the better angle for your career is to get new peers. It’s kind of like when life gives you lemons, make lemonade. When people give you peers that you don’t compare that well to, for whatever reason, you didn’t negotiate with that well, they looked at you wrong, whatever. Don’t care, just get new peers. Just make yourself in a completely different category that the next time this conversation comes around in 2 years or 4 years, it just doesn’t happen because they want you so badly for the things that you’ve done. And I think his anxiety went away when he realized that it’s not about the short term gain and keeping up with the Joneses. It’s about being in a different neighborhood. 00:36:18 - Speaker 3: I’ll point out that a lot of the queer stuff we’ve been talking about here so far is call it human stuff around the edges. It’s not OK, you should study algorithms and then react and then whatever post crass, right? I mean, I’m sure we have lots of suggestions on that front we could give them on this podcast perhaps, but I think people underestimate how important this stuff is. It’s really important. It’s really valuable. It’s easy to form your mind, especially coming out of undergraduate where everything is like formalized tests and classes and grades. A lot of the important career work does not look like that. It’s just dark matter that exists between people and to your experience, Sean, I think it’s really critical to speak with people who are 5, 10 years ahead of you. In a similar journey because they’re gonna have all kinds of weird stuff that they see and all kinds of interesting tricks that they know of, and they can give you those heads up. It sounds almost too good to be true, but you can just like email a handful of, for example, engineering, hiring managers and your career earnings go up by 6 figures easily. So I encourage people to take advantage of just speaking to people and having a conversation and get advice. 00:37:21 - Speaker 2: Maybe that advice is to kind of pay attention to the basic human dynamics is also especially valuable in a field where maybe a lot of us were drawn to it because we’re not that good at humans or, you know, we’re young introverted kids that learn to play with computers and we’re more comfortable there maybe than we were in social settings, for example, that’s obviously not true for everyone in the field, but lots of people are in that position. But then it turns out that products are made by companies and companies are groups of people who are working together, and groups of people working together always have social dynamics, and of course the individual humans involved have their own thoughts and feelings and emotions, and you have your own thoughts and feelings and emotions and just knowing a little bit about how to navigate all that can make a very big difference for you to be able to integrate to the organization and again have the work you want to have and have the impact you want to have. 00:38:13 - Speaker 1: I have one more point to bring up in terms of sort of general career advice. I think, yes, we want to be intentional or try to point ourselves at worthwhile problems that we think that we can solve and grow together with the industry and, but then there’s a lot of randomness and serendipity and I think being able to square the intentionality and the randomness, I think the best way that I’ve heard about it is to create luck. And it’s like, how can luck be created, it just happens to you. And I think this is one of the biggest mental model shifts that I’ve had in my career so far that I received as advice from people that were ahead of me. I’ll bring you through sort of like a four stage mental model if you’re ready to do that. So like the first stage of thinking about luck is that people are either lucky or unlucky. There’s people that you know, like things just happened for them. I don’t know what happened, but they’re lucky and I’m not like that, so I just kind of treat them as different than myself. And I think that’s a very static view of how luck is distributed in the world. The second stage of this mental model is progressing from that to having some agency in the matter, which is Selina Mark you brought up. And the term that is very popular for this is having a lux surface area, which is that people who are lucky have a larger lux surface area for capturing the random luck that happens in the universe as opposed to people who are not lucky. What kind of lux surface area are we talking about? The two typical axes that people give a combination of doing and telling. Like, have you done enough that is noteworthy for people to take notice of your work and then have you told people about it? A lot of people, particularly on this podcast, are doers. And they’re maybe not so comfortable with the telling, but you have to kind of do both in equal amounts to get your message out there, to get your work out there, so that you get opportunities for future work that compounds and compounds and compounds. But you have to sort of think about it in terms of that two dimensional graphic of like surface area rather than a one dimensional lucky or non-lucky binary metric. Then the third progression in this line of thinking is that there are 4 kinds of locks, so you sort of split that two dimensional chart into like a 2 by 2. So I kind of turn, if you imagine like a 2 by 2 diagram, the y axis, you could sort of split into active versus passive, and the x-axis, you can split into general versus individual. So, for example, general and passive luck is luck that just happens to you. It’s the same luck that a plant would have just being born where it is. A lot of this comes from privilege, but a lot of this just comes from just sheer randomness in the universe. But active luck, for example, that in general is from you just doing random things, trying all sorts of things and seeing what sticks, kind of throwing stuff at the wall and seeing what sticks, right? And you can sort of think about career analogies for that as well. But where things become really individual is that, for example, you sort of primed yourself throughout your career to notice certain opportunities and when it happens, you are one of maybe 5 individuals in the world that can take advantage of it because you’ve just spent all your life preparing for this. And when it happens, you really capitalize on that and that really works out for career progression as well. And then finally, the fourth category, which is active luck, that is also individual focused is what I call magnetic luck, which is that you’ve done so much in your life and you’ve built such a strong network that you draw people to you in the sense that people come your way because they know to seek you out. And I really like this as a mental model because Obviously it’s an aspirational thing, but I do really like the fact that you don’t do as much work, but people are drawn to you for your specific skill set that only you can fill. Like there’s a sort of U-shaped hole in the universe and you’ve created that sort of suction energy or gravitational pull that people find you. And I think as far as careers go, the more unique you are, the more unsubstitutable you are, the better compensated you will be. And the more you enjoy your job, to be honest, right? And so finally, throughout all of that, I think there’s a lot of focus on Being in the right place at the right time. The final stage of this model that I developed for myself is the concept and the place of strategy. Instead of being in the right place at the right time, try to think actively about where the puck is going. A lot of times I call this the meta game behind the game, so a lot of times you’re playing two games at once, you’re playing the game with the rules as they are written right now, and then you’re also looking out for how the rules are changing. And going towards that and hopefully being in a position to change those rules to benefit yourself. But to me, that’s strategy, right, to being able to say like, OK, the status quo is this. I can play by the system, but at the same time, the system is probably going to change in a certain way. If you have an active opinion on that, you can just leave behind the whole system and just go straight for the new one because that’s ultimately where you want to go. I’ll stop there. I feel like I’ve been rambling for a bit. I wanted to just drop this because I think luck plays a huge role in careers, but often people don’t really have a system to think about luck. 00:43:02 - Speaker 2: I like the framework. I think that knowing that, of course, there’s always this huge amount of, as you described a randomness or privilege or just, yeah, the, everyone has a very unique and different circumstances, time and place you were born, particular capabilities, you have just people you just randomly happen to meet that may have opportunities for you, but being alert for those. Opportunities and doing what you can to maximize your opportunities. Well, that is something you can actively do, and I think it’s probably a recipe for happiness and life in general to focus on the things you can affect and work on those things and then try not to lose too much sleep over the things that are circumstances that are essentially forced upon you by the universe. Exactly. Do you have any good personal stories about sort of using some elements of this framework or essentially creating that lock to find your way to, especially the role you’re in now that I’ve heard you speak with great pleasure about? Was there some of this framework that fed into you being able to find this? Yeah. 00:44:03 - Speaker 1: So the blog post that I wrote directly led to me getting hired for the role, and in fact, the full story is a little bit more complicated than that. The blog post that I wrote generated some comments and one of the commenters on that blog post. Got hired as head of product for Temporo and that guy turned around to hire me because obviously I wrote that blog post. So out of that blog post, two jobs came out. But I think the more general meta thing is to write about the most interesting problem in your domain. And just to work towards that, because I think problems are inherently more attractive than solutions, they’re inherently more timeless than solutions. A lot of people are like very focused on solutions like what’s the best tool for personal knowledge management? What’s the best tool for thought? But really, like, OK, sure, like every solution out there is just one instantiation of one team’s current way of thinking of how to solve this, but if you study the problem in the infinite depths of the nuances to what people really want out of that problem. You have a more general and timeless model for evaluating solutions to aligning your career with those solutions and to see what’s missing, to kind of look for the negative space and if that’s valuable enough to pursue it. And it’s kind of what I did with the whole long running job thing. I was like, OK, service is a really well, very competitive space, but hey, the long running job thing is not really being done. And so you just write about it and I think when the opportunity comes up, it looks like nothing happened for like a year. When the opportunity comes up, you’re in a place to have thought through at least the arguments for it so that when they came calling, I picked up the phone, where in a lot of situations, you would ignore an email like that. And that’s also you know something I talked about with the passive individual luck, which I call sort of prepared luck. There’s some situations where you have to kind of prime yourselves because these opportunities happen at random to people and they’re ignored all the time because you’ve just trained yourself to say, like, this is just one of many opportunities, and I haven’t really thought about it. But if you do work hard to understand like what could be missing. Then you prime yourself a little bit better to write it. So yeah, I definitely say that I’ve unintentionally aligned myself towards this framework, just again, this is retroactively breaking it down for myself. 00:46:15 - Speaker 3: Yeah, that’s a great story. And another thing I think it illustrates well is how unknowable the payoffs are for your discrete investment in one’s career capital, if you will. You won’t know and you can’t know if, how and when these investments are going to pay off in practice what we see is it takes a very winding course, you know, it’s a year later someone read a comment and then you know emails or whatever, you know, many such cases. And I think that’s one of the things that makes it so hard to do. You have to, you know, sit down and write a blog post, which everyone knows is a huge amount of work and you’re dealing with people commenting about you on the internet and blah blah blah, but you have to kind of believe that probabilistically at some point in the future, this will pay off. I think it’s just important to be aware of that, because otherwise one’s gonna be frustrated. It’s not something that you can pick an outcome and say I want to achieve that. Therefore, I’m going to do this investment. It’s much more probilistic and random. The flip side of that is that it becomes optionality, you know, if one has career capital, you can, if you will call on that in different ways throughout your career and you don’t need to know the time of creating it, how you will make that call. 00:47:19 - Speaker 1: I think that’s very well put. My personal reflection on this, by the way, is uh, this becomes a problem when your job involves the industrial production of these kinds of things, the industrial production of luck. Like I just told you, like the feedback cycle is over a year for me about publishing a blog post to me getting the job. That doesn’t fit in any OKR or performance review cycle. And when your job is kind of creating content or creating luck in different ways, whether it is sort of laying the seeds. So for example, I have some customers now who I think are potential investments, but they won’t pay off for another 23 years. So they’re viewed as dead weight by some people, but in 2 or 3 years from now, again, like, there’ll be a whole different team taking credit for the groundwork that we laid today. And I think you just kind of had to take a very long term view for that. And I wonder how to measure this because people ask me like, How do you measure your like output or how do you justify the time that you spend on all this personal content? And I’m like, I don’t know, but I just generally believe that doing good things leads to good outcomes. Like there’s a bit of mystic karma that you have to kind of have to suspend your disbelief for, but hopefully it kind of works out. It is an open question, how do you measure this? 00:48:32 - Speaker 3: Yeah, it’s a tough matter of judgment, which by the way, kind of seems isomorphic with the startup investing problem, and I think that the state of the art solution is similar, which is you find people who have good demonstrated ability to. Evaluate these things and you get their advice and opinion. So it circles back to my suggestion earlier I was speaking with people who are a little bit further ahead in their journey. They can’t give you a closed form solution for how to evaluate your personal capital investments, but they can give you their appraisal. I like that. 00:48:59 - Speaker 2: Yeah, hearing you describe it that way, it made me think of investing. It also makes me think of the sales, for example, especially enterprise sales, it can be a very long cycle as an element of this, and research, right? The work Mark and I were doing, and I can switch, and the work that team continues to do, where, you know, you can have KPIs around papers published and citations and things, and that is what tends to kind of drive the academic world, but the reality is, it is very long term investment. Most of it won’t pay off, but the things that do pay off, you know, occasionally you invent calculus or split the atom or whatever, and those payoffs are so big that it’s worth having a big portfolio of these things, and so it’s probably the same for career investments, whether it’s finding opportunities through blog posts, through attending events where you’re likely to meet other like-minded people. And so on. It’s a long and steady portfolio of investments and over time, you can post hoc show how it paid off, but it’s really hard to measure it in a week by week or month by month metric. 00:50:00 - Speaker 1: Yeah, totally. I will say that there is a noticeable difference between people who engage in these luck creation activities, let’s just call it LCAs, as a general category of like blogging, speaking, whatever, right, putting yourself out there. There’s some people who just do it because they are told that it’s a good thing to do and then they do that, and others who do it because they’re genuinely interested in the thing that they’re working on. And every time it’s super obvious which is which, and one is just completely not that valuable and I wish I could tell them without offending them. And the other is I wish they would do more of and a lot of them don’t because they don’t know that they have it, whatever it is. And Basically, what I’m saying is like the outcomes are almost secondary to you loving the process, just falling in love with the process, making the best thing you could possibly make like for its own sake, not because you think some benefit will flow back to you eventually, because it will, but if you’re motivated by the benefit first, you’ll make a worser product. 00:51:00 - Speaker 2: That to me also circles back to something I realized at some point in my career, which is I care very much about the mission, the impact, you know, the thing you’re making, right? I want to go to work for this company because they make this product or I want to get involved with this group that’s working on this open source project or whatever because I love the product or the problem they’re solving or whatever, and that remains incredibly important to me, but it has become of equal importance to me, the Exactly as you said, loving the process, loving the act of what I’m doing when I sit down every day, and whether or not this particular product I’m working on a particular project I’m involved in right now has kind of the impact I wanted to have because again, some do, some don’t. That’s part of the business, but I want to know that I’ve enjoyed the day to day, the week to week, and a lot of that is the people I’m working with, the specifics of what kind of work I’m doing. And maybe the vibe of the team, the culture, even something like the tools we use, right, that if the tools make the creative process and my daily work kind of enjoyable and fun versus they’re sort of clunky and feel like they’re holding me back. It’s those collection of things really matter a lot. And in fact, I’ve told the story on the podcast before, but I, similar to you made a transition, career transition from video games early in my life, and that was something I was passionate about making games and I still think games are an incredible form of art. But the process, at least at the time I was involved in it, the way the teams worked and the tools and all that sort of thing were very punishing. I would describe it as, it wasn’t worth that to me. It wasn’t worth hating the day to day in exchange for producing a thing I’m proud of at the end, or an art form that I wanted to be involved in. 00:52:43 - Speaker 1: You kind of have to go through that journey to appreciate what you have today, don’t you? 00:52:47 - Speaker 2: Quite so, yeah, I never would have thought, you know, as a younger person that business and productivity software would make me a lot happier than writing video games for a living, but you know, sometimes you got to maybe achieve your dream to realize it’s not what you want after all. 00:53:02 - Speaker 1: So, a lot of people come to me actually, they’re inspired by games. A lot of us got into programming because of games and design because of games. But then, I immediately tell them to avoid the AAA game industry like play, right? And I wonder how to fix that because like that cannot be a sustainable way of things. And I don’t know, like GameDev just seems like such a dead end career because it takes such talented developers, pays them nothing, and they all come up burned out. And I feel like we should talk about this more because like, how do we fix this? 00:53:32 - Speaker 2: Yeah, well, I feel the indie game revolution, you might call it, when that sort of started to happen, I think it was kind of in the late aughts, is that what we’re calling that decade now, but things like Braid, for example, was, I think one of the first kind of like, what seemed to be successful relative mainstream success made by a relatively small team, partially enabled by these new platforms like the Xbox, Marketplace, and Steam and so on. So to me, I could imagine myself getting back into games now, I wouldn’t do that cause I love what I’m doing, but there is a coming back to this venue idea or container, you know, the AAA in game industry was not the right venue for me to express my ideas and do my work with something like the indie games world, where a couple of people can make a successful game that has a lot of art and makes a unique statement, and can be played by a lot of people, and, well, you can make a living from it. And the style and approach and you know, just add a work life balance of the indie games industry is quite a different beast from the AAA world. 00:54:34 - Speaker 3: Yeah, for me, this also moves back to the agency discussion and this idea of actively understanding the world. I’m not sure because I don’t know a lot of people who entered and exited the AAA space, but my suspicion is that there’s a few fields where people really significantly misestimate the nature of the work in totality, including the conditions and the career implications and compensation and hours and things like this, and I think that’s one of them, and I think they get a little bit blinded by what they see on the outside, and I think if one. took more time to see what’s on the inside, they might come to a different conclusion. Now I think there’s also an element of people, they know that’s there and they still want to do it, you know, cause people are different, you know, fair enough, but this is a case where it’s worth it